Closed jseeley-cricut closed 2 years ago
Update; I realized that I also switched to host in IIS, not Kestrel or IIS Express. This is an issue locally on my debug machine with IIS alone. Works in Kestrel, works in IIS Express. I'm closing this because it is a hosting related issue (and likely permissions at that).
Describe the bug Created a brand new Blazor WASM "hosted" project in .NET 6 as per Microsoft docs.
To Reproduce Steps to reproduce the behavior:
using the following command:
dotnet new blazorwasm --hosted -o HostedTest
Add Blazorise to the
.Client
application per documentationRun the
.Server
application in debug modeSee an error
Expected behavior Expected the site to load and start using Blazorise resources. This does work if I launch the client application directly instead of using the Server application passthrough.
Screenshots
Additional context Add any other context about the problem here.