MudBlazor VS ASP.NET Core

Our website is updated as well: MudBlazor - Blazor Component Library

Though I can't develop beautiful UI and good UX even if my life depended on it. I can write a functional front-end, but don't expect it to be pretty. I usually ask for assistance regarding that from our UX designers instead where they essentially layout the whole UI (either on figma or Photoshop) so I just need to make it functional. Component based frameworks these days (JS, and Blazor) really helps at least. The UX guys usually make sharable base components that the company needs (buttons, grids, etc...), which includes all the styling and animations and we use those instead to create decent looking UI. For personal stuff I use MudBlazor which kinda does the same, but I do know a bit of css to customize when needed.

There are a ton of component libraries out there. I like the mudblazor library. https://mudblazor.com

There are grid controls from the usual commercial vendors like Radzen and Telerik. I used them briefly during a free trial. It has a funny name, but MudBlazor [1] has been the MIT licensed library I have been using lately. I have been using their Table control, which may be what you are looking for in a data grid. [2] Check it out and see.

[1] https://mudblazor.com/

[2] https://mudblazor.com/components/table#api

It seems to be a known issue a known issue. By default, external libraries such as MudBlazor are not trimmed

I recommend Mud blazor if you're going for Material design. For other design languages Andt Blazor's pretty polished and there's Blazorise as well if you want to be flexible (it supports Antd, Bulma, Bootstrap and Material via configuration).

The ones I've used that's pretty good are MudBlazor (Material Design), Antd blazor (Antd), and Blazorise (Multi design support via configuration). There's also the newly announced Fluent UI for Blazor at MS build that's from MS themselves but I haven't tried it yet.

There's Uno that's been talked about by MS community standups if you wanna use UWP XAML to do the Job. If you wanted to use Blazor though, you'll have to at least learn a bit of CSS and Html. Luckily you can find really nice component libraries like mudblazor that does a lot of the nitty gritty html + styling for you. So you'll just have to use their components most of the time and with little to no JS required (depending in your usecase).

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