Transition into COM context 0x%1$x for this RuntimeCallableWrapper failed with the following error: %2$s. This is typically because the COM context 0x%1$x where this RuntimeCallableWrapper was created has been disconnected or it is busy doing something else and cannot process the context transition. No proxy will be used to service the request on the COM component and calls will be made to the COM component directly. This may cause corruption or data loss. To avoid this problem, please ensure that all COM contexts/apartments/threads stay alive and are available for context transition, until the application is completely done with the RuntimeCallableWrappers that represents COM components that live inside them.
Transaction Id: {0} State machine: {1} Current state: {2} History: {3} Unexpected event: {4} Unexpected event details: {5} ...
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 ...