Visual Studio 2013

  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 actual parameter '%1$ls' should exactly match the type '%2$ls': This usually indicates that an enum formal was ...
  4. The type of at least one of your configuration variables has been modified from Standard to Encrypted. The values of those ...
  5. The type of build configuration to perform. 'Create' creates and agent and controller, 'Restore' restores an existing definition ...
  6. The type of service you're monitoring. Valid values include "Tfs", "Sps", "Els" and "Msdn". See ServiceDeploymentType enumeration. ...
  7. The type of the new registry value (REG_SZ, REG_MULTI_SZ, REG_DWORD_BIG_ENDIAN, REG_DWORD, REG_BINARY, REG_DWORD_LITTLE_ENDIAN, ...
  8. The Type of the role player provided in the DomainRoleAttribute for DomainRole '{0}' on DomainRelationship '{1}' is not a ...
  9. The Type on FilterDescriptor '{0}' cannot be set to 'Timestamp'. The Method '{1}' already contains a FilterDescriptor of ...
  10. The type parameter '%1!ls!' cannot be used with the 'as' operator because it does not have a class type constraint nor a ...
  11. The type parameters inferred for this value are not stable under the erasure of type abbreviations. This is due to the use ...
  12. The type provider '{0}' provided a method with a name '{1}' and metadata token '{2}', which is not reported among its methods ...
  13. The type provider '{0}' returned an invalid type from 'ApplyStaticArguments'. A type with name '{1}' was expected, but a ...
  14. The type provider does not have a valid constructor. A constructor taking either no arguments or one argument of type 'TypeProviderConfig' ...
  15. The type referenced through '{0}' is defined in an assembly that is not referenced. You must add a reference to assembly ...
  16. The type XSLTProcessor and the function XmlDocument.transformNode are not supported by this browser, can't transform XML ...
  17. The type {0} can not be resolved within the current project. This can happen when setting WPF values in a Silverlight project, ...
  18. The type {0} could not be loaded. The assembly containing the class may be missing or may have additional references which ...
  19. The type {0} does not have a default query defined. A parameter-less query with IsDefault set to True is required. The type ...
  20. The typed dataset will not compile. Open the dataset in the Dataset Designer and verify each TableAdapter is set to a valid ...
  21. The TypeDescriptor '{0}' is of a DateTime type, but there is no Interpretation describing how the back-end interprets the ...
  22. The TypeDescriptor '{0}' references an Association '{1}' which could not be found on Entity with name '{2}' and namespace ...
  23. The TypeDescriptor '{0}' references an Identifier '{1}' which could not be found on Entity with name '{2}' and namespace ...
  24. The TypeDescriptor named '{0}' contains too many child TypeDescriptors that have the Associated Filter property set to the ...
  25. The TypeDescriptor with name '{0}' does not specify the name of the association being referred to in the Entity '{1}' in ...
  26. The TypeDescriptor with name '{0}' does not specify the name of the identifier being referred to in the Entity '{1}' in namespace ...
  27. The TypeDescriptor with name '{0}' has an invalid LobName. The LobName for a TypeDescriptor cannot be longer than {1} characters. ...
  28. The TypeDescriptor with name '{0}' has an invalid TypeName. The TypeName for a TypeDescriptor cannot be longer than {1} characters. ...
  29. The TypeName property of TypeDescriptor '{0}' is defined to be '{1}' which is a multi-dimension array that is not supported ...
  30. The types System.ValueType, System.Enum, System.Delegate, System.MulticastDelegate and System.Array cannot be used as super ...
  31. The UI Factory returned a valid UIElement but it does not support WPF and cannot be used in this scenario. (Actual type:{0}). ...
  32. The UI Factory returned a valid UIElement that supports IVsUIWpfElement, but CreateFrameworkElement failed with error code ...
  33. The UI Factory returned a valid view, but the view failed to create. The UI element's GetUIObject method returned error code ...
  34. The UI Factory threw a TargetInvocationException during CreateFrameworkElement. This typically indicates a XAML bug in the ...
  35. The underlying values array passed to this mapped object converter is invalid; it must be a single element array containing ...
  36. The uninstall cannot continue because it might affect other applications that are installed. For more information, see h ...
  37. The uninstall of Microsoft .NET Framework 3.0 cannot continue because a later version of Microsoft .NET Framework is dependent ...
  38. The uninstallation was unable to uninstall the extension to the selected product. For more information, click on the install ...
  39. The unit test adapter failed to connect to the data source or to read the data. For more information on troubleshooting this ...
  40. The unit test adapter failed to connect to the data source or to read the data. For more information on troubleshooting this ...
  41. The UnitTestIsolation instrumentation was not properly initialized. Please ensure that your VisualStudio installation supports ...
  42. The updated version of the application is signed with a different key than the published version. Do you want to overwrite ...
  43. The upgrade operation failed since this project contained some reference(s) to assemblies that are not available in the present ...
  44. The upgrade task cannot be completed. The following share location could not be accessed: {1} because of the following security ...
  45. The upgrade task did not complete successfully. Investigate the reported errors, and then rerun the tool to complete upgrading ...
  46. The URL '{0}' is currently configured on the local IIS web server. LightSwitch can only use IIS Express to host the web server. ...
  47. The URL authority, consisting of Domain Name System (DNS) host name or IP address and the port number, to use for token audience ...
  48. The URL for SharePoint Central Administration usually has the following format: http://ServerName:Port/ For more information, ...
  49. The URL is only used as entry point for your app. You still have to use the publish functionality of your Web- or Azure Project ...
  50. The URL or name of this list instance conflicts with a list instance already on the server. The list instance on the server ...
  51. The URL specified ('{0}') does not correspond to a valid directory. Tests configured to run in ASP.NET in IIS require a valid ...
  52. The url specified in the registry to connect to Visual Studio Online for load testing is invalid: {0}. Specify a valid url ...
  53. The url specified to connect to Visual Studio Online for load testing was not found in Team Explorer: {0}. Connect to this ...
  54. The URL to the Access Control Service management portal. The default value is for the TfsAzure service namespace, which is ...
  55. The URL {0} is for a different instance of Team Foundation Server. Technical information (for administrator): Current Server ...
  56. The use case defining additional behavior. The definition of this use-case is typically not self-contained, and can be understood ...
  57. The use case defining the included behavior. The definition of this use-cases is typically self-contained, so that it can ...
  58. The use of '->' in sequence and computation expressions is limited to the form 'for pat in expr -> expr'. Use the syntax ...
  59. The use of the type syntax 'int C' and 'C ' is not permitted here. Consider adjusting this type to be written in the form ...
  60. The user '{1}' does not have permission to modify the database. Permission granted by a security group is not sufficient. ...
  61. The user account for the test agent does not have administrator privileges. Press F1 to learn more about when the test agent ...
  62. The user must be granted the 'Log on as a service' privilege. This can be done with the 'Local Security Policy' administrative ...
  63. The user name or password is not valid. Enter a valid user name (for example, domain\user) and password, and try the operation ...
  64. The user pressed Cancel in the Find Source dialog. The debug source files settings for the active solution have been modified ...
  65. The user template information is out of date. This information is automatically regenerated. There must have been a problem ...
  66. The value "{0}" was returned by the registry get operation. To determine which key was accessed, see the previous diagnostic ...
  67. The value '{0}' is not a valid custom errors mode. The custom errors mode can be one of the following: On, Off, or RemoteOnly. ...
  68. The value '{0}' is not a valid download ticket type. Download ticket type could be one of the following: MD5Ticket, RSATicket. ...
  69. The value '{0}' was marked inline but its implementation makes use of an internal or private function which is not sufficiently ...
  70. The value '|1' is not a valid subsystem version. The version must be 6.02 or greater for ARM or AppContainerExe, and 4.00 ...
  71. The value contains characters that are not allowed (control characters, 0xFFFE, or 0xFFFF). Please remove those characters. ...
  72. The value for IPBlock is not valid. Specify a valid IPv4 address and subnet mask in the format shown in this example: 192.168.23.0/24 ...
  73. The value for the property should be either >, >=, , equal, not equal, greater than equal, greater than, less than equal ...
  74. The value for this item is stale because a problem occurred during evaluation. {0}For details, rest the pointer on the refresh ...
  75. The value for this item is stale due to a problem that occurred while evaluating it. Hover your cursor over the refresh button ...