Skip to content

Visual Studio Insiders blocks ASP.NET builds on unmatched scoped CSS endpoints #70014

Open

Agent suggestions

Public preview

Description

@vsfeedback

This issue has been moved from a ticket on Developer Community.


[regression] [worked-in:VS 2026 Insiders 12224.323]
After Visual Studio Insiders 2026 I'm not able to compile the application because of the issue:

the following scoped css bundles do not have matching endpoints: _framework/microsoft.net.sdk.blazorweb.dotnetwatch#[.{fingerprint}]!.lib.module.js

If I create the new ASP.NET Web API project I'm getting the same issue.

IntegraService.csproj

I'm attaching .csproj which has problem with this.
After rollback everything works fine.


Original Comments

Feedback Bot on 15/10/2026, 07:45 AM:

Based on similar issues resolved with Microsoft in the last 6 months, the following can help resolve this issue faster.

Possible workarounds

Continue using the previous Visual Studio version that builds the project successfully, as reported. Also test the latest available Visual Studio Insiders build to determine whether the regression has been corrected.

If not already included, please provide:

Detected: VS: Visual Studio Insiders 2026, Project type: ASP.NET Web API, Category: .NET

  • What exact Visual Studio version/build reproduces the issue, and which previous version works?
  • What .NET SDK version is installed, and is a global.json present? Please include its contents if applicable.
  • Does the failure occur with both Build and Rebuild, and does dotnet build from a command prompt fail with the same message?
  • Please provide the complete build output and, if possible, a binary log from the failing build.
  • Please confirm the exact steps to reproduce this in the new ASP.NET Web API project and whether it reproduces every time.

Feedback Bot on 15/10/2026, 09:18 AM:

We have directed your feedback to the appropriate engineering team for further evaluation. The team will review the feedback and notify you about the next steps.

Gyorgy Koszeg on 19/10/2026, 02:42 PM:

I had the same issue. Confirming that a rollback to 12224.323 solves the problem.

Activity

  1. added this to the Backlog milestone on Oct 23, 2026
  2. MihuBot commented on Oct 23, 2026

    @MihuBot
  3. github-actions commented on Oct 23, 2026

    @github-actions
    Contributor

    Triage Summary

    Area: area-blazor (already applied; error references _framework/...blazorweb.dotnetwatch...lib.module.js scoped CSS/static web asset endpoints)
    Type: Bug (build fails with an error message on a project that built previously)

    Regression Info

    • Previously working version: Visual Studio 2026 Insiders 12224.323 (per reporter)
    • Failing version: not stated (only "after Visual Studio Insiders 2026")
    • Reported but unconfirmed regression: the reporter says rolling back to 12224.323 resolves the error. The failing VS build and the .NET SDK version are missing.

    Potential Duplicates

    Notes

    • Missing: failing VS build number, .NET SDK version (and global.json if any), whether dotnet build from the command line gives the same error, and a binary log of the failing build.

    Generated by Issue Triage Agent for dotnet/aspnetcore for #70014 · copilot · auto · 19.9 AIC · ⌖ 1.01 AIC · ⊞ 30.5K · ◷

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Author: Migration Bot 🤖The issue was created by a issue mover bot. The author may not be the actual author.area-blazorIncludes: Blazor, Razor Components

    Type

    No type

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions