.NET Core samples should not include CAS elements

[danmoseley]

In .NET Core, CAS types (like FileIOPermission, etc) and Security Transparency types are stubbed only. CAS is not supported. Therefore the samples in .NET Core topics should not include use of them.

For example, in the AppDomain.UnhandledException topic for .NET Core 2.1 it has this sample:

using System;
using System.Security.Permissions;

public class Example 
{
   [SecurityPermission(SecurityAction.Demand, Flags=SecurityPermissionFlag.ControlAppDomain)]
   public static void Main()
   {
...

Here [SecurityPermission(SecurityAction.Demand, Flags=SecurityPermissionFlag.ControlAppDomain)] should be removed as it does nothing and implies that CAS is relevant.

---

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: 48667829-dc8d-680d-6fde-71a46dee4ce7
• Version Independent ID: 15184777-1251-be89-27a7-7ca859082294
• Content: AppDomain.UnhandledException Event (System)
• Content Source: xml/System/AppDomain.xml
• Product: dotnet-api
• GitHub Login: @rpetrusha
• Microsoft Alias: ronpet

[mairaw]

Thanks @danmosemsft. I've added this issue to our security review project. We're hoping to get started on this soon.

[danmoseley]

Here's another example, which reminded me.
https://docs.microsoft.com/en-us/dotnet/api/system.console.bufferheight?view=netcore-3.0

Security
UIPermission 
for modifying safe top-level windows and subwindows. Associated enumeration: SafeTopLevelWindows

A bit confusing if you heard that CAS is dead.

[rpetrusha]

This issue has languished, @danmosemsft, but I'll start addressing it in the next sprint.

[danmoseley]

Thanks, @rpetrusha