Visual Studio 2010

  1. The type name {0} conflicts in whole or in part with the namespace name '{1}'. Change either name to eliminate the conflict. ...
  2. The type of a field using the 'DefaultValue' attribute must admit default initialization, i.e. have 'null' as a proper value ...
  3. The type of field "%1" does not match the type of the column "%2" in the database. Modify the field mapping or change the ...
  4. The Type of the role player provided in the DomainRoleAttribute for DomainRole '{0}' on DomainRelationship '{1}' is not a ...
  5. The type of the specified content control does not match the type of content control that this method adds to the document. ...
  6. The Type on FilterDescriptor '{0}' cannot be set to 'Timestamp'. The Method '{1}' already contains a FilterDescriptor of ...
  7. The type parameter '%1!ls!' cannot be used with the 'as' operator because it does not have a class type constraint nor a ...
  8. The type parameters inferred for this value are not stable under the erasure of type abbreviations. This is due to the use ...
  9. The type referenced through '{0}' is defined in an assembly that is not referenced. You must add a reference to assembly ...
  10. The type {0} is not strongly named. You must use strong name signing for assemblies that contain implementations of extensions. ...
  11. The typed dataset will not compile. Open the dataset in the Dataset Designer and verify each TableAdapter is set to a valid ...
  12. The TypeDescriptor '{0}' is of a DateTime type, but there is no Interpretation describing how the back-end interprets the ...
  13. The TypeDescriptor '{0}' references an Association '{1}' which could not be found on Entity with name '{2}' and namespace ...
  14. The TypeDescriptor '{0}' references an Identifier '{1}' which could not be found on Entity with name '{2}' and namespace ...
  15. The TypeDescriptor named '{0}' contains too many child TypeDescriptors that have the Associated Filter property set to the ...
  16. The TypeDescriptor with name '{0}' does not specify the name of the association being referred to in the Entity '{1}' in ...
  17. The TypeDescriptor with name '{0}' does not specify the name of the identifier being referred to in the Entity '{1}' in namespace ...
  18. The TypeDescriptor with name '{0}' has an invalid LobName. The LobName for a TypeDescriptor cannot be longer than {1} characters. ...
  19. The TypeDescriptor with name '{0}' has an invalid TypeName. The TypeName for a TypeDescriptor cannot be longer than {1} characters. ...
  20. The TypeName property of TypeDescriptor '{0}' is defined to be '{1}' which is a multi-dimension array that is not supported ...
  21. The types System.ValueType, System.Enum, System.Delegate, System.MulticastDelegate and System.Array cannot be used as super ...
  22. The underlying values array passed to this mapped object converter is invalid; it must be a single element array containing ...
  23. The undo checkout of the file '%1' on the Web server succeeded, but a failure occured when trying to update your local copy ...
  24. The uninstallation was unable to uninstall the extension to the selected product. For more information, click on the install ...
  25. The unit test adapter failed to connect to the data source or to read the data. For more information on troubleshooting this ...
  26. The unnamed check constraint on table {0} will be checked by checking the table. Name the constraint to avoid checking the ...
  27. The unnamed foreign key between tables {0} and {1} will be checked by checking the table. Name the foreign key to avoid checking ...
  28. The Update Action was reset for an object of type {0}' because it is indistinguishable from another object of the same type ...
  29. The Update Action was reset for one or more objects because they were indistinguishable from objects of the same type with ...
  30. The updated version of the application is signed with a different key than the published version. Do you want to overwrite ...
  31. The updates installed on Microsoft Test Manager do not match the updates installed on Team Foundation Server. The mismatch ...
  32. The updates installed on Microsoft Test Manager do not match the updates installed on Team Foundation Server. The mismatch ...
  33. The updates installed on Microsoft Test Manager do not match the updates installed on Team Foundation Server. You cannot ...
  34. The updates installed on Microsoft Test Manager do not match the updates installed on Team Foundation Server. You cannot ...
  35. The upgrade operation failed since this project contained some reference(s) to assemblies that are not available in the present ...
  36. The upgrade task cannot be completed. The following share location could not be accessed: {1} because of the following security ...
  37. The upgrade task did not complete successfully. Investigate the reported errors, and then rerun the tool to complete upgrading ...
  38. The URL '%1!.200s!' is invalid. It may refer to a nonexistent file or folder, or refer to a valid file or folder that is ...
  39. The URL '%1!.200s!' may not be used. It may refer to a folder name that is in use, or to a file or folder outside the current ...
  40. The URL '{0}' specified for Web project '{1}' requires IIS Express. Would you like to download it now using Web Platform ...
  41. The URL '{1}' for Web project '{0}' is configured to use IIS as the web server but the URL is currently configured on the ...
  42. The URL '{1}' for Web project '{0}' is configured to use IIS Express as the web server but the URL is currently configured ...
  43. The URL for SharePoint Central Administration usually has the following format: http://ServerName:Port/ For more information, ...
  44. The URL membership condition is true for all assemblies that originate from the URL specified below. Assemblies that meet ...
  45. The URL must include the protocol such as 'ftp://' or 'http://'. An asterisk (*) can be used as a wildcard character at the ...
  46. The URL or name of this list instance conflicts with a list instance already on the server. The list instance on the server ...
  47. The URL specified ('{0}') does not correspond to a valid directory. Tests configured to run in ASP.NET in IIS require a valid ...
  48. The URL {0} is for a different instance of Team Foundation Server. Technical information (for administrator): Current Server ...
  49. The use case defining additional behavior. The definition of this use-case is typically not self-contained, and can be understood ...
  50. The use case defining the included behavior. The definition of this use-cases is typically self-contained, so that it can ...
  51. The use of '->' in sequence and computation expressions is limited to the form 'for pat in expr -> expr'. Use the syntax ...
  52. The use of named arguments in union case expressions is reserved for future use. Arguments of the form 'a=b' should be parenthesized. ...
  53. The use of the type syntax 'int C' and 'C ' is not permitted here. Consider adjusting this type to be written in the form ...
  54. The user account '%1!.200s!' cannot be added to the current virtual server because it is in use by a site on a different ...
  55. The user account '%1!.200s!' cannot be created due to quota limitations. The maximum number of user accounts for this site ...
  56. The user account for the test agent does not have administrator privileges. Press F1 to learn more about when the test agent ...
  57. The user creation request has been canceled. Please verify your entry and try again. If the problem persists, please contact ...
  58. The user or group, %1!.250s!, you are attempting to add equals or contains the account used by your web server to allow anonymous ...
  59. The user pressed Cancel in the Find Source dialog. The debug source files settings for the active solution have been modified ...
  60. The user template information is out of date. This information is automatically regenerated. There must have been a problem ...
  61. The user-defined table type ({0}) could not be created because the minimum row size would be {1}. Table rows cannot be larger ...
  62. The value "{0}" was returned by the registry get operation. To determine which key was accessed, see the previous diagnostic ...
  63. The value '{0}' contains an unexpected quotation mark ("). To specify a value that contains a quotation mark, surround the ...
  64. The value '{0}' was marked inline but its implementation makes use of an internal or private function which is not sufficiently ...
  65. The value '{1}' contains significant white space(s) but "xml:space = preserve" cannot be written down on the member '{0}'. ...
  66. The value contains characters that are not allowed (control characters, 0xFFFE, or 0xFFFF). Please remove those characters. ...
  67. The value contains characters that are not allowed (control characters, 0xFFFE, or 0xFFFF). Please remove those characters. ...
  68. The value for item '{0}' and property '{1}' is not available because a previous validation rule deemed the value invalid, ...
  69. The value for the property should be either >, >=, , equal, not equal, greater than equal, greater than, less than equal ...
  70. The value for this item is stale due to a problem that occurred while evaluating it. Hover your cursor over the refresh button ...
  71. The value for this item is stale due to a problem that occurred while evaluating it. Hover your cursor over the refresh button ...
  72. The value must be of type "{0}" or must be the string formed from concatenating the string elements using the Separator string. ...
  73. The value of the attribute '{0}' contains a definition in an external DTD that changes on normalization and this is not allowed ...
  74. The value of the ExpectedResponseUrl property '{0}' does not equal the actual response URL '{1}'. QueryString parameters ...
  75. The value of the property {2} of the {1} with ID {0} cannot be changed because its properties are locked, either individually ...