[xperiandri]

Summary

Stacked on #55. The branch contains the commits of #55 and of the pull requests before it, so the last 2 commits are new here.

This pull request moves the package versions of both projects into Directory.Packages.props (central package management). It requires #55 (the edit is made on the SDK-style projects). The new commits are Move the package versions to central package management and Update the instructions for central package management; the extension 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 are stacked on each other. The branch of each one contains the commits of the earlier ones, so GitHub lists those commits here until the earlier pull requests are merged. All of them target main. Merge them 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 Add instructions, skills and MCP configuration for AI coding agents #54)
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) – this pull request
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)

Changes

• Directory.Packages.props holds one PackageVersion for each of the 19 packages, in three groups: the packages of the extension, the dependencies that the projects name explicitly, and the test packages. The two projects name the packages only. The versions are the ones the projects had; where both projects used a package they used the same version, so one entry replaces two.
• The file is added to the solution items, and the instructions say where the versions are.

Things to know

• A version is changed in one place now, and a project can still deviate with VersionOverride. Central package management needs NuGet 6.2 or later, which the build tools of this repository have.
• nuget.config (the package source mapping) is unchanged.

Verification

• The resolved packages are the same: project.assets.json lists the same 154 libraries for the extension and the same 162 for the tests, with the same entries for net481. In Debug and Release the references, the 26 distinct warnings, the VSIX entries and the fingerprints of both assemblies are identical to the previous commit, and the 4 tests pass (the MSBuild of Visual Studio 2026 18.12).
• The workflows of this repository wait for the approval of a maintainer on a pull request, so the commit ran in a fork. Build builds, tests and uploads a VSIX with the same 34 entries and sizes as the run for the previous pull request, and Copilot Setup Steps passes. The step Publish Test Results then fails, because the third-party action EnricoMi/publish-unit-test-result-action/windows@v2 finds no Python interpreter on the image (No python3 interpreter found); it fails in the same way on the unchanged code of main (run in the fork), so it is not caused by this change and not fixed here.

🤖 Generated with Claude Code