Diagnose and fix Static Web Assets pack test assertion failures in .NET SDK.
npx skills add https://github.com/dotnet/dotnet --skill swa-pack-format
Please help me install this Agent Skill. Skill: swa-pack-format Source: https://github.com/dotnet/dotnet/tree/main/src/sdk/.claude/skills/swa-pack-format Command: npx skills add https://github.com/dotnet/dotnet --skill swa-pack-format
When MSBuild .targets logic changes, Static Web Assets pack tests fail because the produced nupkg contents no longer match test assertions, and tracing which MSBuild condition branch applies to a given TFM is tedious and error-prone.
Microsoft.NET.Sdk.StaticWebAssets.Pack.targets to determine which MSBuild condition branch fires for a test's TFM and configuration.NuPkgContainsPatterns and NuPkgContain assertions to exactly match the nupkg entries produced by the active branch.Fix the failing StaticWebAssetsPackIntegrationTest assertions by tracing the pack targets conditions for the test's TFM.
High-intent search queries and answers about installing and using this skill.
Identify the test's TFM from how it creates the test asset, then trace the Condition attributes in Microsoft.NET.Sdk.StaticWebAssets.Pack.targets to find the active branch. Update the NuPkgContainsPatterns or NuPkgContain assertions to exactly match that branch's nupkg entries.
Pack targets use Condition attributes on ItemGroup elements that branch on TFM version, feature flags, and asset presence. Each branch produces a different set of nupkg entries, so test assertions must match the branch activated by the test's configuration.
No. Tests explicitly targeting older TFMs verify backward compatibility and their assertions match the legacy nupkg format. Only update tests whose TFM activates the new condition branch; leave older-TFM tests untouched.
Changing conditions, file paths, or included items in pack targets alters the nupkg contents for every TFM branch the change affects. Any test asserting the old contents on those branches fails until its assertions are updated to the new expected entries.
Common asserted paths include build/ for build-time imports and manifests, buildMultiTargeting/ and buildTransitive/ for import files, and staticwebassets/ for the actual asset files. Assertions use glob patterns or exact path matching helpers.
dotnetGenerate unique binary log files for MSBuild and .NET builds.
BSchafer01Enumerate .NET TFMs and update references across apps, tests, and packaging.
christianhelleAudit NuGet analyzer package nuspec and nupkg contents for transitive and bundled assets.
sayalinvidiaAutomates NeMo-RL research campaigns with TSV logging and durable ledgers.