Repository navigation
Move the package versions to central package management - #56
Open
xperiandri wants to merge 4 commits into
Open
xperiandri wants to merge 4 commits into
xperiandri wants to merge 4 commits into
Conversation
`dotnet sln migrate` produced `StringResourceVisualizer.slnx` from `StringResourceVisualizer.sln`, and the old file is removed. The projects and the solution items are the same. The project ids are the ones of the old solution, which is what Visual Studio writes into the file itself. The `.slnx` format is XML, much shorter than the `.sln`, and designed to reduce merge conflicts (https://devblogs.microsoft.com/visualstudio/new-simpler-solution-file-format/). Building it needs the .NET SDK 9.0.200 or later, or MSBuild from Visual Studio or Build Tools 17.13 or later. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
This was referenced Oct 27, 2026
Both projects use `Microsoft.NET.Sdk` with `net481` now, and `VSSDKBuildToolsAutoSetup` with `Microsoft.VSSDK.BuildTools` 18.5 builds the VSIX. The source files are included by globbing; the extension project excludes the folder of the test project, which lies inside its own folder. `Properties\AssemblyInfo.cs` stays, because the version comes from the `Vsix` constants, and the output stays in `bin\Debug\` and `bin\Release\`. The signing target is called `SignAndCopyVsix` and runs after `Build`. As `AfterBuild` it would be replaced by the SDK targets and never run. The packages and their versions are the same, apart from the added `Microsoft.VSSDK.BuildTools`. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Visual Studio 2026 18.5 and later deploys an SDK-style VSIX project to the Experimental instance on F5 only when the solution has a `<Deploy>` element for it. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
`Directory.Packages.props` holds the version of each of the 19 packages, and the two projects name the packages only. The versions are the ones the projects had, so the resolved packages (154 for the extension, 162 for the tests) are the same as before. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
xperiandri
force-pushed
the
chain/central-packages
branch
from
October 29, 2026 01:18
089024e to
209ff12
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Stacked on #55. The branch contains the commits of #55 and of the pull requests before it, so the last 1 commit is new here.
This pull request moves the package versions of the two projects into one file,
Directory.Packages.props(central package management). It requires #55: it edits thePackageReferenceitems of the SDK-style project files that #55 creates. The matching update of the instructions is part of the last pull request of the chain (#69), because the instructions live in the files that #54 adds. The code does not change, and NuGet resolves the same packages as before.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:.slnxformat #53 – Switch the solution to the.slnxformat (first in the chain, no dependencies).slnxformat #53).slnxformat #53)dotnet build#58 – Build withdotnet build(stacked on Set the C# language version to 14 #57)dotnet build#69 – Update the instructions for the SDK-style projects, central package management, C# 14 anddotnet build(stacked on Build withdotnet build#58 and Add instructions, skills and MCP configuration for AI coding agents #54)Changes
Directory.Packages.propsholds onePackageVersionfor 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.Things to know
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
project.assets.jsonlists the same 154 libraries for the extension and the same 162 for the tests, with the same entries fornet481. InDebugandReleasethe 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).windows-2022runner:Buildbuilds the solution and runs the 4 tests, which pass. As on the unchangedmain(run), the stepPublish Test Resultsfails there: the third-party actionEnricoMi/publish-unit-test-result-actionfinds no Python interpreter on the image. This pull request neither causes nor changes it.🤖 Generated with Claude Code