Tim   
#dotnet 9 had a breaking change that broke #GeoBlazor. They no longer support multiple constructors in Razor Components without adding an `[ActivatorUtilitiesConstructor]` attribute. I missed this one earlier bc of the issues with static file compilation that made GeoBlazor painfully slow to compile. Hope to have a quick fix out soon. https://github.com/dotnet/aspnetcore/issues/58004
[Blazor][net9] System.InvalidOperationException: Multiple constructors accepting all given argument types have been found in type 'Component'. There should only be one applicable constructor · Issue #58004 · dotnet/aspnetcore

Is there an existing issue for this? I have searched the existing issues Describe the bug The System.InvalidOperationException: Multiple constructors accepting all given argument types have been fo...

GitHub
Dec 19, 2024 at 8:31pmWeb
Show threadTim   Dec 19, 2024
Even when I fix this, however, #GeoBlazor apps are going to be *really slow* to compile until Microsoft fixes this #dotnet #aspnetcore issue https://github.com/dotnet/aspnetcore/issues/59014
Razor Class Library Build Time Serious Regression with .NET 9 SDK · Issue #59014 · dotnet/aspnetcore

Is there an existing issue for this? I have searched the existing issues Describe the bug Build time for a Razor Class Library with significant static assets (JavaScript files) is more than 4x slow...

GitHub
Show threadTim   Dec 19, 2024
So I intend to mostly stick to .NET 8 for GeoBlazor projects for now. You also want a global.json pinned to #dotnet 8 to not get the compilation issue.