JHipster.NET VS ASP.NET Core

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.

> Just .GetAwaiter().GetResult() it.

That won’t work with various synchronization contexts, where doing this would cause a deadlock. There’s not much fun in trying to debug such issues.

And now that various libraries only provide async api, or worse an non-async version wrapping the async one with . GetAwaiter().GetResult(), you’ll be in for a treat updating your dependencies.

Async all the way is the answer, although various frameworks still don’t offer async hooks. Recently I ran into this for example trying to write an async validator in blazor, but that’s not possible and you have to work around it [1].

C# 5 introduced async/await almost 12 years ago. And we’re still not “async all the way”.

[1]: https://github.com/dotnet/aspnetcore/issues/40244

This approach to organizing middleware enhances code readability, maintainability, and reusability. By following this encapsulation pattern, you're adhering to best practices in ASP.NET Core development, ensuring your application remains well-organized and scalable.

🌟.NET 9 Preview 2 ➡️.NET 9 Preview 2 Discussion ➡️ASP.NET Core updates in .NET 9 Preview 2 ➡️ASP.NET Core updates in .NET 9 Preview 2 Release Notes ➡️EF Core updates in .NET 9 Preview 2 ➡️.NET Aspire preview 4 - .NET Aspire

https://github.com/dotnet/aspnetcore/issues/50643

Even if you look at Microsoft’s by far most popular GitHub project, they’re still only half as big as SupaBase. If you believe “the SupaBase story”, SupaBase grew and became twice as large as Microsoft in 3 years. Below is their likes over time if you’re curious, together with a couple of additional “too good to be true” Silicon Valley projects.

https://github.com/dotnet/aspnetcore/issues/10117

To achieve these objectives, we will take inspiration from ASP.NET Core Identity's PasswordHasher class. It incorporates a concept of hash versioning, allowing only the number of iterations to be modified.

yes I watched several courses, may be aim not getting clearly. but i worked with asp.net which uses http call and firebase cloud function also which uses socket connection, for socket connection its makes sense to use observable bcoz there streams of data we can observe once the connection establish ,but for http it need to be call every time.