Rafael F.

I'd love to see a link or example on how the MudBlazor team suggests we test components that use MudSelect, because so far it has been very frustrating to use...

Same here, easy to reproduce, create a new project and add mudblazor. Go to launchSettings.json and create 2 profiles, Development works, Local doesn't. `"profiles": { "Local": { "commandName": "IISExpress", "launchBrowser":...

> Since this issue has been resolved in the 6.x version of MudBlazor and .NET 5 is EOL. This can be closed. This is not fixed, I'm using Mudblazor 6.0.15...

> @rafaelf82 could you also confirm that @alex-maro solution fixed your problem? 😊 Yes, using builder.WebHost.UseStaticWebAssets(); fixes the issue.

This is not fixed, I'm using Mudblazor 6.0.15 and .Net 6 and just had this issue, if ASPNETCORE_ENVIRONMENT is not "Development" we cannot run the application in Visual Studio.

The following code also fires OnComplete twice, it's also fired from OnUpdate but using Kill(true) instead.... ``` public void dotest() { Sequence sequence = DOTween.Sequence(); int updatecount = 0; int...