Open Closed

Runtime Pack error #9579


User avatar
0
Spospisil created

I'm getting the following error for my solution and I do a clean and build.

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

I've created a private repo on github and invited 'maliming' as a collaborator to it.

Markdown supported.
Copy, paste, or drag & drop images and files (max 100 MB per file, 100 MB total per post)

4 Answer(s)
  • User Avatar
    0
    AI-Bot created
    Support Team ABP Agent
    • The error "There was no runtime pack for Microsoft.AspNetCore.App available for the specified RuntimeIdentifier 'browser-wasm'" typically occurs when trying to use server-side or ASP.NET Core-specific packages in a Blazor WebAssembly (WASM) project. Blazor WASM runs on the client and does not support the full ASP.NET Core runtime, so references to Microsoft.AspNetCore.App or similar server-side packages should be avoided in the WASM project.

    • To resolve this:

      1. Ensure that your Blazor WASM project does not reference server-only packages like Microsoft.AspNetCore.App. Only the server (Host) project should reference these.
      2. If you are using a hosted Blazor solution (Blazor WASM + HttpApi.Host), make sure the WASM project only references client-compatible packages.
      3. Clean the solution and delete the bin and obj folders in all projects.
      4. Rebuild the solution.
    • If you are using a custom RuntimeIdentifier or have edited the project file, ensure that the Blazor WASM project targets net8.0 (or the correct .NET version) and does not set a RuntimeIdentifier like browser-wasm unless required by the template.

    • For a correct setup, see the official ABP Blazor WASM + ASP.NET Core Hosted integration steps:

      • Add the Blazor project reference and Microsoft.AspNetCore.Components.WebAssembly.Server package only to the Host project.
      • Use app.UseBlazorFrameworkFiles() and app.UseStaticFiles() in the Host's OnApplicationInitialization.
      • Do not add server-only dependencies to the WASM project.
    • If you have a private repo and have invited a collaborator, you can continue troubleshooting with them, but the above steps should resolve the runtime pack error.

    Sources:

    • https://abp.io/community/articles/zbjvgrc9
    • https://abp.io/docs/latest/tutorials/todo/single-layer/

    This response was generated by AI. If it didn’t solve your problem, feel free to post a new answer — our support team will jump in to help you soon.

    Markdown supported.
    Copy, paste, or drag & drop images and files (max 100 MB per file, 100 MB total per post)
  • User Avatar
    0
    Spospisil created

    I've tried everything suggested and still get the error. I've shared the repo where this issue can be seen. Make sure you're using the ABP_Issue branch.

    Markdown supported.
    Copy, paste, or drag & drop images and files (max 100 MB per file, 100 MB total per post)
  • User Avatar
    0
    maliming created
    Support Team Fullstack Developer

    hi Spospisil

    I have reproduced your problem. I will provide a solution soon.

    Thanks.

    Markdown supported.
    Copy, paste, or drag & drop images and files (max 100 MB per file, 100 MB total per post)
  • User Avatar
    0
    maliming created
    Support Team Fullstack Developer

    hi

    The CFData.Structure.Core is used Sdk="Microsoft.NET.Sdk.Web" as SDK.

    It can not be used in a WASM project.

    Can you try to remove this project from your CFData.Structure.Tenant.Licensing project?

    Or change CFData.Structure.Core to using Sdk="Microsoft.NET.Sdk"

    Thanks.

    Markdown supported.
    Copy, paste, or drag & drop images and files (max 100 MB per file, 100 MB total per post)
Boost Your Development
ABP Live Training
Packages
See Trainings
Mastering ABP Framework Book
The Official Guide
Mastering
ABP Framework
Learn More
Mastering ABP Framework Book
Made with ❤️ on ABP v10.8.0-preview. Updated on September 16, 2026, 14:50
1
ABP Assistant
🔐 You need to be logged in to use the chatbot. Please log in first.