[xperiandri]

Summary

Stacked on #57. The branch contains the commits of #57 and of the pull requests before it, so the last 1 commit is new here.

This pull request builds the solution with dotnet build instead of the MSBuild of Visual Studio in the build workflow. It requires #55: the SDK-style projects build with the .NET SDK, the old-style ones relied on the VSSDK targets that Visual Studio installs. It sits behind #57 only for the order of the commits. The same change in copilot-setup-steps.yml and the instructions are part of the last pull request of the chain (#69), because those files come with #54. The code does not change.

Chain, changes, things to know and verification

Chain

This pull request is part of a chain of small pull requests that all target main. After #53 the chain has two branches that do not depend on each other: the AI agent files (#54) and the modernization of the build (#55 to #58). The last pull request (#69) merges both and updates the instructions, which live in the files of the AI branch. The branch of each pull request contains the commits of the ones it is stacked on, so GitHub lists those commits here until they are merged. Merge in this order and review only the commits that are new in each pull request:

1. Switch the solution to the .slnx format #53 – Switch the solution to the .slnx format (first in the chain, no dependencies)
2. Add instructions, skills and MCP configuration for AI coding agents #54 – Add instructions, skills and MCP configuration for AI coding agents (stacked on Switch the solution to the .slnx format #53)
3. Convert the projects to the SDK style #55 – Convert the projects to the SDK style (stacked on Switch the solution to the .slnx format #53)
4. Move the package versions to central package management #56 – Move the package versions to central package management (stacked on Convert the projects to the SDK style #55)
5. Set the C# language version to 14 #57 – Set the C# language version to 14 (stacked on Move the package versions to central package management #56)
6. Build with dotnet build #58 – Build with dotnet build (stacked on Set the C# language version to 14 #57) – this pull request
7. Update the instructions for the SDK-style projects, central package management, C# 14 and dotnet build #69 – Update the instructions for the SDK-style projects, central package management, C# 14 and dotnet build (stacked on Build with dotnet build #58 and Add instructions, skills and MCP configuration for AI coding agents #54)

Changes

• .github/workflows/build.yaml runs dotnet build ./StringResourceVisualizer.slnx --configuration ${{ env.Configuration }} -p:OutDir=\_built -v:m; the step that made MSBuild available (timheuer/bootstrap-dotnet with msbuild: 'true') is gone. The version stamp, the artifact upload and the test steps are unchanged.

Things to know

• dotnet build works for this repository because the SDK-style projects use no private Visual Studio assemblies, no COM references and no binary resources. It needs the .NET SDK 9.0.200 or later for the .slnx; the language version asks for 10 anyway.
• The deployment to the Experimental instance is Visual Studio's job (F5).

Verification

• dotnet build with the .NET SDK 10.0.402 and the MSBuild of Visual Studio 2026 give the same result in Debug and Release: the same VSIX entries and sizes, identical extension.vsixmanifest, pkgdef and content types, identical assembly fingerprints, the same 26 distinct warnings, and the 4 tests pass.
• CI: the workflows of this repository wait for the approval of a maintainer on a pull request from a fork, so the commit ran in a fork on a clean windows-2022 runner: Build builds the solution with dotnet build and runs the 4 tests, which pass. As on the unchanged main (run), the step Publish Test Results fails there: the third-party action EnricoMi/publish-unit-test-result-action finds no Python interpreter on the image. This pull request neither causes nor changes it.

🤖 Generated with Claude Code

• After the chain was re-cut so that this pull request no longer contains the files of Add instructions, skills and MCP configuration for AI coding agents #54, the tip was built again locally with the MSBuild of Visual Studio 2026 (no errors, the same distinct warnings as the pull request before it), and with dotnet build.