based on the suggestion in https://github.com/microsoft/dotnet-apiport/issues/851 I ran Roselyn analyzer on my project. It did not spot System.DirectoryServices.AccountManagement as not supported. However it spotted TcpClient and SmtpClient as being deprecated, which - to the extend I tested so far - work on .NET Core 3.1 on linux/Docker.
Is this just a bug in the tool? Or a missing annotation in the package?
Is this information looking at future release or really at the release I am using?
if an Api is marked as deprecated, what about providing replacement suggestions?
based on the suggestion in https://github.com/microsoft/dotnet-apiport/issues/851 I ran Roselyn analyzer on my project. It did not spot System.DirectoryServices.AccountManagement as not supported. However it spotted TcpClient and SmtpClient as being deprecated, which - to the extend I tested so far - work on .NET Core 3.1 on linux/Docker.
Ok, I checked https://docs.microsoft.com/en-us/dotnet/api/system.net.mail.smtpclient?view=netframework-4.8 and got the recommendation for MailKit (I am hesitating to follow that because I don´t need any of the extra features and SmtpClient given my use case was working fine for years)). For TcpClient I am lacking any recommendation..
Please advise.
Thanks, Joachim