Revert change from FxCopAnalyzers to NetAnalyzers #35108
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 reverts commit 6bf7b23. I've opened Azure#35107 to track reverting this reversion after the problem is fixed and working with internal teams to identify where that issue needs to be opened. This is causing Visual Studio to constantly run expensive background operations and slows it to a near-halt.
heaths
requested review from
hallipr,
weshaggard,
benbp,
paterasMSFT,
dpwatrous,
wiboris,
NickKouds,
bgklein,
JoshLove-msft,
christothes,
annelo-msft and
KrzysztofCwalina
as code owners
ghost
added
|
API change check API changes are not detected in this pull request. |
jsquire
approved these changes
Mar 23, 2023
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 reverts commit 6bf7b23. I've
opened #35107 to track reverting this reversion after the problem is
fixed and working with internal teams to identify where that issue needs
to be opened.
This is causing Visual Studio to constantly run expensive background
operations and slows it to a near-halt.