Remove bad link (#10569)

gewarren · web-flow · commit 25c8d2620bce · 2024-10-16T07:43:24.000-07:00
diff --git a/xml/System.IO/PathTooLongException.xml b/xml/System.IO/PathTooLongException.xml
@@ -59,37 +59,19 @@
     </Attribute>
   </Attributes>
   <Docs>
-    <summary>The exception that is thrown when a path or fully qualified file name is longer than the system-defined maximum length.</summary>
+    <summary>The exception that's thrown when a path or fully qualified file name is longer than the system-defined maximum length.</summary>
     <remarks>
       <format type="text/markdown"><![CDATA[
 
 ## Remarks
- In apps that run under versions of the .NET Framework prior to the .NET Framework 4.6.2, full paths must not exceed 260 characters to maintain compatibility with Windows operating systems. Any path in excess of 260 characters automatically throws a <xref:System.IO.PathTooLongException>. For more information about this restriction, see the entry [Long Paths in .NET](https://go.microsoft.com/fwlink/?LinkID=163666) in the BCL Team blog.
 
 > [!NOTE]
->  This exception is not included in [.NET for Windows Store apps](https://go.microsoft.com/fwlink/?LinkID=247912) or the [Portable Class Library](/dotnet/standard/cross-platform/cross-platform-development-with-the-portable-class-library), but it is thrown by some members that are. To catch the exception in that case, write a `catch` statement that handles an <xref:System.IO.IOException> instead.
+> This exception is not included in [.NET for Windows Store apps](https://go.microsoft.com/fwlink/?LinkID=247912) or the [Portable Class Library](/dotnet/standard/cross-platform/cross-platform-development-with-the-portable-class-library), but it is thrown by some members that are. To catch the exception in that case, write a `catch` statement that handles an <xref:System.IO.IOException> instead.
 
- Starting with apps running under the .NET Framework 4.6.2, the .NET Framework supports long paths in excess of 260 (or `MAX_PATH`) characters.  The conditions under which a <xref:System.IO.PathTooLongException> exception are thrown depend on the version of the .NET Framework that an app targets:
+ Starting with apps running under .NET Framework 4.6.2, .NET supports long paths in excess of 260 (or `MAX_PATH`) characters. The runtime throws a <xref:System.IO.PathTooLongException> under the following conditions:
 
- **Apps that target the .NET Framework 4.6.2 and later versions**
- Long paths are supported by default. The runtime throws a <xref:System.IO.PathTooLongException> under the following conditions:
-
--   The operating system returns `COR_E_PATHTOOLONG` or its equivalent.
-
--   The length of the path exceeds <xref:System.Int16.MaxValue?displayProperty=nameWithType> (32,767) characters.
-
- **Apps that target the .NET Framework 4.6.1 and earlier versions**
- Long paths are disabled by default, and the legacy behavior is maintained. The runtime throws a <xref:System.IO.PathTooLongException> whenever a path exceeds 260 characters.
-
- If this is undesirable, apps that target the .NET Framework 4.6.1 and earlier but run under the .NET Framework 4.6.2 can enable long path support by including the following setting in the [\<runtime>](/dotnet/framework/configure-apps/file-schema/runtime/runtime-element) element of the application configuration file:
-
-```xml
-
-<runtime>
-   <AppContextSwitchOverrides value="Switch.System.IO.UseLegacyPathHandling=false" />
-</runtime>
-
-```
+- The operating system returns `COR_E_PATHTOOLONG` or its equivalent.
+- The length of the path exceeds <xref:System.Int16.MaxValue?displayProperty=nameWithType> (32,767) characters.
 
  <xref:System.IO.PathTooLongException> uses the HRESULT `COR_E_PATHTOOLONG`, which has the value 0x800700CE.
 
