Description
Multiple BlazorWasm Static Web Assets integration tests and the BlazorWasm global usings test fail due to the Microsoft.Extensions.*.Abstractions inbox change (dotnet/dotnet#5206) that baked into the bootstrap SDK.
Static Web Assets baseline failures
The BlazorWasm SWA integration tests compare generated manifests against stored JSON baselines. The Extensions inbox change alters the set of DLLs that appear as WASM framework assets (e.g., compressed .wasm.gz/.wasm.br variants), causing the baselines to drift.
Fix: Regenerate baselines with ASPNETCORE_TEST_BASELINES=true using a bootstrap SDK that includes the inbox change.
CS0012 compilation failure
GivenThatWeWantToGenerateGlobalUsings_BlazorWasm.It_generates_blazorwasm_usings_and_builds_successfully fails with CS0012 because the test references Microsoft.AspNetCore.Components.WebAssembly v5.0.0 against net11.0. Types from Microsoft.Extensions.* assemblies that moved inbox are no longer resolvable through the old package's assembly references.
Affected Tests
BlazorWasmStaticWebAssetsIntegrationTest.StaticWebAssets_Build_Hosted_WorksBlazorWasmStaticWebAssetsIntegrationTest.StaticWebAssets_BuildMinimal_WorksBlazorWasmStaticWebAssetsIntegrationTest.StaticWebAssets_Publish_Hosted_WorksBlazorWasmStaticWebAssetsIntegrationTest.StaticWebAssets_PublishMinimal_WorksBlazorWasmStaticWebAssetsIntegrationTest.StaticWebAssets_Publish_DoesNotIncludeXmlDocumentationFiles_AsAssetsGivenThatWeWantToGenerateGlobalUsings_BlazorWasm.It_generates_blazorwasm_usings_and_builds_successfully
Build
https://dev.azure.com/dnceng-public/public/_build/results?buildId=1373051
Helix job: d9fc0bd3-ff11-45e2-aa54-6c468495f55d, work item: Microsoft.NET.Sdk.BlazorWebAssembly.Tests.dll.1
Description
Multiple BlazorWasm Static Web Assets integration tests and the BlazorWasm global usings test fail due to the
Microsoft.Extensions.*.Abstractionsinbox change (dotnet/dotnet#5206) that baked into the bootstrap SDK.Static Web Assets baseline failures
The BlazorWasm SWA integration tests compare generated manifests against stored JSON baselines. The Extensions inbox change alters the set of DLLs that appear as WASM framework assets (e.g., compressed
.wasm.gz/.wasm.brvariants), causing the baselines to drift.Fix: Regenerate baselines with
ASPNETCORE_TEST_BASELINES=trueusing a bootstrap SDK that includes the inbox change.CS0012 compilation failure
GivenThatWeWantToGenerateGlobalUsings_BlazorWasm.It_generates_blazorwasm_usings_and_builds_successfullyfails with CS0012 because the test referencesMicrosoft.AspNetCore.Components.WebAssemblyv5.0.0 against net11.0. Types fromMicrosoft.Extensions.*assemblies that moved inbox are no longer resolvable through the old package's assembly references.Affected Tests
BlazorWasmStaticWebAssetsIntegrationTest.StaticWebAssets_Build_Hosted_WorksBlazorWasmStaticWebAssetsIntegrationTest.StaticWebAssets_BuildMinimal_WorksBlazorWasmStaticWebAssetsIntegrationTest.StaticWebAssets_Publish_Hosted_WorksBlazorWasmStaticWebAssetsIntegrationTest.StaticWebAssets_PublishMinimal_WorksBlazorWasmStaticWebAssetsIntegrationTest.StaticWebAssets_Publish_DoesNotIncludeXmlDocumentationFiles_AsAssetsGivenThatWeWantToGenerateGlobalUsings_BlazorWasm.It_generates_blazorwasm_usings_and_builds_successfullyBuild
https://dev.azure.com/dnceng-public/public/_build/results?buildId=1373051
Helix job:
d9fc0bd3-ff11-45e2-aa54-6c468495f55d, work item:Microsoft.NET.Sdk.BlazorWebAssembly.Tests.dll.1