You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Microsoft.NET.Sdk.StaticWebAssets.Compression.targets(345,5): Error MSB4018 : errore imprevisto dell'attività "ApplyCompressionNegotiation".
System.InvalidOperationException: Endpoints not found for compressed asset: C:<redacted>\obj\Release\net9.0\compressed\4t6f7o5fzg-j538s5lvtp.gz
at Microsoft.AspNetCore.StaticWebAssets.Tasks.ApplyCompressionNegotiation.Execute()
at Microsoft.Build.BackEnd.TaskExecutionHost.Execute()
at Microsoft.Build.BackEnd.TaskBuilder.ExecuteInstantiatedTask(TaskExecutionHost taskExecutionHost, TaskLoggingContext taskLoggingContext, TaskHost taskHost, ItemBucket bucket, TaskExecutionMode howToExecuteTask)
After adding the package to the blazor wasm solution I get this error at publishing to a folder. In my case the call to .AddBlazorJSRuntime() is within a components library meanwhile I call .BlazorJSRunAsync() in the usual Program.cs file as usual.
To Reproduce
Steps to reproduce the behavior:
Add the NuGet package to the solution
Click Publish to folder
See error
Expected behavior
The publishing works as usual
Desktop (please complete the following information):
OS: Windows 10 x64
Browser edge
The text was updated successfully, but these errors were encountered:
The issue was originally set to be fixed in .Net 10 but Microsoft coders have since found the source of the issue and it should be fixed in a future release of .Net 9.
Describe the bug
After adding the package to the blazor wasm solution I get this error at publishing to a folder. In my case the call to
.AddBlazorJSRuntime()
is within a components library meanwhile I call.BlazorJSRunAsync()
in the usualProgram.cs
file as usual.To Reproduce
Steps to reproduce the behavior:
Expected behavior
The publishing works as usual
Desktop (please complete the following information):
The text was updated successfully, but these errors were encountered: