Avoid TypeLoadExceptions in VS 2022 #34664
Merged
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
- This should be fixed when VS 2022 updates its Microsoft.CodeAnalysis.CSharp dependency
halter73
added
the
area-infrastructure
JamesNK
approved these changes
Jul 24, 2021
ghost
added this to the
This was referenced Jul 29, 2021
Merged
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 avoids errors like the following when building or testing in VS 2022:
I haven't filed an issue related to this since as far as I can tell, Microsoft.CodeAnalysis.CSharp.dll ships with VS. I don't see a realistic way to keep the latest SDKs we use in our repo always working with VS previews. Presumably this will resolve itself with VS updates.