diff --git a/docs/framework/network-programming/best-practices-for-system-net-classes.md b/docs/framework/network-programming/best-practices-for-system-net-classes.md index 1d35629a33edd..9d4b67dc2b73f 100644 --- a/docs/framework/network-programming/best-practices-for-system-net-classes.md +++ b/docs/framework/network-programming/best-practices-for-system-net-classes.md @@ -26,6 +26,8 @@ ms.workload: # Best Practices for System.Net Classes The following recommendations will help you use the classes contained in to their best advantage: +- For Transport Layer Security (TLS) best practices, see [Transport Layer Security (TLS) best practices with .NET Framework](tls.md). + - Use and whenever possible instead of type casting to descendant classes. Applications that use **WebRequest** and **WebResponse** can take advantage of new Internet protocols without needing extensive code changes. - When writing ASP.NET applications that run on a server using the **System.Net** classes, it is often better, from a performance standpoint, to use the asynchronous methods for and .