Fluxor VS ASP.NET Core

Take a look at Fluxor! Might be a little bit of a learning curve at first, but you will see how much it reduces the headache in these cases.

Ive been using fluxor in my blazor projects. I love it. https://github.com/mrpmorris/Fluxor

Check out https://github.com/mrpmorris/Fluxor which is an implementation of the react pattern for blazor, similar to redux. If you are used to the concepts of actions and reducers it should be pretty easy for you to get going.

There's a ViewModelComponent where T : IViewModel This ViewModel has to be a state object, meaning part of Fluxor.

Look into using some nuget like Blazor-State or Fluxor to achieve this?

You will probably need to implement a shared state that both components can utilize as their model. This is the type of scenario that Fluxor is designed for. (Not a recommendation, just a reference)

Application state using the Flux pattern with the Fluxor library

Another thing you might like based on your username, lol - I'm using Fluxor in one of my projects and it's pretty good. You'd still foreach loop though your list of items, but create an async "fetch data" request for all your items waiting in a queue to be processed. And you can just add observers when parts of your data are loaded. Makes it pretty easy to fetch batches of data

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.