Transparent code must be fully verifiable. This rule looks for any use of pointer types to check for unverifiable code, however it is not a complete verifier and PEVerify / transparent must be run on assemblies to ensure that all of their transparent code is verifiable.
Transparency visibility must be preserved between overriding methods and the methods that are being overridden. If the virtual ...
Transparent code cannot refer to security critical methods, types, or fields. At runtime these references will result in ...
Transparent code may not call native code directly. This rule looks for any transparent code which calls a method stub (such ...
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 ...