Pin VS-compatible package versions for local dev#20016
Open
abonie wants to merge 1 commit into
Open
Conversation
Local (non-CI) workaround: the Roslyn/MSBuild package versions that flow in via Maestro run ahead of what ships in the currently-released Visual Studio, causing assembly version skew (see dotnet#18766). For local builds we pin these back to the last VS-compatible versions, CI keeps the Maestro-provided versions. Override AFTER the import so these win over the eager XxxVersion aliases
Contributor
✅ No release notes required |
github-actions
Bot
added
⚠️ Affects-Build-Infra
Contributor
|
🔍 Tooling Safety Check — Affects-Build-Infra, Affects-Restore
|
Member
Author
Contributor
|
If I don't need to do anything special after pulling, it doesn't. Maybe I'll need to do a full git clean... |
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
2 participants
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.
Local (non-CI) workaround: the Roslyn/MSBuild package versions that flow
in via Maestro run ahead of what ships in the currently-released
Visual Studio, causing assembly version skew
(see #18766).
For local builds we pin these back to the last VS-compatible versions, CI keeps the Maestro-provided versions.
Override AFTER the import so these win over the eager XxxVersion aliases