[Blazor] Remove unnecessary update to the Blazor webassembly js file

[javiercn]

[Blazor] Remove unnecessary update to the Blazor webassembly js file

Remove redundant blazor.webassembly.js update that broke publish

Description

Hosted webassembly apps failed to publish due to a bug in how we were trying to update the blazor.webassembly.js asset definition. We realized that we did not have to do so, but that there was a bug precluding us from finding the asset during the publish process.

The fix corrects the identity of the blazor.webassembly.js to account for the fingerprint for the file we introduced in 10.0, which wasn't being taken into account.

Fixes #119886

Customer Impact

Customers with a hosted Blazor WebAssembly + Web API (Server) solution failed to publish. There is no straightforward user workaround short of editing writing a significant amount of MSBuild to work around the issue.

Regression?

• Yes
• No

Regressed from .NET 8 (publishing the same project type succeeded in 8.x).

Risk

• High
• Medium
• Low

Justification: The change only removes an unnecessary build step and fixes a case that was exclusively related to Blazor webassembly. It does not alter the contents of the delivered script, pipeline ordering, or introduce new logic— it simply stops creating an anomalous asset entry. Existing publish & static web asset tests still apply. Low surface area and isolated to Blazor WASM publish scenario.

Verification

• Manual (required)
  • Reproduced failure with unpatched SDK (publish fails).
  • Applied change; publish succeeds
• Automated

Packaging changes reviewed?

• Yes
• No
• N/A

[maraf]

StaticWebAsset identity for fingerprinted blazor.js is correct

[javiercn]

This unrelated test seems to be failing continuously:
https://github.com/dotnet/sdk/blame/3581345c8d0770d4fc2713038056dc6dd376db37/test/Microsoft.NET.Publish.Tests/GivenThatWeWantToPublishIncrementally.cs#L138

Sample failure here:
https://dev.azure.com/dnceng-public/public/_build/results?buildId=1154760&view=ms.vss-test-web.build-test-results-tab&runId=31900102&resultId=112582&paneView=debug

[lewing]

This unrelated test seems to be failing continuously: https://github.com/dotnet/sdk/blame/3581345c8d0770d4fc2713038056dc6dd376db37/test/Microsoft.NET.Publish.Tests/GivenThatWeWantToPublishIncrementally.cs#L138

Sample failure here: https://dev.azure.com/dnceng-public/public/_build/results?buildId=1154760&view=ms.vss-test-web.build-test-results-tab&runId=31900102&resultId=112582&paneView=debug

I see the same failure on an unrelated pr https://github.com/dotnet/sdk/pull/50948/checks?check_run_id=50914392897 so I'm comfortable it is not related to this change. I do wonder when it regressed though. cc @marcpopMSFT

[lewing]

/backport to release/10.0.1xx-rc2

[github-actions]

Started backporting to release/10.0.1xx-rc2: https://github.com/dotnet/sdk/actions/runs/17931765331