-
Finalize the workload-id and any aliases for installing blazorwasm-aot and/or browser-native workloads and aliases therein. Preview4 shipped with `microsoft-net-sdk-blazorwebassembly-aot` the inital …
-
Upgraded the project to .NET 6 Preview 7 and suddenly it shows the JSON key instead of the actual value. Worked perfectly before the update to .NET 6 Preview 7 (including Preview 6)
-
### Question 1: how to address the CORS policy?
> Access to script at 'https://meet.jit.si/external_api.js' from origin 'https://localhost:44376' has been blocked by CORS policy: No 'Access-Control-A…
-
Hey, I'm pretty sure I have everything setup properly based on the guide in your readme file, but on the callback (after visiting the IDP) I'm getting the following error:
```
crit: Microsoft.AspNet…
-
# Problem description
With a blazor project (using Microsoft.NET.Sdk.BlazorWebAssembly) a library [LIB1] is referenced (using Microsoft.NET.Sdk.Razor).
In LIB1 typescript is used. The typescript s…
-
### Describe the bug
A project pack fails because the same file is being compressed twice.
Here are the logs that show the output:
```
[01] Compressing 'C:\MyProject\output\net6.0\MyProject…
-
### Feature Request
This is a request for .NET 6 Preview 5, which is not out yet. There's a bug in Preview 4 that prevents AOT workloads from working. https://github.com/dotnet/sdk/issues/17865
…
-
### Is there an existing issue for this?
- [X] I have searched the existing issues
### Describe the bug
My blazor wasm project publish fails after updating nuget packages to 6.0.6 and my visu…
-
### Describe the bug
1) I updated my project to .Net Preview 6
2) All was working including publishing my wasm app
3) I referred back to the announcement blog and discovered that I missed the s…
-
I have blazor hosted. I run dotnet watch inside server project. Only hot reload works for sever project not the client project.
I try to run dotnet watch inside project. It has hot reload on client p…