Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Error cases on security streams are handled differently, and successive calls to BeginAuthenticateAsServer or BeginAuthenticateAsClient may no longer fail.
Version introduced
5.0
Change description
In previous .NET versions, calling BeginAuthenticateAsServer or BeginAuthenticateAsClient successively without first calling EndAuthenticateAsServer or EndAuthenticateAsClient results in a NotSupportedException. Starting in .NET 5, successive calls to BeginAuthenticateAsServer or BeginAuthenticateAsClient no longer result in a NotSupportedException, because these APIs are backed by a Task-based implementation.
Reason for change
Switching the internal implementation from asynchronous programming model (APM) to Task-based improves performance and decreases code complexity.
Recommended action
No action is required on the part of the developer.
Affected APIs
Collaborate with us on GitHub
The source for this content can be found on GitHub, where you can also create and review issues and pull requests. For more information, see our contributor guide.
