Visual Studio 2010

  1. The item {0} was renamed to a path that was previously deleted. This is a known data-lose scenario that the VSS converter ...
  2. The item(s) %1 you are about to delete locally cannot be deleted in the source control database at this time because you're ...
  3. The item(s) %1 you are about to rename locally cannot be renamed in the source control database at this time because you're ...
  4. The items for this operation {0} and {1} cannot be located on different SharePoint sites. If you are moving an item, select ...
  5. The items you selected cannot be checked out, so this modification cannot be completed. The items have probably been checked ...
  6. The job '{0}' was associated with the upgraded server. This job could not be deleted, the job is no longer needed and can ...
  7. The job agent is not configured correctly. The application setting {0} in the configuration file {1} must be a valid connection ...
  8. The job agent is not configured correctly. The application setting {0} in the configuration file {1} must be a valid guid. ...
  9. The job agent is not configured correctly. The configuration file {0} does not exist or the job agent service account doesn't ...
  10. The Just-In-Time debugger is not properly installed. Use 'Add or Remove Programs' to repair the Microsoft Visual Studio 64-bit ...
  11. The Just-In-Time debugger was launched without necessary security permissions. This is most likely because User Account Control ...
  12. The KernelTraceControl.dll does not support the required functions, collection cannot proceed. Please repair your installation. ...
  13. The key name cannot: - contain any of the following characters: / ? : \ " < > | - contain Unicode control characters - be ...
  14. The key {0} was created from a cryptographic provider, but that provider does not exist in the database. The key was omitted. ...
  15. The lab agent is a background process that runs on a machine to configure, monitor, and report on status and errors. The ...
  16. The lab agent received instruction to restart test agent but that instruction was ignored because test agent process is not ...
  17. The lab agent received instruction to start test agent but that instruction was ignored because test agent is configured ...
  18. The lab agent received instruction to start test agent service but that instruction was ignored because startup mode for ...
  19. The lab agent received instruction to start test agent service but that instruction was ignored because test agent service ...
  20. The lab agent received instruction to start the build agent service but that instruction was ignored because startup mode ...
  21. The lab agent received instruction to start the build agent service but that instruction was ignored because the build agent ...
  22. The label has been modified since it was opened in the editor and you no longer have the latest version. Please close the ...
  23. The label name '{0}' is not supported. It must be less than 64 characters, and cannot contain any of the following characters: ...
  24. The language for this file does not support the necessary code parsing and generation services. Please ensure the file you ...
  25. The language identifier (LCID) specified in the process template does not exist on the server running SharePoint Products. ...
  26. The language identity (ID) specified in the process template cannot be validated. If the SharePoint Web application does ...
  27. The language of the file referenced by the 'CodeFile' attribute does not match the language specified by the 'Language' attribute ...
  28. The language referenced by the 'Language' attribute is not supported by Visual Studio IntelliSense and statement completion. ...
  29. The language samples familiarize you with various C# language features. They are available in the LanguageSamples folder. ...
  30. The language to use for the generated code. Choose from 'CS', 'VB', 'JS', 'VJS', 'CPP' or provide a fully-qualified name ...
  31. The last breakpoint hit. If multiple breakpoints were hit simultaneously, it is undefined which breakpoint in particular ...
  32. The last Configuration Manager action caused SCC to reload the solution and one or more projects and was cancelled. Please ...
  33. The last Win32 error can be reset as a result of making managed calls, due to P/Invokes called by the runtime itself. In ...
  34. The latest version of the solution or project file containing the item(s) will not reflect this change until your next checkin. ...
  35. The latest version of the solution or project file containing the item(s) will not reflect this change until your next checkin. ...
  36. The layout definition for a pyramid diagram with accent shapes must contain a grandchild layout node with the name specified ...
  37. The layout definition for a pyramid diagram with accent shapes must specify height, width, centerX and centerY constraints ...
  38. The layout definition for a pyramid diagram with accent shapes must use the composite algorithm for its child layout nodes. ...
  39. The layout table form style shows a layout table with a single table cell containing the fields that you chose. This style ...
  40. The length of the full path for the solution, project or item you are creating exceeds the maximum path length allowed by ...
  41. The length of the full path for the test project you are creating exceeds the maximum path length allowed by the system. ...
  42. The length of the full path of the Office document exceeds the maximum path length allowed. Reduce the length of the document ...
  43. The length of the full path of the Office document exceeds the maximum path length allowed. Reduce the length of the name ...
  44. The length of the name for the solution will cause the path to exceed the maximum path length allowed by the system. You ...
  45. The length of the name of the file(s) selected is too long. Please select fewer files or files with shorter path lengths. ...
  46. The line endings in this file are not consistently a CR/LF pair but are consistent throughout the file. Do you want the line ...
  47. The lines show moving averages (7 day and 8 week) for the number of work items that were changed into each state per day. ...
  48. The link options to enable edit, delete, and insert modes are unavailable because the current data source does not support ...
  49. The link options to enable edit, delete, and insert modes are unavailable because the current Data View uses XSLT that does ...
  50. The link options to enable edit, delete, and insert modes are unavailable because the current Data View was created by converting ...
  51. The link options to enable edit, delete, and insert modes are unavailable because the current layout does not support link ...
  52. The link options to enable edit, delete, and insert modes are unavailable because the data source query does not contain ...
  53. The link options to enable edit, delete, and insert modes are unavailable for Data Views created on Windows SharePoint Services ...
  54. The link options to enable edit, delete, and insert modes can only be used on servers running Windows SharePoint Services ...
  55. The LinkDemands on override {0} do not exactly match the following LinkDemands on base method {1}: {2}. Add, remove, or modify ...
  56. The LinkDemands on override {0} do not exactly match the LinkDemands on base method {1}. Add, remove, or modify LinkDemands ...
  57. The linked image cannot be displayed. The file may have been moved, renamed, or deleted. Verify that the link points to the ...
  58. The list below contains specific changesets that have been checked in to the source branch but not merged into the target ...
  59. The list from which you are removing one or more columns has one or more cells with values which have been changed. If any ...
  60. The list of builds cannot be retrieved. Verify that the Team Build Web service is configured properly, and then try again. ...
  61. The list of code coverage files to process could not be read from the RunUpdate table in the Team Foundation Build database: ...
  62. The list of code coverage updates to process could not be updated in the team build database. Some code coverage data may ...
  63. The list of custom message class names contains incorrect formatting. These are the guidelines for the list: Use the fully ...
  64. The list of folders to search for files. Checking the "Add subfolders" checkbox indicates that all of the subfolders for ...
  65. The list of test runs to process could not be read from the TestRun or Platforms_Flavors table in the Team Foundation Build ...
  66. The load test contains an old definition for the LoadTest CounterSet and needs to be updated. To do so, edit the load test: ...
  67. The load test network emulation configuration is invalid for a local run: more than one network type can only be specified ...
  68. The load test network emulation configuration is invalid for agent '{0}': more than one network type can only be specified ...
  69. The load test results database could not be opened. Check that the load test results database specified by the connect string ...
  70. The load test results repository is out of space. Allocate more space to the repository (if possible), or delete results ...
  71. The load test results repository was created with a previous version and is not compatible. You can either upgrade this repository ...
  72. The load test results repository was created with a previous version and is not compatible. You can either upgrade this repository ...
  73. The load test results repository was created with a previous version and is not compatible. You can either upgrade this repository ...
  74. The loader was unable to read code from '{0}'. Be sure the file has a valid language extension and is not currently open ...
  75. The LoadTest Results Store Type is 'Database', but the results repository connect string has not been specified. The load ...