ASP.NET Boilerplate VS JHipster.NET

https://aspnetboilerplate.com/ (por si alguien le interesa)

This is pretty similar

Aspnet boilerplate has great documentation and handles multi tenant. Good design patterns and supports several front-end frameworks. https://aspnetboilerplate.com/

DotNetBoilerplate might suit your needs. They also have a more advanced commercial offering

Hi beautiful people of learnprogramming. I’m a Junior-Developer and I‘m having a hard time learning the backend-part of the Framework I been using for the past months. We use ASP.NET for the backend and Angular for the front. The angular part gets slowly better, the backend I‘m a complete noob. We use http://aspnetboilerplate.com and the learning curve is so high.

Evo ja trenutno radim za klijenta koji ima vise projekata i koriste ASP.netZero koji se placa a bazira se na AspNetBolerplejtu. Ti bojlerplejtovi su odmah spremi za rad sa Angularom, Vue ili Reactom za front.

Hands down ABP. Download and follow the tutorials, you’ll get a great education out of it. It’s multi tenant and the documentation is excellent. ASP.net: https://aspnetboilerplate.com

ABP was an acronym for "ASP.NET Boilerplate". However, it is the name of the previous generation: https://aspnetboilerplate.com/ ABP.IO is the next generation of the ASP.NET Boilerplate framework and we no longer use the long name, because the "Boilerplate" word is misleading (they think it is just a startup template, but actually a complete framework & platform).

Alright, so I'm using an https://aspnetboilerplate.com/ template with Angular and it's awesome. Basic Angular app that is responsive, lots of out of the box functionality to play with. Here's a screenshot of the structure: https://imgur.com/a/WOPOKj1

I found this post about a highly customisable .NET Application generator which looks promising. It could be indeed very convenient to gather a fast "start template" for any project. Since the latest release, it looks like we can enable the "CQRS design pattern". I never heard about CQRS before, but from what I understood it uses the mediator pattern from MediatR to do a "seggregation" between queries and commands thanks to an "Application layer". I also found some people arguing that MediatR is good and that they're using it to implement CQRS. I also find that those patterns are very close to the DDD approach. What bothers me is that those patterns‏‏‎‏‏‎‏‏‎‏‏‎­seem really difficult to understand/master. If you're curious just like me, you can try to generate a CQRS app from their Github repository. I find this being a good way to discover this "not so well-known" pattern. But anyway, do you think that it's a good design pattern? I never worked on a project using it, and I'm afraid that the beneffits from this pattern aren't worth the trouble.

Well, I happen to be involved in a code generator (https://github.com/jhipster/jhipster-dotnetcore).

If you're curious just like me, you can try to generate a CQRS app from their Github repository. It find this being a good way to discover this "not so well-known" pattern.

This community is based on JHipster.NET, an open-source .NET application generator based on JHipster !

https://github.com/jhipster/jhipster-dotnetcore https://wrapt.dev/

https://github.com/jhipster/jhipster-dotnetcore is quite nice and lets you generate code using their JDL format which is quite easy to use, not really a starter kit though, goes a bit further than the basics

Hi, i'm the maintener of JHipster.NET (https://github.com/jhipster/jhipster-dotnetcore). The advantage of JHipster.NET it's that the code is generated so you can do whatever you want with it. And there's less magic. That's what i like in this project compared to the other libraries.