.NET Framework
- TrackRecord= WorkflowInstanceUpdatedRecord, InstanceID = {0}, RecordNumber = {1}, EventTime = {2}, ActivityDefinitionId = ...
- TransactedBatchingBehavior validation failed because none of the service operations had the TransactionScopeRequired property ...
- TransactedBatchingBehavior validation failed. Service cannot be started. Transacted batching requires ServiceBehavior.Re ...
- TransactedBatchingBehavior validation failed. Service or client cannot be started. Transacted batching is not supported for ...
- TransactedBatchingBehavior validation failed. The service endpoint cannot be started. TransactedBatchingBehavior requires ...
- Transaction Id: {0} State machine: {1} Current state: {2} History: {3} Unexpected event: {4} Unexpected event details: {5} ...
- 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 ...
- 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 ...
- Transparent method {0} has parameter {1} of security critical type {2}. In order for this parameter to be allowed under the ...
- Transparent method {0} is a member of security critical type {1}. Since this method will not have access to its own instance ...
- Transparent method {0} is protected with a LinkDemand for {1}. Remove this LinkDemand, or make the method security critical ...
- Transparent method {0} references security critical field {1}. In order for this reference to be allowed under the security ...
- Transparent method {0} references security critical method {1}. In order for this reference to be allowed under the security ...
- Transparent method {0} references security critical type {1}. In order for this reference to be allowed under the security ...
- Transparent method {0} returns a byref type. Change the return type of this method, or mark it security critical or safe-critical. ...
- Transparent method {0} returns security critical type {1}. In order for this return type to be allowed under the security ...
- Transparent or safe critical method {0} is overriding critical method {1} in violation of method override rules. {0} must ...
- Transparent or safe-critical method {0} uses the SuppressUnmanagedCodeSecurityAttribute, either directly on the method or ...
- Transparent or safe-critical type {0} derives from critical type {1} in violation of the transparency inheritance rules. ...
- Transparent type {0} derives from safe-critical type {1} in violation of the transparency inheritance rules. {0} must be ...
- Trigger-less transition '{0}' of state '{1}' must contain a condition. A state can only have one unconditional transition ...
- True is not a valid value for the Checked property. This is only valid for MenuItems that have no children and are not top-level. ...
- Truncated tracking record {0} written to ETW session with provider {1}. Variables/annotations/user data have been removed ...
- TryExpression is not supported as a child expression when accessing a member on type '{0}' because it is a value type. Construct ...
- TryExpression is not supported as an argument to method '{0}' because it has an argument with by-ref type. Construct the ...
- TThe operation '{1}' on contract '{0}' is configured with TransactionAutoComplete set to false and with ConcurrencyMode not ...
- Turn optimized code generation on or off;Change Designer layout grid settings;Turn automatic display of Designer Smart Tag ...
- Two different copies of MSCORWKS.DLL have been loaded. First copy: %s Second copy: %s This is typically caused by having ...
- Two different copies of MSCORWKS.DLL have been loaded. First copy: %s Second copy: %s This is typically caused by having ...
- Two distinct members of the attribute uses must not have type definitions which are both xs:ID or are derived from xs:ID. ...
- Two entities with different keys are mapped to the same row. Ensure these two mapping fragments do not map two EntitySets ...
- Two entities with different keys are mapped to the same row. Ensure these two mapping fragments do not map two groups of ...
- Two entities with different keys are mapped to the same row. Ensure these two mapping fragments do not map two groups of ...
- Two entities with different keys are mapped to the same row. Ensure these two mapping fragments do not map two groups of ...
- Two entities with identical keys are mapped to different rows within the same table. Ensure these two mapping fragments do ...
- Two entities with possibly different keys are mapped to the same row. Ensure these two mapping fragments do not map two unrelated ...
- Two entities with possibly different keys are mapped to the same row. Ensure these two mapping fragments map both ends of ...
- Two entities with possibly identical keys are mapped to different rows within the same table. Ensure these two mapping fragments ...
- Two indexers have different names; the IndexerName attribute must be used with the same name on every indexer within a type ...
- Two ReceiveParametersContent objects with same ServiceContractName and OperationName '{0}' have different number of parameters. ...
- Two ReceiveParametersContent objects with same ServiceContractName and OperationName '{0}' have different parameter names. ...
- Two ReceiveParametersContent objects with same ServiceContractName and OperationName '{0}' have different parameter types. ...
- Two rows with different primary keys are mapped to the same entity. Ensure these two mapping fragments do not map two groups ...
- Two rows with different primary keys are mapped to two entities that carry identical keys through a referential integrity ...
- Two SendParametersContent objects with same ServiceContractName and OperationName '{0}' have different number of parameters. ...
- Type '%1!ls!' cannot be embedded because it has a generic argument. Consider setting the 'Embed Interop Types' property to ...
- Type '%1!ls!' cannot be embedded because it is a nested type. Consider setting the 'Embed Interop Types' property to false. ...
- Type '%1!ls!' from assembly '%2!ls!' cannot be used across assembly boundaries because a type in its inheritance hierarchy ...
- Type '%1!ls!' from assembly '%2!ls!' cannot be used across assembly boundaries because it has a generic type parameter that ...
- Type '%1' in assembly '%2' has method '%3' which is either static, virtual, abstract or generic, but is marked as being a ...
- Type '%1' in assembly '%2' has method '%3' with an incorrect signature for the serialization attribute that it is decorated ...
- Type '%hs' has auto-layout but is being exported. Consider marking the type ComVisible(false) since the exported definition ...
- Type '{0}' cannot be added to list of known types since another type '{1}' with the same data contract name '{2}:{3}' is ...
- Type '{0}' cannot be added to list of known types since another type '{1}' with the same data contract name '{2}:{3}' is ...
- Type '{0}' cannot be exported as a schema type because it is an open generic type. You can only export a generic type if ...
- Type '{0}' cannot be initialized from text (XamlLanguage.Initialization). Add a TypeConverter to this type or change the ...
- Type '{0}' cannot be instantiated under a partially trusted security policy (AllowPartiallyTrustedCallersAttribute is not ...
- Type '{0}' cannot be serialized. Consider marking it with the DataContractAttribute attribute, and marking all of its members ...
- Type '{0}' cannot be serialized. Consider marking it with the DataContractAttribute attribute, and marking all of its members ...