ABP VS dotnet-webapi-starter-kit

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've seen two possible solutions, one is that User table isn't created in the domain model, and when you want to reference something to a user in the domain model, you just give a GUID as field, but you don't reference directly to the user, in other words, its just a GUID field, not an explicit foreign key. This way is implemented in this example: https://github.com/fullstackhero/dotnet-webapi-boilerplate

not exactly empty, but https://github.com/fullstackhero/dotnet-webapi-boilerplate , its built on top of mudblazor, open source, has theme preferences manager and much more

https://github.com/fullstackhero/dotnet-webapi-boilerplate , comes with a blazor client too in another repo in the oragnizaiton