There was no runtime pack for Microsoft.AspNetCore.App available for the specified RuntimeIdentifier 'browser-wasm'.

Hello,

When I migrated my Asp.net Core 3.1 Hosted Blazor Webassembly Project to .Net 5 (Client, Server, Shared) I started to get at Server project below error message:

There was no runtime pack for Microsoft.AspNetCore.App available for the specified RuntimeIdentifier ‘browser-wasm’. and directs me there: `

ResolveRuntimePackAssets

Resolve assets from runtime packs.

–> <ResolveRuntimePackAssets FrameworkReferences="@(FrameworkReference)" ResolvedRuntimePacks="@(ResolvedRuntimePack)" UnavailableRuntimePacks="@(UnavailableRuntimePack)" SatelliteResourceLanguages="$(SatelliteResourceLanguages)" DesignTimeBuild="$(DesignTimeBuild)"> <Output TaskParameter="RuntimePackAssets" ItemName="RuntimePackAsset" /> </ResolveRuntimePackAssets>

<ItemGroup> <ReferenceCopyLocalPaths Include="@(RuntimePackAsset)" Condition="'$(CopyLocalLockFileAssemblies)' == 'true' and ('$(SelfContained)' == 'true' or '%(RuntimePackAsset.RuntimePackAlwaysCopyLocal)' == 'true')" /> </ItemGroup> `

When I bring back Project Sdk=“Microsoft.NET.Sdk.BlazorWebAssembly” to Project Sdk=“Microsoft.NET.Sdk.Web” in Server project file it seems to compile successfully but the client does not render properly.

Why this is happening?

Same issue was addressed in StockExchange: https://stackoverflow.com/questions/63993294/there-was-no-runtime-pack-for-microsoft-aspnetcore-app-available-for-the-specifi

but I don’t see them having a fitting solution for me.

Thanks,

Describe the bug

A clear and concise description of what the bug is.

To Reproduce

Exceptions (if any)

Further technical details

• ASP.NET Core version .Net 5.0
• Include the output of dotnet --info dotnet info.txt
• The IDE (VS / VS Code/ VS4Mac) you’re running on, and it’s version Visual Studio 2019 16.8

[pranavkm]

@ozanyasindogan could you verify this is what your projects’ SDKs look like:

• Client - Microsoft.NET.Sdk.BlazorWebAssembly
• Server - Microsoft.NET.Sdk.Web
• Shared - Microsoft.NET.Sdk

@guardrex looking at the SO responses, there might be some confusion about what projects need the SDK to be updated. Do we need to tweak our migration guides to make this clearer: https://docs.microsoft.com/en-us/aspnet/core/migration/31-to-50?view=aspnetcore-3.1&tabs=visual-studio#update-blazor-webassembly-projects?

[pranavkm]

Hi, it’s not helpful to comment on a closed issue as it is very easy for us to miss these notifications. If you’re having issues migrating what would help is to file a new issue, include the contents of your app’s project files, and any errors you see during the build when you update the app. Thanks!