Radzen Blazor Components VS ChartJs.Blazor

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

Works well: https://github.com/mariusmuntean/ChartJs.Blazor

I just published a Blazor ChartJs wrapper pax.BlazorChartJs. There are already some very good libraries out (e.g. ChartJs.Blazor).

I've googled it and found this ChartJs.Blazor to be a viable alternative, but it seems to not be very updated.

https://blazor.radzen.com/ , https://mudblazor.com/ , and https://www.iheartblazor.com/ are free tools for chart. iheart support percificly for chartjs only, you will have a lot of option for charts. Radzen and Mud provide standard charts and enough for a standard application with more ultilities support like table, form, tab, etc.