Transparency attributes are applied from larger scopes inward. For instance, if a type is marked as entirely security critical, than all methods introduced by the type will also be security critical. Members should not have transparency annotations which conflict with larger scoped annotations, as these smaller scoped annotations will be ignored by the CLR and can be misleading during a code review. Methods not introduced by their type, such as virtual methods being overridden from a base type or interface methods being implemented, do have their annotations considered under the level 2 security rule set and are not considered by this rule.
Transactions are not supported for asynchronous method calls. Provide a synchronous version of the method or unset the TransactionOption ...
Transition '{0}' of state '{1}' is an unconditional transition. It may not share the same trigger '{2}' with other transition(s). ...
Transition into COM context 1$x for this RuntimeCallableWrapper failed with the following error: %2$s. This is typically ...
Transition into COM context 1$x for this RuntimeCallableWrapper failed with the following error: %2$s. This is typically ...
Transparency attributes are applied from larger scopes inward. For instance, if a type is marked as entirely security critical, ...
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 ...