ASP.NET Core VS AspNetCore-Developer-Roadmap

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.

As I'm not utilizing ASP.NET, despite its resource-intensive nature and occasional unpredictability, I prefer the cost-free option. I'm hesitant to invest in EPPlus or engage in trials, and moreover, I am more proficient with Interop. Given the limited volume of records in my department, there's a preference for utilizing tools covered by our existing license. This avoids the need for navigating through layers of approval within the chain of command and ensures compliance with our contractual agreements and Microsoft's patch management, ultimately aligning with a cost-saving mindset.

Here is a cool repo that I think might help too: https://github.com/MoienTajik/AspNetCore-Developer-Roadmap

ps As middle in my team I improve basic knowledge (.net + struct + algorithm + angular) and going through asp.net roadmap. In my team I can ask for help to build bore specific path, if you ask your more senior teammates the will help with advices and loooooot of materials Good luck =)

But I'm confused. I found 2 roadmaps for backend development. One is from Nick Chapsas Elfocrash/.NET-Backend-Developer-Roadmap: Roadmap for a .NET Backend Developer working with Microservices (github.com) and the other is from a /r/learnprogramming thread I ran into today MoienTajik/AspNetCore-Developer-Roadmap: Roadmap to becoming an ASP.NET Core developer in 2023 (github.com)