Aspnetcore: Blazor WASM PWA built on net5.0 preview 8 not generating service-worker-assets.js

[houstonhaynes]

Describe the bug

When attempting to build a Blazor WASM client using net5.0 preview 8 objDebugnet5.0browser-wasmservice-worker-assets.js is not being built

To Reproduce

See repo

https://github.com/houstonhaynes/BlazorError_dotnet5

Exceptions (if any)

Error MSB3954 Failed to compute hash for file 'objDebugnet5.0browser-wasmservice-worker-assets.js' because it does not exist or is inaccessible. SPA1.Client C:Usersh3tec.nugetpackagesmicrosoft.aspnetcore.components.webassembly.build5.0.0-preview.6.20312.15targetsServiceWorkerAssetsManifest.targets 59

Further technical details

• ASP.NET Core version 5.0 preview 8
• VS Community Version 16.8.0 Preview 2.1

[javiercn]

@houstonhaynes thanks for contacting us.

Can you try with the nightly builds to see if this is still an issue for you? The build pipeline has undergone significant changes and it might have been fixed in a later preview.

[houstonhaynes]

Will do. I'll report findings after updating and rebuilding.

I noticed the csproj forces the specific build number after wildcarding at 8(*) -- which strikes me as a bit high-touch for these scenarios.

Would be nice if the wildcarfing stayed in place.

[houstonhaynes]

@javiercn I'm pulling the installer from here

Yielding this installer : dotnet-sdk-5.0.100-rc.2.20458.7-win-x64

and getting this error

NETSDK1112 The runtime pack for Microsoft.NETCore.App.Runtime.browser-wasm was not downloaded. Try running a NuGet restore with the RuntimeIdentifier 'browser-wasm'. SPA1.Client C:\Program Files\dotnet\sdk\5.0.100-rc.2.20458.7\Sdks\Microsoft.NET.Sdk\targets\Microsoft.NET.Sdk.FrameworkReferenceResolution.targets
which runtime should I be using? what am I mising? I have to admit it's been years since I've dabbled with daily builds in .NET so I plead no lo contedre if I missed a step.

[pranavkm]

@houstonhaynes removing the WebAssembly.Build package allows the project to build using the preview8 SDK. There's more juggling involved when migrating to the rc1 SDK that we will include as part of release notes. Until then, I'll recommend staying with a publicly released SDK.

[pranavkm]

For our preview releases, we use our release notes to document migration guides. For e.g. if you look at our preview7 release notes - https://devblogs.microsoft.com/aspnet/asp-net-core-updates-in-net-5-preview-7/#upgrade-existing-blazor-webassembly-projects it tells you to remove the Build package.

I also sent a PR to your repo https://github.com/houstonhaynes/BlazorError_dotnet5/pull/1 after verifying that removing the package actually causes the project to build and run.

[houstonhaynes]

Still doesn't build.

Thanks for all of the super helpful advice.

[houstonhaynes]

Final note: it's poor form to close someone's issue when the original author has not confirmed the fix.

Check that into your process repo...

[szalapski]

I am having a similar issue, but my error is C:\Program Files\dotnet\sdk\5.0.100-rc.1.20452.10\Sdks\Microsoft.NET.Sdk\targets\Microsoft.NET.Sdk.FrameworkReferenceResolution.targets(379,5): error NETSDK1082: There was no runtime pack for Microsoft.AspNetCore.App available for the specified RuntimeIdentifier 'browser-wasm'. Not sure if it is related. Here is a link in case it helps: https://stackoverflow.com/questions/63993294/there-was-no-runtime-pack-for-microsoft-aspnetcore-app-available-for-the-specifi