We recommend using Visual Studio 2017
This documentation is archived and is not being maintained.

CA2143: Transparent methods should not use security demands







Breaking Change


A tranparent type or method is declaratively marked with a SecurityAction.Demand demand or the method calls the CodeAccessPermission.Demand method.

Security transparent code should not be responsible for verifying the security of an operation, and therefore should not demand permissions. Security transparent code should use full demands to make security decisions and safe-critical code should not rely on transparent code to have made the full demand. Any code that performs security checks, such as security demands, should be safe-critical instead.

In general, to fix a violation of this rule, mark the method with the SecuritySafeCriticalAttribute attribute. You can also remove the demand.

Do not suppress a warning from this rule.

The rule files on the following code because a transparent method makes a declarative security demand.

using System;
using System.Security;
using System.Security.Permissions;

namespace TransparencyWarningsDemo

    public class TransparentMethodDemandClass
        // CA2142 violation - transparent code using a Demand.  This can be fixed by making the method safe critical.
        [PermissionSet(SecurityAction.Demand, Unrestricted = true)]
        public void TransparentMethod()