ABP VS JHipster.NET

In conclusion, ABP Suite is a game-changer in the realm of application development. Its modular design (comes from ABP Framework), powerful code generation, and support for modern frontend frameworks make it a go-to choice for developers looking to build scalable and feature-rich applications. Whether you are working on a small project or a large enterprise application, ABP Suite provides the tools you need to succeed in your development endeavors.

We use something like this at work: https://abp.io/

Take a look at abp.io. The framework is free and there is also a commercial version. It supports Blazor Server and WebAssembly UI layer.

Even better, try this version: https://github.com/abpframework/eShopOnAbp which is eShop on the ABP framework which I highly recommend.

We're using ABP and TinyMVVM along with the CommunityToolkit.Mvvm, working nicely.

Best i can think of is https://abp.io/

See the abp.io source code and document. Excellent documentation and well structured code.

I'd like to suggest ABP. Follow the getting started tutorial. They also blog about DDD things and offer some additional info and articles about it on the site and in the walkthrough.

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.