Is there support for Razor Components (aka server side Blazor)? #676
Thanks for a great framework! I've used it in the past, and hope to get it working with my current Razor Components project.
Steps to recreate:
I'm unfamiliar with crosswiring and ASP.NET; please let me know if I made any errors. Blazor initially did not support custom service providers, but that was fixed recently. AutoFac seems to work, so I feel like I'm missing something. I'm using SimpleInjector v4.4.3 (and Integration.AspNetCore.Mvc v4.4.3). Thanks again!
I tried to get the full stack working with VS2019prev, .NET Core v3, templates, etc, but for some reason the
Can you provide me with a .zip file of your solution?
And don't forget to post the full stack trace.
You used to have to install the Blazor extension to get the dotnet templates working. Now, as far as I can tell, it's major benefit is giving you intellisense in
When I run
I threw it on github here.
I had to navigate to https://localhost:5001/fetchdata directly from a new tab to see the error in the
A painful observation is that the building of these Razor Components is tightly coupled to the built-in configuration system, and I see no easy way to redirect the resolution of those components to a non-conforming container, such as Simple Injector.
Hopefully, this code isn't released yet and the Microsoft team can still make some changes to the design.
Hopefully @davidfowl can chime in and correct me if I'm wrong.
David, am I correct by saying the necessary Seam is missing in this part of the ASP.NET Core code base or is there a different way for non-conformers to plugin at this point? If there's no way to integrate, can you make sure this is something that will be addressed?