Closed uhfath closed 2 years ago
Thanks for contacting us. This has been fixed for 6.0 release. We recommend updating to the latest 6.0-rc2 release to get the fix.
I see, thanks. Is there any possibility to backport this fix to 5.x?
@mkArtakMSFT, could you please suggest a workaround for 5.x? There is no way we can afford migrating to a preview of a 6.x just to publish the project.
Describe the bug
When trying to publish a Blazor Webassembly project in multiple ways I get some weird looking errors whereas rebuilding and running from VS works fine.
To Reproduce
dotnet nuget locals all --clear
);dotnet publish -c Release -r browser-wasm -p:PublishTrimmed=true --self-contained true --nologo -o publish -v d > publish.log
The file in question is reported multiple times but it's always a random file.
Then I tried to publish without compression (steps 1-2 are same):
dotnet publish -c Release -r browser-wasm -p:PublishTrimmed=true --self-contained true --nologo -o publish -v d -p:BlazorEnableCompression=false > publish.log
200 ok
integrity.ps1
script but without luck (my app is not a PWA so there is no service worker script used):Invoke-WebRequest: D:\Projects\MedService\Application\MedService.UI\MedService.UI\integrity.ps1:110 Line | 110 | … viceWorkerAssetsResponse = Invoke-WebRequest $serviceWorkerAssetsUrl; |
~~~~~~~~~ | Error 404HTTP 404ApplicationInformation