Align MSBuild package versions to 17.14.28 #228
Closed
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.
Four MSBuild-related packages in
Directory.Packages.propswere at version17.14.8whileMicrosoft.Build.Frameworkwas already at17.14.28.Changes:
Microsoft.Build.Tasks.Core:17.14.8→17.14.28Microsoft.Build.Utilities.Core:17.14.8→17.14.28Microsoft.Build:17.14.8→17.14.28Microsoft.NET.StringTools:17.14.8→17.14.28Original prompt
Update the
Microsoft.Build.Tasks.Core,Microsoft.Build.Utilities.Core, andMicrosoft.Buildpackage versions insrc/SourceBrowser/src/Directory.Packages.propsto17.14.28so they are consistent with the existingMicrosoft.Build.Frameworkreference.Current file contents at commit
15545241d04f32df12fdf0cd74c0c440848e10cd: