Transparent method {0} calls {1} which is a P/Invoke method. Mark this method as security-critical or remove the call to the P/Invoke method.
Transparent code may not use security asserts, since asserting permissions can result in elevating the effective permissions ...
Transparent code must be fully verifiable. This rule looks for any use of pointer types to check for unverifiable code, however ...
Transparent code must not use security critical attributes. This includes using security critical constructors, properties, ...
Transparent method {0} calls {1} to load an assembly from a byte array. This method should be marked security critical or ...
Transparent method {0} calls {1} which is a P/Invoke method. Mark this method as security-critical or remove the call to ...
Transparent method {0} contains unverifiable code. Mark this method security critical or safe-critical, or remove the unverifiable ...
Transparent method {0} handles security critical exception type {1}. In order for this exception handler to be allowed under ...
Transparent method {0} has a local variable {1} of security critical type {2}. In order for this local variable to be allowed ...
Transparent method {0} has generic parameter {1} with security critical constraint {2}. In order for this generic parameter ...