Update ExpectedException analyzer message/description to use the new Assert.Throws methods (and fix typo) #4527
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
Evangelink
reviewed
Jan 6, 2025
…Assert.Throws methods
Youssef1313
force-pushed
the
expectedex-resources
branch
from
47dbe0d to
5d4f72b
Compare
Evangelink
approved these changes
Jan 6, 2025
Youssef1313
changed the title
|
The other extra changes were mostly already done in AreNotSame. They unintentionally ended up in this branch. Rebasing made them go away, and also adjusted the PR title as I also fixed a typo in the messages I'm modifying. |
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
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.
No description provided.