blazor-workshop VS ASP.NET Core

https://github.com/dotnet-presentations/blazor-workshop/blob/main/docs/09-progressive-web-app.md tells you how to implement push notifications the way I think you mean.

Blazor - app building workshop

If you just want a tutorial I recommend learn-by-doing so you dont just sit there for an hour and then forgett about whatever you just did. https://github.com/dotnet-presentations/blazor-workshop

If you already know C#, then it won't take you long to try Blazor to see if you like it. If you want a guided walkthrough then I recommend https://github.com/dotnet-presentations/blazor-workshop to get started. James Montemagno is also doing a youtube series on it https://www.youtube.com/playlist?list=PLwOF5UVsZWUj3rc2ACx3pTN1MgXTSGlVu

This workshop is a cool way to get started https://github.com/dotnet-presentations/blazor-workshop

When you have the basics, follow the Blazing Pizza Workshop for a good guide to structure, flow, etc. Shows lots of good practice. https://aka.ms/blazorworkshop

> 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.