Delete CAS docs (#24693)

Author: gewarren

.openpublishing.redirection.json

@@ -4258,6 +4258,91 @@
             "source_path": "docs/framework/misc/binding.md",
             "redirect_url": "/dotnet/framework/configure-apps/file-schema/wcf/bindings"
         },
+        {
+          "source_path": "docs/framework/misc/code-access-security-basics.md",
+          "redirect_url": "/previous-versions/dotnet/framework/code-access-security/code-access-security-basics",
+          "redirect_document_id": false
+        },
+        {
+          "source_path": "docs/framework/misc/code-access-security-policy-compatibility-and-migration.md",
+          "redirect_url": "/previous-versions/dotnet/framework/code-access-security/code-access-security-policy-compatibility-and-migration",
+          "redirect_document_id": false
+        },
+        {
+          "source_path": "docs/framework/misc/code-access-security.md",
+          "redirect_url": "/previous-versions/dotnet/framework/code-access-security/code-access-security",
+          "redirect_document_id": false
+        },
+        {
+          "source_path": "docs/framework/misc/dangerous-permissions-and-policy-administration.md",
+          "redirect_url": "/previous-versions/dotnet/framework/code-access-security/dangerous-permissions-and-policy-administration",
+          "redirect_document_id": false
+        },
+        {
+          "source_path": "docs/framework/misc/how-to-run-partially-trusted-code-in-a-sandbox.md",
+          "redirect_url": "/previous-versions/dotnet/framework/code-access-security/how-to-run-partially-trusted-code-in-a-sandbox",
+          "redirect_document_id": false
+        },
+        {
+          "source_path": "docs/framework/misc/link-demands.md",
+          "redirect_url": "/previous-versions/dotnet/framework/code-access-security/link-demands",
+          "redirect_document_id": false
+        },
+        {
+          "source_path": "docs/framework/misc/securing-exception-handling.md",
+          "redirect_url": "/previous-versions/dotnet/framework/code-access-security/securing-exception-handling",
+          "redirect_document_id": false
+        },
+        {
+          "source_path": "docs/framework/misc/securing-method-access.md",
+          "redirect_url": "/previous-versions/dotnet/framework/code-access-security/securing-method-access",
+          "redirect_document_id": false
+        },
+        {
+          "source_path": "docs/framework/misc/securing-wrapper-code.md",
+          "redirect_url": "/previous-versions/dotnet/framework/code-access-security/securing-wrapper-code",
+          "redirect_document_id": false
+        },
+        {
+          "source_path": "docs/framework/misc/security-and-public-read-only-array-fields.md",
+          "redirect_url": "/previous-versions/dotnet/framework/code-access-security/security-and-public-read-only-array-fields",
+          "redirect_document_id": false
+        },
+        {
+          "source_path": "docs/framework/misc/security-and-remoting-considerations.md",
+          "redirect_url": "/previous-versions/dotnet/framework/code-access-security/security-and-remoting-considerations",
+          "redirect_document_id": false
+        },
+        {
+          "source_path": "docs/framework/misc/security-and-serialization.md",
+          "redirect_url": "/previous-versions/dotnet/framework/code-access-security/security-and-serialization",
+          "redirect_document_id": false
+        },
+        {
+          "source_path": "docs/framework/misc/security-transparent-code-level-1.md",
+          "redirect_url": "/previous-versions/dotnet/framework/code-access-security/security-transparent-code-level-1",
+          "redirect_document_id": false
+        },
+        {
+          "source_path": "docs/framework/misc/security-transparent-code-level-2.md",
+          "redirect_url": "/previous-versions/dotnet/framework/code-access-security/security-transparent-code-level-2",
+          "redirect_document_id": false
+        },
+        {
+          "source_path": "docs/framework/misc/security-transparent-code.md",
+          "redirect_url": "/previous-versions/dotnet/framework/code-access-security/security-transparent-code",
+          "redirect_document_id": false
+        },
+        {
+          "source_path": "docs/framework/misc/using-libraries-from-partially-trusted-code.md",
+          "redirect_url": "/previous-versions/dotnet/framework/code-access-security/using-libraries-from-partially-trusted-code",
+          "redirect_document_id": false
+        },
+        {
+          "source_path": "docs/framework/misc/using-the-assert-method.md",
+          "redirect_url": "/previous-versions/dotnet/framework/code-access-security/using-the-assert-method",
+          "redirect_document_id": false
+        },
         {
             "source_path": "docs/framework/network-programming/httplistener.md",
             "redirect_url": "/dotnet/api/system.net.httplistener"

docs/core/compatibility/core-libraries/5.0/code-access-security-apis-obsolete.md

@@ -63,7 +63,7 @@ This is a compile-time only change. There is no run-time change from previous ve
 
 ## Reason for change
 
-[Code access security (CAS)](../../../../framework/misc/code-access-security.md) is an unsupported legacy technology. The infrastructure to enable CAS exists only in .NET Framework 2.x - 4.x, but is deprecated and not receiving servicing or security fixes.
+[Code access security (CAS)](/previous-versions/dotnet/framework/code-access-security/code-access-security) is an unsupported legacy technology. The infrastructure to enable CAS exists only in .NET Framework 2.x - 4.x, but is deprecated and not receiving servicing or security fixes.
 
 Due to CAS's deprecation, the [supporting infrastructure was not brought forward to .NET Core](../../../porting/net-framework-tech-unavailable.md) or .NET 5.0+. However, the APIs were brought forward so that apps could cross-compile against .NET Framework and .NET Core. This led to "fail open" scenarios, where some CAS-related APIs exist and are callable but perform no action at run time. This can lead to security issues for components that expect the runtime to honor CAS-related attributes or programmatic API calls. To better communicate that the runtime doesn't respect these attributes or APIs, we have obsoleted the majority of them in .NET 5.0.
 

docs/core/porting/net-framework-tech-unavailable.md

@@ -28,13 +28,13 @@ Across machines, use a network-based solution as an alternative. Preferably, use
 
 ## Code access security (CAS)
 
-Sandboxing, which relies on the runtime or the framework to constrain which resources a managed application or library uses or runs, [isn't supported on .NET Framework](../../framework/misc/code-access-security.md) and therefore is also not supported on .NET Core and .NET 5+. There are too many cases in the .NET Framework and the runtime where an elevation of privileges occurs to continue treating CAS as a security boundary. Also, CAS makes the implementation more complicated and often has correctness-performance implications for applications that don't intend to use it.
+Sandboxing, which relies on the runtime or the framework to constrain which resources a managed application or library uses or runs, [isn't supported on .NET Framework](/previous-versions/dotnet/framework/code-access-security/code-access-security) and therefore is also not supported on .NET Core and .NET 5+. There are too many cases in the .NET Framework and the runtime where an elevation of privileges occurs to continue treating CAS as a security boundary. Also, CAS makes the implementation more complicated and often has correctness-performance implications for applications that don't intend to use it.
 
 Use security boundaries provided by the operating system, such as virtualization, containers, or user accounts, for running processes with the minimum set of privileges.
 
 ## Security transparency
 
-Similar to CAS, security transparency separates sandboxed code from security critical code in a declarative fashion but is [no longer supported as a security boundary](../../framework/misc/security-transparent-code.md). This feature is heavily used by Silverlight.
+Similar to CAS, security transparency separates sandboxed code from security critical code in a declarative fashion but is [no longer supported as a security boundary](/previous-versions/dotnet/framework/code-access-security/security-transparent-code). This feature is heavily used by Silverlight.
 
 Use security boundaries provided by the operating system, such as virtualization, containers, or user accounts, for running processes with the least set of privileges.
 

docs/csharp/misc/cs0688.md

@@ -12,7 +12,7 @@ ms.assetid: 8ce5af36-663e-46e8-87e9-bb32555796ae
 
 'method1' has a link demand, but overrides or implements 'method2' which does not have a link demand. A security hole may exist.  
 
- The link demand set up on the derived class method can easily be circumvented by calling the base class method. To close the security hole, the base class method needs to also use the link demand. For more information, see [Demand vs. LinkDemand](../../framework/misc/securing-wrapper-code.md#demand-vs-linkdemand).  
+ The link demand set up on the derived class method can easily be circumvented by calling the base class method. To close the security hole, the base class method needs to also use the link demand. For more information, see [Demand vs. LinkDemand](/previous-versions/dotnet/framework/code-access-security/securing-wrapper-code#demand-vs-linkdemand).  
 
 ## Example  
 

docs/framework/configure-apps/file-schema/runtime/loadfromremotesources-element.md

@@ -70,7 +70,7 @@ so this load may be dangerous. If this load is not intended to sandbox the assem
 
 To load the assembly and execute its code, you must either:
 
-- Explicitly create a sandbox for the assembly (see [How to: Run Partially Trusted Code in a Sandbox](../../../misc/how-to-run-partially-trusted-code-in-a-sandbox.md)).
+- Explicitly create a sandbox for the assembly (see [How to: Run Partially Trusted Code in a Sandbox](/previous-versions/dotnet/framework/code-access-security/how-to-run-partially-trusted-code-in-a-sandbox)).
 
 - Run the assembly's code in full trust. You do this by configuring the `<loadFromRemoteSources>` element. It lets you specify that the assemblies that run in partial trust in earlier versions of the .NET Framework now run in full trust in the .NET Framework 4 and later versions.
 
@@ -114,7 +114,7 @@ The following example shows how to grant full trust to assemblies loaded from re
 ## See also
 
 - [More Implicit Uses of CAS Policy: loadFromRemoteSources](/archive/blogs/shawnfa/more-implicit-uses-of-cas-policy-loadfromremotesources)
-- [How to: Run Partially Trusted Code in a Sandbox](../../../misc/how-to-run-partially-trusted-code-in-a-sandbox.md)
+- [How to: Run Partially Trusted Code in a Sandbox](/previous-versions/dotnet/framework/code-access-security/how-to-run-partially-trusted-code-in-a-sandbox)
 - [Runtime Settings Schema](index.md)
 - [Configuration File Schema](../index.md)
 - <xref:System.Reflection.Assembly.LoadFrom%2A?displayProperty=nameWithType>

docs/framework/configure-apps/file-schema/runtime/netfx40-legacysecuritypolicy-element.md

@@ -56,7 +56,7 @@ In the .NET Framework version 3.5 and earlier versions, CAS policy is always in
 
 CAS policy is version-specific. Custom CAS policies that exist in earlier versions of the .NET Framework must be respecified in the .NET Framework 4.
 
-Applying the `<NetFx40_LegacySecurityPolicy>` element to a .NET Framework 4 assembly does not affect [security-transparent code](../../../misc/security-transparent-code.md); the transparency rules still apply.
+Applying the `<NetFx40_LegacySecurityPolicy>` element to a .NET Framework 4 assembly does not affect [security-transparent code](/previous-versions/dotnet/framework/code-access-security/security-transparent-code); the transparency rules still apply.
 
 > [!IMPORTANT]
 > Applying the `<NetFx40_LegacySecurityPolicy>` element can result in significant performance penalties for native image assemblies created by the [Native Image Generator (Ngen.exe)](../../../tools/ngen-exe-native-image-generator.md) that are not installed in the [global assembly cache](../../../app-domains/gac.md). The performance degradation is caused by the inability of the runtime to load the assemblies as native images when the attribute is applied, resulting in their being loaded as just-in-time assemblies.

docs/framework/data/adonet/secure-client-applications.md

@@ -63,7 +63,7 @@ Applications typically consist of many parts that must all be protected from vul
 |--------------|-----------------|  
 |[Configuration of Remote Applications](/previous-versions/dotnet/netframework-4.0/b8tysty8(v=vs.100))|Discusses how to configure remoting applications in order to avoid common problems.|  
 |[Security in Remoting](/previous-versions/dotnet/netframework-4.0/9hwst9th(v=vs.100))|Describes authentication and encryption as well as additional security topics relevant to remoting.|  
-|[Security and Remoting Considerations](../../misc/security-and-remoting-considerations.md)|Describes security issues with protected objects and application domain crossing.|  
+|[Security and Remoting Considerations](/previous-versions/dotnet/framework/code-access-security/security-and-remoting-considerations)|Describes security issues with protected objects and application domain crossing.|  
 
 ## See also
 

docs/framework/data/adonet/security-overview.md

@@ -67,7 +67,7 @@ For more information, see the following resources:
 |Resource|Description|
 |--------------|-----------------|
 |[Code Access Security and ADO.NET](code-access-security.md)|Describes the interactions between code access security, role-based security, and partially trusted environments from the perspective of an ADO.NET application.|
-|[Code Access Security](../../misc/code-access-security.md)|Contains links to additional topics describing CAS in the .NET Framework.|
+|[Code Access Security](/previous-versions/dotnet/framework/code-access-security/code-access-security)|Contains links to additional topics describing CAS in the .NET Framework.|
 
 ## Database Security
 

docs/framework/data/adonet/sql/clr-integration-security-in-sql-server.md

@@ -16,7 +16,7 @@ Microsoft SQL Server provides the integration of the common language runtime (CL
 
 |Resource|Description|  
 |--------------|-----------------|  
-|[Code Access Security](../../../misc/code-access-security.md)|Contains topics describing CAS in the .NET Framework.|  
+|[Code Access Security](/previous-versions/dotnet/framework/code-access-security/code-access-security)|Contains topics describing CAS in the .NET Framework.|  
 |[CLR Integration Security](/sql/relational-databases/clr-integration/security/clr-integration-security)|Discusses the security model for managed code executing inside of SQL Server.|  
 
 ## See also

docs/framework/deployment/index.md

@@ -149,7 +149,7 @@ The .NET Framework provides the following options for distributing applications:
 
 To determine where to deploy your application's assemblies so they can be found by the runtime, see [How the Runtime Locates Assemblies](how-the-runtime-locates-assemblies.md).
 
-Security considerations can also affect how you deploy your application. Security permissions are granted to managed code according to where the code is located. Deploying an application or component to a location where it receives little trust, such as the Internet, limits what the application or component can do. For more information about deployment and security considerations, see [Code Access Security Basics](../misc/code-access-security-basics.md).
+Security considerations can also affect how you deploy your application. Security permissions are granted to managed code according to where the code is located. Deploying an application or component to a location where it receives little trust, such as the Internet, limits what the application or component can do. For more information about deployment and security considerations, see [Code Access Security Basics](/previous-versions/dotnet/framework/code-access-security/code-access-security-basics).
 
 ## Related Topics