[release/7.0] Correct [Obsolete] message for AutoTransactionBehavior #30040
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
Fixes dotnet#29990 (cherry picked from commit ac98b60)
roji
force-pushed
the
AutoTranasctionBehavior7.0
branch
from
9a596a9
to
137039b
Compare
roji
changed the title
ajcvickers
approved these changes
Jan 12, 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.
Fixes #29990, backports #29991
Description
An [Obsolete] attribute message points to the wrong replacement API.
Customer impact
It's harder for users to figure out which new API to use instead of the obsoleted API.
How found
Customer report on 7.0.
Regression
No.
Testing
No testing necessary, this is a pure string message fix.
Risk
Zero; this is a pure obsoletion message fix.