Visual Studio 2010

  1. The reference control is not valid for the child control insertion. The reference control must exist and be valid for insertion ...
  2. The reference from {0} to {1} cannot be resolved because you do not have a translator that can map between their respective ...
  3. The reference to an element that has the name {0} and the disambiguator {1} could not be resolved because no element with ...
  4. The reference to an unnamed element that has the disambiguator {0} could not be resolved because no element with that disambiguator ...
  5. The reference to the element that has the name {0} and no disambiguator could not be resolved because no element with that ...
  6. The reference to the element with the name '{0}' could not be resolved. More than one element with this name exists. To resolve ...
  7. The reference to the external element with the name '{0}' could not be resolved. More than one element with this name exists. ...
  8. The reference {0} does not exist or does not refer to a valid assembly that was generated by Microsoft Visual Studio 2010 ...
  9. The referenced or default base CLI library 'mscorlib' is binary-incompatible with the referenced F# core library '{0}'. Consider ...
  10. The referenced or default base CLI library 'mscorlib' is binary-incompatible with the referenced library '{0}'. Consider ...
  11. The referenced table '{0}' contains no primary or candidate keys that match the referencing column list in the foreign key. ...
  12. The registration form will work only in the Root Web. In order for this form to function properly, this page must be saved ...
  13. The registration key you entered is not valid. Please enter the registration key exactly as it appears on the registration ...
  14. The relative path of the file in the SharePoint server. The fully qualified path for the file is created by concatenating ...
  15. The remote computer does not have a CLR version which is compatible with the remote debugging components. To install a compatible ...
  16. The remote debugger can be run as either a Windows service or a Windows application. Running the remote debugger as a service ...
  17. The remote debugger has encountered a serious internal error, and must abort the remote debugging session. Please restart ...
  18. The remote debugger is not correctly installed on the remote computer. Repair your remote debugger installation using 'Add ...
  19. The remote debugger is unable to communicate with Visual Studio, and must abort the remote debugging session. Please restart ...
  20. The remote debugger service was successfully configured. However, the service did not start due to a logon failure. Verify ...
  21. The remote debugger was closed while a remote debugging session was active. This remote debugger must abort this session. ...
  22. The remote debugging components are not registered or running on the web server. Ensure the proper version of msvsmon is ...
  23. The remote procedure could not be debugged. This usually indicates that debugging has not been enabled on the server. See ...
  24. The remote Web site already contains a file named '{0}'.{1}{2}Do you want to replace this file on the remote Web site:{3}{4}{5}{6}{7}{8}Status: ...
  25. The removal of Microsoft Visual Studio 2010 Service Pack 1 may put this computer in an state in which projects cannot be ...
  26. The rename operation cannot be completed because the designer required to refactor the generated code has not been activated. ...
  27. The rename operation cannot be completed because the document designer is closed. Open the document designer and perform ...
  28. The repeating form (centered) style shows the title for an item in the list and the other fields on separate lines underneath ...
  29. The repeating form style shows the title for an item in the list and the other fields on separate lines underneath the title. ...
  30. The repeating tabular form style shows the title for an item in the list and the other fields on separate rows underneath ...
  31. The report contains an embedded image with an invalid name {1}'. Embedded image names must be CLS-Compliant identifiers. ...
  32. The report contains an invalid data source with the name {1}'. Data source names must be greater than 0 and less than or ...
  33. The report contains an invalid embedded image name, {1}'. Embedded image names must be greater than 0 and less than or equal ...
  34. The report data source object must be of the type System.Data.DataTable, System.Collections.IEnumerable, or System.Web.UI.IDataSource. ...
  35. The report data source object must be of the type System.Data.DataTable, System.Collections.IEnumerable, System.Windows.Forms.BindingSource, ...
  36. The Report Definition Customization Extension (RDCE) name that is specified in the report does not match the RDCE name that ...
  37. The Report Definition Customization Extension (RDCE) returned a different RDL version than it was originally passed. The ...
  38. The Report Definition Customization Extension (RDCE) returned a null or invalid RDL. Make sure that the RDL contains valid ...
  39. The report definition element '{0}' is empty at line {2}, position {3}. It is missing a mandatory child element of type '{1}'. ...
  40. The report definition is not valid. Please verify that the report definition uses the current report definition {2} (i.e. ...
  41. The report parameter {1}' has a DefaultValue or a ValidValue that depends on the report parameter "{3}". Forward dependencies ...
  42. The report parameter {1}' has a DefaultValue that has a Values collection containing more than one value. For single-value ...
  43. The report parameter {1}' has a DefaultValue that has both or neither of the following: Values and DataSetReference. DefaultValue ...
  44. The report parameter {1}' has a ValidValues that has both or neither of the following: ParameterValues and DataSetReference. ...
  45. The report server cannot access the private key for the service account. This key is used to decrypt the symmetric key that ...
  46. The report server cannot decrypt the symmetric key that is used to access sensitive or encrypted data in a report server ...
  47. The report server cannot open a connection to the report server database. A connection to the database is required for all ...
  48. The report server configuration file specifies localhost for the Web server name. The report server requires that the computer ...
  49. The report server could not transmit the file because the file {0} is not installed or you do not have the correct permissions ...
  50. The report server to which you are connecting has returned an SSL certificate that is not valid. The server might not be ...
  51. The Report Server Web Service is unable to access secure information in the report server. Please verify that the WebServiceAccount ...
  52. The report snapshot '{1}' cannot be found for report '{0}'. The snapshot identifier cannot be located in the report server ...
  53. The Report Viewer Web Control HTTP Handler has not been registered in the application's web.config file. Add {0} to the {1} ...
  54. The report was uploaded, but a warning occurred. The severity of the warning is: {1}. The message is: {2}. The code is: {0}. ...
  55. The representation of this type is hidden by the signature. It must be given an attribute such as ], or to indicate the characteristics ...
  56. The request could not be processed because the application is not configured correctly. No service host is available for ...
  57. The request for the URL '{0}' failed. Ensure that the web site is configured correctly on the web server and is accessible. ...
  58. The requested mapping matches an existing mapping on server path ({0} to {1}) as well as a different mapping on local path ...
  59. The requested operation cannot be completed because the list or document library at "%1!.200s!" would contain the list or ...
  60. The requested schema property {0} did not match the expected value. The server requires the {1} schema but the database currently ...
  61. The requested schema property {0} was not found. This property is required and must match the application's required version. ...
  62. The required Internet protocol is not installed on your computer, or the Internet address you requested may not be valid. ...
  63. The required pattern for URI containing ";component" is "AssemblyName;Vxxxx;PublicKey;component", where Vxxxx is the assembly ...
  64. The required version of the .NET Framework is not installed on this computer. The computer must have the .NET Framework Client ...
  65. The required version of the .NET Framework is not installed on this computer. The computer must have the .NET Framework version ...
  66. The required version of the .NET Framework is not installed on this computer. The computer must have the .NET Framework version ...
  67. The required Windows Rights Management client is present but the server could not be accessed. Information Rights Management ...
  68. The required Windows Rights Management client is present but the server refused access. Information Rights Management (IRM) ...
  69. The reset settings operation cannot be completed because no vssettings file has been specified, please specify a valid vssettings ...
  70. The resource file is corrupted and cannot be edited; there may be a problem with the resource script. Create the resource ...
  71. The resource file is corrupted, or the editor for this type of file is not available. Create another resource file or install ...
  72. The resource listed below uses this symbol. To change the symbol name or value, click "View Use" and edit the ID for the ...
  73. The resource name or ID specified in reserved by Visual Studio. The reserved names are DESIGNINFO, HWB, and TEXTINCLUDE, ...
  74. The resource script %s was not created using Microsoft Visual Studio. Comments, macros, preprocessor directives, and conditionally ...
  75. The resource string "{0}" for the "{1}" task cannot be found. Confirm that the resource name "{0}" is correctly spelled, ...