-
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
Is System.Net.Mail.SmtpClient obsolete in 4.7.2 and 4.8 ? #4114
Comments
See #2986 for prior discussion. SmtpClient is marked with ObsoleteAttribute in Xamarin/Mono, and due to docs site engine bug it causes the obsolete notice to be displayed for all frameworks. In .NET Framework/Core, it is not marked obsolete, but it's still considered legacy API (not updated to new protocol features). |
It has been a year already and the docs still say this is obsolete in Framework 4. Can't this be manually corrected? |
@dotnet/ncl - thoughts? |
There is no mention of obsoletion in the docs beside Xamarin when I open them: SmtpClient docs The Remarks section explicitly calls it out: The
|
The original question has been answered in the docs, closing. |
@karelz, the mention of obsolete in the docs is in the first paragraph (under Definition): |
OK, that was missing in the original report - the link wasn't there and the text quoted was slightly different. Reopening. I think we can change the text to "The SmtpClient type is now obsolete on some platforms and not recommended on others - see Remarks for details." |
@karelz, that sounds much better. I believe that should clarify things sufficiently. Hopefully, the original poster agrees with me. Thank you for your quick response. |
I can't see any trace of
System.Obsolete
inside the code of SmtpClient.cs. Does this mean that this class is not obsolete?Because in docs.microsoft.com it states clearly, This API is now obsolete.
The text was updated successfully, but these errors were encountered: