Stop updating VS PackageReferences on insertion #12663
Draft
+8
−19
Conversation
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
VSSDK packages have recently exposed a "live" dependency on MSBuild, which has caused several complications in the VS/MSBuild/VSSDK release process. In consultation with the VSSDK team, the plan for now is to pin to MSBuild's 18.0 package, so there's a known stable version to use. VSSDK consumers will have the option to locally reference a higher MSBuild but we suspect they are unlikely to need to do so. This can't be a full and final solution because eventually we'll introduce new API for VS to use and need to reference it in VS. At that time we'll need to disentangle the "public" and "internal" MSBuild references in VS.
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.
VSSDK packages have recently exposed a "live" dependency on MSBuild,
which has caused several complications in the VS/MSBuild/VSSDK release
process. In consultation with the VSSDK team, the plan for now is to pin
to MSBuild's 18.0 package, so there's a known stable version to use.
VSSDK consumers will have the option to locally reference a higher
MSBuild but we suspect they are unlikely to need to do so.
This can't be a full and final solution because eventually we'll
introduce new API for VS to use and need to reference it in VS. At that
time we'll need to disentangle the "public" and "internal" MSBuild
references in VS.
Related internal PR: https://dev.azure.com/devdiv/DevDiv/_git/VS/pullrequest/680433