Use precise assembly version for analyzers project #1266
Merged
Conversation
This file contains 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
This removes an MSBuild property that makes version calculating happen only once per build, under the (incorrect) assumption that only one version.json file exists in this repo. But the analyzers project has a unique one, and this msbuild property was causing that to be ignored.
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
RyanToth3
approved these changes
Jan 5, 2024
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.
This removes an MSBuild property that makes version calculating happen only once per build, under the (incorrect) assumption that only one version.json file exists in this repo. But the analyzers project has a unique one, and this msbuild property was causing that to be ignored.
See also microsoft/vs-mef#437 for a similar bug and fix.