-
Notifications
You must be signed in to change notification settings - Fork 1.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Added Include note about class being obsolete #10015
Conversation
This comment was marked as outdated.
This comment was marked as outdated.
@lorieide What's the motivation behind this PR? |
@gewarren Sure. I've been assigned this GitHub issue to resolve MicrosoftDocs/azure-docs#111552 |
@gewarren Here's what I found: |
This comment was marked as outdated.
This comment was marked as outdated.
@lorieide Ahh, okay. Currently, if a .NET API is marked with the ObsoleteAttribute, for example, WebRequest.Create, then the API reference docs automatically show the CAUTION block with the text from the ObsoleteAttribute. So that's why you see the info on some APIs and not others. There's also a work item to propagate the obsolete warning to all members of a type that's marked obsolete (although I don't think that applies to any of these 4 System.Net types unfortunately). Related to #6867. |
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
Learn Build status updates of commit 409844e: ✅ Validation status: passed
For more details, please refer to the build report. For any questions, please:
|
FYI |
Learn Build status updates of commit f9a8675: ✅ Validation status: passed
For more details, please refer to the build report. For any questions, please:
|
Summary
Describe your changes here.
Fixes #Issue_Number (if available)