MudBlazor VS Roslyn

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.

and you can use mudblazor components for free. https://mudblazor.com/

I'm creating a Blazor MAUI project using MudBlazor, and I'm looking for a way to refresh a page on Android using the pull to refresh feature. By now the best result I've found is to surround all the with a tag as shown here but this would mean refreshing the whole content on the page, NavMenu included. I've also tried to implement the BcdLib/PullComponent: with this one I can refresh only the body of the page but I can't achieve a smooth refresh animation like in the first method.

The load times and lighthouse score for the MUD Blazor site has put me off of Blazor entirely for anything public facing:

https://mudblazor.com/

My understanding is that the .NET team is working toward this with Interceptors: https://github.com/dotnet/roslyn/blob/main/docs/features/int...

.NET is a little smarter about switch code generation these days: https://github.com/dotnet/roslyn/pull/66081

Recently, while creating some experimental C# source code generators (xafero/csharp-generators), I was just concatenating strings together. Like you do, you know, if things have to go very quickly. If you have a simple use case, use a formatted multi-line string or some template library like scriban. But I searched for a way to generate more and more complicated logic easily - like for example, adding raw SQL handler methods to my pre-generated DBSet-like classes for my ADO.NET experiment. You could now say: Use Roslyn and that's really fine if you look everything up in a website like SharpLab, which shows immediately the syntax tree of our C# code.

At runtime, the Case C# expressions are embedded into a function and dynamically compiled into an assembly using the Roslyn C# compiler. Then the function that contains the expression is called (e.g. CaseAvailableFunction.Availablle()). At runtime, the function provides various methods to access stored case values as well as the current input data.