FullStackHero vs BlazorHero

[jasonabanico]

When fullstackhero / blazor-wasm-boilerplate gets released, will it have the same features as in BlazorHero? For a future full stack project running on Blazor against Web API, what will be the things to consider when choosing FullStackHero or BlazorHero?

[FrancoisMongeau]

Hello Mukesh,
The question/comment above kind of relate to the message I DM'ed you a couple of days ago:
Hello from Canada! Great work - I learn a lot from you.
Can I respectfully ask: it's not clear how all these projects are related. for example FluentPOS, BlazorHero and fullstackhero...
fluentpos has a published Milestone of Nov10 for v1. But there is no published Milestone for BlazorHero v3. ...
Is fullstackhero the next (more complete, .NET6) version of BlazorHero ?
I'm sure many of your followers would appreciate clarifications on the above. Thank you kindly.

[iammukeshm]

Hi @jasebanico & @FrancoisMongeau! Let me explain the purpose of each of the projects first.

blazorHero - I would use this project as a starting point when a requirement is that of an internal application/website that needs Blazor as the primary application which can expose a few API endpoints if needed. blazorHero is complete in that way.

fullstackhero - When I need a more general-purpose API with much more flexibility to work, I would choose this. In this project, the dotnet-webapi-boilerplate is like the CORE project whose services can be consumed by the accompanying Client Projects like Angular / Blazor / MVC. FYI, For the client application, I would be concentrating more on perfecting the Angular Project (as soon as I am done with the API project).

fluentpos - is a variant of fullstackhero serving a specific business need along with a modular architecture.

As for the current planning, fullstackhero will be my top priority along with fluentpos. I am keeping blazorHero updates for later,as I feel it's kinda mature now.

fullstackhero will definitely be the project to watch out for!

You will be getting an API with the following features

• Clean Architecture .NET 6.0
• Multitenancy Built
• Out of the box support for MSSQL , MySQL , PostgreSQL
• Advanced User, Role & Permission Management
• Code Analysis Built-in to help maintain code sanity
• Repository Pattern
• Rapid Development Framework

So, now that we have the API complete, fullstackhero will also provide client-application boilerplates to consume the developed API.

• Angular
• MVC
• BlazorWASM

I hope I have made myself clear. Thanks!

[FrancoisMongeau]

Thank you for taking the time for this complete answer. Just for the record: I, for one, have no interest in older tech like Angular: the future is Blazor IMHO. I would prefer emphasis on Blazor WASM. Respectfully.

[iammukeshm]

In my opinion, Angular is like 10 times more mature and faster to develop with than Blazor offer. Blazor is cool, but yeah, it is still a very new framework. Angular is definitely not old technology. It receives updates every 6 months with an active dev and user community. And yeah, it's backed up by Google. But I expect Blazor to come close pretty soon.

[justSteve]

@iammukeshm You are no doubt correct re: the maturity of Angular and from your perspective it makes sense to concentrate on that client first. On the other hand, for those of us focused on Blazor it will be difficult to be patient enough to wait.

You have provided an excellent starting point of a Clean Architecture implementation for Blazor at BlazorHero. I'd like to take lessons learned there and migrate them over to FSH asap.

Could you provide some guidance on how you see FSH organized to support the 3 different client frameworks?

Understanding that we are in pre-release territory and that the Core will see breaking changes for a while - do you foresee different branches per Angular vs. MVC vs. Blazor or would one 'Main' containing all three be possible?

Or perhaps an argument could be made for the Core to stand as it's own repo with separate repos for each client?

thx

[iammukeshm]

@justSteve Hi!, so regarding the repository setup, the current repo, ie dotnet-webapi-boilerplate contains only the API project as the name suggests,

blazor -> https://github.com/fullstackhero/blazor-wasm-boilerplate (yet to start)
angular -> https://github.com/fullstackhero/angular-material-boilerplate (I started somewhat on this)
mvc -> https://github.com/fullstackhero/dotnet-mvc-boilerplate (yet to start)

This gives a much better separation than branching out. in realtime application, standalone webapis make more sense, rather than to club multiple client techs. This way, a developer can choose the client tech he wants and get started very easily. Makes sense?

[gfo2007]

@iammukeshm thanks for taking the time to explain all the differences. Please when will we get some detailed documentation on how to create one's own entities from the Model to the UI side in BlazorHero? There are many areas that are not so easy to follow even after reading the Onion Architecture article.