Prevent Microsoft.AspNetCore.App.Internal.Assets from packing without framework assets

[Copilot]

• You've read the Contributor Guide and Code of Conduct.
• You've included unit or integration tests for your change, where applicable.
• You've included inline docs for your change, where applicable.
• There's an open issue for the PR that you are making. If you'd like to propose a new feature or change, please open an issue to discuss the change or find an existing issue.

Prevent incomplete Microsoft.AspNetCore.App.Internal.Assets packages.

Description

Microsoft.AspNetCore.App.Internal.Assets could successfully produce a NuGet package without its required Blazor framework assets when BuildNodeJS=false. The resulting package restored successfully but caused /_framework/blazor.web.js to return 404 at runtime.

This change ensures that an incomplete package is never emitted:

• The project is non-packable when BuildNodeJS=false, preserving intentional no-NodeJS and source-build configurations.
• Package validation runs only when the project remains packable, preserving platform-specific-only CI legs.
• Pack fails when any expected script or source map is absent.
• The final NuGet _PackageFiles list is checked for blazor.web.js, blazor.server.js, and both source maps before GenerateNuspec runs.
• The validation uses NuGet's BeforePack hook so input validation also runs when GenerateNuspec would otherwise be incrementally up-to-date.
• Existing package-layout coverage now verifies all four files in the produced archive.

Verification

• BuildNodeJS=false pack succeeds without producing a .nupkg.
• OnlyPackPlatformSpecificPackages=true pack succeeds without producing this RID-agnostic package.
• Explicit Build succeeds in both no-NodeJS and platform-specific-only configurations.
• Removing an expected source map makes pack fail without producing a package.
• JS-enabled pack produces exactly one package containing all four expected assets.
• AssetsInternalPackage_ShipsBlazorScriptsAndSourceMaps passes against the built package.

Fixes #68975

[Copilot]

🟢 Approval recommended

The changes directly enforce package integrity in the failing configuration and add corresponding automated package-layout coverage for the expected shipped assets.

Pull request overview

Prevents producing an incomplete Microsoft.AspNetCore.App.Internal.Assets NuGet package (notably when BuildNodeJS=false) by making the project non-packable in that configuration and adding pack-time validation to ensure required Blazor framework JS assets and source maps are present before packaging.

Changes:

• Marks Microsoft.AspNetCore.App.Internal.Assets as non-packable when BuildNodeJS=false and adds BeforePack/GenerateNuspec-time validation targets to fail packing if required assets are missing.
• Refactors asset item definitions to centralize the expected Blazor framework files in a single item list used by both packaging and validation.
• Extends package-layout tests to verify both .js files and their .map files are present in the produced package.

File summaries

File	Description
src/Assets/Microsoft.AspNetCore.App.Internal.Assets.csproj	Disables packing when NodeJS build is off and adds pack input/output validation to prevent emitting incomplete internal-assets packages.
src/Components/WebView/test/StaticWebAssets/PackageLayoutTests.cs	Updates packaging assertions to require the two Blazor scripts and their source maps in the internal-assets package.

Review details

• Files reviewed: 2/2 changed files
• Comments generated: 0
• Review effort level: Lite

---

💡 Add a code-review agent skill for context-aware, tailored reviews. Learn more in the docs.