MudBlazor VS Radzen Blazor Components

Taking a quick look at the MudBlazor environment https://mudblazor.com/, we thought it would be interesting to put a TeeChart in there.

Now do the same using Blazor Server (C#). For convenience use https://www.fluentui-blazor.net/ or https://mudblazor.com/ for your UI components.

It has it's compromises but it's great for just building stuff, with UI updates streamed to the client, no JS (or as much as you want), no extra API building just for the sake of your SPA. Note that I'm not talking about Blazor WASM.

If you're interested in working as a developer for corporations outside of the SF bubble (e.g. the other 80% that use Windows instead of macOS) it's worth checking out, especially for internal corporate stuff.

I recently started doing some front-end stuff using C# with Blazor [0]. As UI component library I'm using MudBlazor [1].

I think it's very easy to create a beautiful app this way. You can still use CSS if you want, but don't really need it to start out.

If you want to style an app, just adjust a couple of colors (primary, secondary, surface, background, ...) of the theme and the app looks quite different already. I believe the color scheme is based on Material design, as such, many (shades of) colors will be automatically calculated based on the couple of colors you choose.

Of course you can also change fonts, icon font, etcetera to further customize the app.

The best thing about this approach from my POV is that you don't have to deal with much JavaScript, CSS, HTML ... (though the option is still there when needed).

---

[0]: https://dotnet.microsoft.com/en-us/apps/aspnet/web-apps/blaz...

[1]: https://mudblazor.com

I don't think that new Identity pages will work with MudBlazor out of the box. Take a look at this GitHub issue: https://github.com/MudBlazor/MudBlazor/issues/7805

The Blazor Server application uses the open source component MudBlazor, which I recommend to C# oriented developers. To keep the application simple, all data is stored in JSON files.

You could use Mudblazor and Codebeam Mud extensions.

Look up some Blazor UI / Component Libraries.Awesome-Blazor lists the more popular ones. The two I recommend are Mudblazor and Havit Blazor because the documentation is built using Blazor and the repos are open source on GitHub.

To client project, without any changes, just added Appointment.cs, EventConsole.razor, AppointmentPage.razor, AddAppointmentPage.razor, and EditAppointmentPage.razor (copied from the demo radzen-blazor project) and the scheduler component works as expected.

Since you already have extensive C# experience, Blazor will be incredibly easy to pick up. I came to Blazor from WPF and Xamarin, and it just clicked. Microsoft has done an excellent job documenting it, and there are plenty of amazing libraries to use, both in terms of utility and components. Since you're developing internal tools, where design is not a concern, you can get incredibly far, incredibly fast, with something like Radzen.

I'm curious as well. I'm look at Radzen at the moment, but have only installed it on my laptop, have don't nothing else.

Radzen is open source, (here is the datagrid, cause I was trying to see how they were doing the select all)

The second step to take is to go to https://www.radzen.com/

The license at this location would indicate that they are Open Source: https://github.com/radzenhq/radzen-blazor/blob/master/LICENSE