.NET Framework

  1. The synchronous OperationContract method '{0}' in type '{1}' was matched with the asynchronous OperationContract methods ...
  2. The synchronous OperationContract method '{0}' in type '{1}' was matched with the asynchronous OperationContract methods ...
  3. The synchronous OperationContract method '{0}' in type '{1}' was matched with the asynchronous OperationContract methods ...
  4. The synchronous OperationContract method '{0}' in type '{1}' was matched with the task-based asynchronous OperationContract ...
  5. The synchronous OperationContract method '{0}' in type '{1}' was matched with the task-based asynchronous OperationContract ...
  6. The synchronous OperationContract method '{0}' in type '{1}' was matched with the task-based asynchronous OperationContract ...
  7. The synchronous OperationContract method '{0}' in type '{1}' was matched with the task-based asynchronous OperationContract ...
  8. The System Health Check has detected a problem that may cause Setup to fail. Description %1 Workaround / Remedy %2 More information ...
  9. The System Health Check has detected a problem that will cause Setup to fail. Description %1 Workaround / Remedy %2 More ...
  10. The system hit the limit set for throttle 'MaxConcurrentInstances'. Limit for this throttle was set to %1. Throttle value ...
  11. The system hit the limit set for throttle 'MaxConcurrentInstances'. Limit for this throttle was set to {0}. Throttle value ...
  12. The system hit the limit set for throttle '{0}'. Limit for this throttle was set to {1}. Throttle value can be changed by ...
  13. The table ({0}) cannot be the child table to itself in a nested relation: the DataSet name conflicts with the table name. ...
  14. The table column or XML attribute name to use for a menu item's Value property when databinding. When binding to a data source, ...
  15. The table column or XML attribute name to use for an item's Value property when databinding. When binding to a data source, ...
  16. The table property used by LinqDataSource '{0}' must be a generic type with one parameter that extends ITable, when the Delete, ...
  17. The table property used by LinqDataSource '{0}' must extend Table when the Delete, Insert or Update operations are enabled. ...
  18. The table/view '{0}' does not have a primary key defined and no valid primary key could be inferred. This table/view has ...
  19. The table/view '{0}' does not have a primary key defined. The key has been inferred and the definition was created as a read-only ...
  20. The table/view '{0}' has column '{1}' defined as a primary key, but the column type '{2}' is not a valid type for a key in ...
  21. The tag is no longer supported as a child of the element. Place this tag within a target, and add the name of the target ...
  22. The tail.call (or calli or callvirt) instruction cannot be used to transfer control out of a try, filter, catch, or finally ...
  23. The target directory is not empty, and does not appear to contain a previously compiled application. Please delete it manually, ...
  24. The target namespace of an attribute declaration, whether local or global, must not match http://www.w3.org/2001/XMLSchema-instance. ...
  25. The TargetName property '{0}' on more than one EntityPropertyMappingAttribute on resource type '{1}' have the same value. ...
  26. The targetNamespace '{0}' of included/redefined schema should be the same as the targetNamespace '{1}' of the including schema. ...
  27. The Task provider delegate specified for this IAsyncInfo instance returned a Task object that was not started. Task instances ...
  28. The task provider delegate used to create this asynchronous operation returned null, but a valid Task object was expected. ...
  29. The Task returned from this Async Function will be dropped, and any exceptions in it ignored. Consider changing it to an ...
  30. The task-based asynchronous OperationContract method '{0}' in type '{1}' was matched with the asynchronous OperationContract ...
  31. The task-based asynchronous OperationContract method '{0}' in type '{1}' was matched with the asynchronous OperationContract ...
  32. The task-based asynchronous OperationContract method '{0}' in type '{1}' was matched with the asynchronous OperationContract ...
  33. The task-based asynchronous OperationContract method '{0}' in type '{1}' was matched with the asynchronous OperationContract ...
  34. The template file to be used for creating this event notification is not found. The {0} events that were part of this message ...
  35. The text that appears in the ALT attribute of the invisible image link that allows screen readers to skip repetitive content. ...
  36. The TextInfo.ANSICodePage and TextInfo.OEMCodePage properties must be the same when either one is a multi-byte code page. ...
  37. The ThreadLocal object is not tracking values. To use the Values property, use a ThreadLocal constructor that accepts the ...
  38. The throttle 'MaxPendingMessagesPerChannel' limit of '%1' was hit. To increase this limit, adjust the MaxPendingMessagesPerChannel ...
  39. The throttle 'MaxPendingMessagesPerChannel' limit of '{0}' was hit. To increase this limit, adjust the MaxPendingMessagesPerChannel ...
  40. The time zone ID '{0}' was found on the local computer, but the application does not have permission to read the registry ...
  41. The timeout for a command must be between zero and Int32.MaxValue seconds. Use TimeSpan.MaxValue to specify an infinite timeout. ...
  42. The TimeSpan could not be parsed because at least one of the hours, minutes, or seconds components is outside its valid range. ...
  43. The TimeSpan could not be parsed because at least one of the numeric components is out of range or contains too many digits. ...
  44. The TimeToPersist value must be greater than or equal to TimeSpan.Zero. To disable, specify value equal to TimeSpan.MaxValue. ...
  45. The TimeToUnload value must be greater than or equal to TimeSpan.Zero. To disable, specify value equal to TimeSpan.MaxValue. ...
  46. The title when the connections zone is displaying existing connections. The name of the Web part to connect is appended to ...
  47. The token requirement '{0}' does not specify the target address. This is required by the token manager for creating the corresponding ...
  48. The tool '{0}' is already active in this editing context. You cannot activate the same instance of a task tool more than ...
  49. The toolbox item could not be retrieved from the toolbox. Make sure the assembly that contains the toolbox item is correctly ...
  50. The top XML element '{0}' from namespace '{1}' references distinct types {2} and {3}. Use XML attributes to specify another ...
  51. The total arity specified in '{0}' does not match the number of TypeArguments supplied. There were '{1}' TypeArguments supplied. ...
  52. The total number of instances of the service. http://msdn.microsoft.com/en-US/library/System.ServiceModel.Diagnostics.Pe ...
  53. The total size of messages sent in this session exceeded the maximum value of Int32. The messages in this session cannot ...
  54. The ToValidateContext argument of the {0} named '{1}' resolved to null. A non-null validation context object must be provided. ...
  55. The transaction '{0}' for operation '{1}' was completed due to the TransactionAutoComplete OperationBehaviorAttribute member ...
  56. The transaction '{0}' was aborted because it was uncompleted when the session was closed and the TransactionAutoCompleteOnSessionClose ...
  57. The transaction '{0}' was completed when the session was closed due to the TransactionAutoCompleteOnSessionClose ServiceBehaviorAttribute ...
  58. The transaction associated with the current connection has completed but has not been disposed. The transaction must be disposed ...
  59. The transaction associated with this session channel has been rolled back because Abort was called on the session channel ...
  60. The transaction cannot begin. The current data connection does not support transactions or the current state is not allowing ...
  61. The transaction header '{0}' within the namespace '{1}' was not understood by the service. The client and the service must ...
  62. The transport channel detected a poison message. This occurred because the message exceeded the maximum number of delivery ...
  63. The transport configured on this binding does not appear to support the CompressionFormat specified ({0}) on the message ...
  64. The TransportBindingElement of type '{0}' in this CustomBinding returned a null or empty string for the Scheme. TransportBindingElement's ...
  65. The two ends of a ResourceAssociationSet cannot both have the same ResourceType and ResourceProperty. If this is a self-referencing ...
  66. The type '%2!ls!' in '%1!ls!' conflicts with the imported namespace '%4!ls!' in '%3!ls!'. Using the type defined in '%1!ls!'. ...
  67. The type '%3!ls!' must be a non-nullable value type in order to use it as parameter '%2!ls!' in the generic type or method ...
  68. The type '%3!ls!' must be a reference type in order to use it as parameter '%2!ls!' in the generic type or method '%1!ls!' ...
  69. The type '%3!ls!' must have a public parameterless constructor in order to use it as parameter '%2!ls!' in the generic type ...
  70. The type '%4!ls!' cannot be used as type parameter '%3!ls!' in the generic type or method '%1!ls!'. The nullable type '%4!ls!' ...
  71. The type '%4!ls!' cannot be used as type parameter '%3!ls!' in the generic type or method '%1!ls!'. The nullable type '%4!ls!' ...
  72. The type '%4!ls!' cannot be used as type parameter '%3!ls!' in the generic type or method '%1!ls!'. There is no boxing conversion ...
  73. The type '%4!ls!' cannot be used as type parameter '%3!ls!' in the generic type or method '%1!ls!'. There is no boxing conversion ...
  74. The type '%4!ls!' cannot be used as type parameter '%3!ls!' in the generic type or method '%1!ls!'. There is no implicit ...
  75. The type '%4!ls!' must be convertible to '%2!ls!' in order to use it as parameter '%3!ls!' in the generic type or method ...