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

Question

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

Prathamesh Shende 551

I am facing this issue
There was no runtime pack for Microsoft.AspNetCore.App available for the specified RuntimeIdentifier 'browser-wasm'. in .net 8 version my project is Blazor Web App the blazor client side project is not working and throwing the error.

I have tried every step like deleting the bin obj folders, dotnet clean, dotnet restore but still it is not working.

how do i find where the issue is?

Please help

Deleted

This comment has been deleted due to a violation of our Code of Conduct. The comment was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.

Answer accepted by question author

AgaveJoe 31,706

I think the issue is this property in your .csproj:

<GenerateRuntimeConfigurationFiles>true</GenerateRuntimeConfigurationFiles>

This setting is intended for server or desktop applications (e.g., Web API, Console) where the host needs to produce a .runtimeconfig.json for the OS runtime.

Try removing that line from your project file, run dotnet clean, and try building again.

Prathamesh Shende 551 Reputation points

2026-08-15T03:45:28.8766667+00:00

works after deleting this. Thank you so much

4 additional answers

Your answer

Deleted

This comment has been deleted due to a violation of our Code of Conduct. The comment was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
Prathamesh Shende 551 Reputation points

2026-08-15T03:45:28.8766667+00:00

works after deleting this. Thank you so much

Answer 1

Bruce (SqlWork.com) 85,276

as stated the browser-wasm runtime (mono) does not support the Microsoft.AspNetCore.App package. Most likely your project is referencing a library or nuget package that is dependent on Microsoft.AspNetCore.App.

Prathamesh Shende 551

I have checked all my csproj there is no Microsoft.AspNetCore.App this is my csproj

<Project Sdk="Microsoft.NET.Sdk.BlazorWebAssembly">

	<PropertyGroup>
		<TargetFramework>net8.0</TargetFramework>
		<ImplicitUsings>enable</ImplicitUsings>
		<Nullable>enable</Nullable>
		<NoDefaultLaunchSettingsFile>true</NoDefaultLaunchSettingsFile>
		<StaticWebAssetProjectMode>Default</StaticWebAssetProjectMode>
		<GenerateRuntimeConfigurationFiles>true</GenerateRuntimeConfigurationFiles>
	</PropertyGroup>

	<ItemGroup>
		<PackageReference Include="Blazor.ContextMenu" Version="2.1.0" />
		<PackageReference Include="Blazored.LocalStorage" Version="4.5.0" />
		<PackageReference Include="Blazored.SessionStorage" Version="2.4.0" />
		<PackageReference Include="Blazored.TextEditor" Version="1.1.3" />
		<PackageReference Include="EPPlus" Version="8.0.6" />
		<PackageReference Include="IdentityModel" Version="6.0.0" />
		<PackageReference Include="IndexedDB.Blazor" Version="1.1.1" />
		<PackageReference Include="Markdig" Version="1.3.2" />
		<PackageReference Include="Microsoft.AspNetCore.Components.WebAssembly" Version="8.0.30" />
		<PackageReference Include="Microsoft.AspNetCore.Components.WebAssembly.Authentication" Version="8.0.30" />
		<PackageReference Include="Microsoft.AspNetCore.SignalR.Client" Version="8.0.30" />
		<PackageReference Include="Microsoft.Extensions.Http" Version="8.0.1" />
		<PackageReference Include="QRCoder" Version="1.8.0" />
		<PackageReference Include="Tewr.Blazor.FileReader" Version="3.4.0.24340" />
	</ItemGroup>


</Project>

Bruce (SqlWork.com) 85,276 Reputation points

2026-08-14T22:35:14.6366667+00:00

you might check "IdentityModel", as its not a standard nuget package.

Also check if you are using a razor component library that it does not have server (browser) support.:

<SupportedPlatform Include="browser" />

Note: it’s also time to upgrade to.net 10, .net 8 support ends in November. Like mobile, blazor changes pretty fast and you should be on a current release.

Answer 2

Hello @Prathamesh Shende ,

Thanks to AgaveJoe for the correct answer! The issue stems from having the <GenerateRuntimeConfigurationFiles>true</GenerateRuntimeConfigurationFiles> property in your Blazor WebAssembly .csproj file.

This setting instructs the .NET build system to emit a .runtimeconfig.json file. This configuration file is strictly meant for traditional applications (like ASP.NET Core Web APIs, Console Apps, or Desktop Apps) to tell the host environment which OS-specific runtime environment to load.

Blazor WebAssembly operates in a completely different hosting model. It runs entirely inside the browser's sandbox using the WebAssembly runtime (browser-wasm). It does not use a .runtimeconfig.json file, and there is no traditional server-side Microsoft.AspNetCore.App runtime pack built for browser-wasm.

By setting this flag to true, you are explicitly forcing the build process to look for and resolve a server/desktop-style runtime pack for the browser environment. Since one doesn't exist, the build pipeline fails with the There was no runtime pack for Microsoft.AspNetCore.App available error.

Hope this helps clarify your issue.

Answer 3

Prathamesh Shende 551

FrameworkReference Include="Microsoft.AspNetCore.App" is not present. I have also tried the dotnet nuget locals all --clear but still not working

0 comments

Answer 4

This error usually means a WebAssembly client build is trying to pull in the server-side shared framework Microsoft.AspNetCore.App.

For browser-wasm, there is no runtime pack for Microsoft.AspNetCore.App, because that shared framework is for ASP.NET Core server apps, not Blazor WebAssembly runtime.

Since bin, obj, dotnet clean, and dotnet restore were already tried, focus on finding where the client project is bringing in the server framework.

Check the client project file (.csproj)
- Look for any explicit FrameworkReference to Microsoft.AspNetCore.App.
- If present, remove it.
- The client project should not reference the server shared framework.
Check project references from the client project
- If the Blazor WebAssembly client references a server or Minimal API project directly, that can bring in Microsoft.AspNetCore.App.
- The client should call the API over HTTP instead of referencing the API project directly.
Verify the server project type
- A Minimal API or ASP.NET Core server project can use the web SDK and server runtime.
- That server project should target a server runtime, not browser-wasm.
Check the RuntimeIdentifier
- If the client project uses browser-wasm, that is expected for WebAssembly.
- If another referenced project also ends up being evaluated with that RID, the build can fail because Microsoft.AspNetCore.App has no browser-wasm runtime pack.
If a package or reference depends on an incompatible runtime
- A package can fail when it does not support the project RuntimeIdentifier.
- Review package and project references used by the client and remove anything intended only for server hosting.
If the RID itself is custom or invalid
- Make sure the RuntimeIdentifier is recognized.
- In .NET 8 and later, prefer portable RIDs instead of version-specific or distro-specific RIDs.
If restore/build state is inconsistent
- Delete bin and obj again.
- Clear NuGet caches with dotnet nuget locals all --clear.
- Restore and rebuild.

What to look for first in this specific case:

FrameworkReference Include="Microsoft.AspNetCore.App" in the client project
A project reference from the client to a server/Minimal API project
Shared code placed in a server project instead of a separate class library

A common fix is to move shared models/interfaces into a plain class library, keep the API in the server project, and let the WebAssembly client consume the API via HTTP.