Visual Studio 2013

  1. The process that runs tests on agent '{0}' received an error communicating with the process that collects data and diagnostics: ...
  2. The product identification number in the OS profile of the following template is not valid: {0}. The product identification ...
  3. The product key and password information have not been carried forward from SCVMM. You can specify it in OS profile under ...
  4. The product key information has not been carried forward from SCVMM. You can specify it in OS profile under 'Machine properties' ...
  5. The profile name cannot be empty or be a system reserved names such as COM1, etc., and must contain only use characters that ...
  6. The profiler service is inaccessible. Consider usage of /Admin:security option of VSPerfCmd from elevated environment to ...
  7. The Profiles applied to this Package. This determines what stereotypes that can be applied to elements contained within the ...
  8. The profiling environment for {0} is not set up correctly. Use vsperfclrenv.cmd to setup environment variables. Continue ...
  9. The profiling method you use depends on whether you want to examine performance for the entire application or concentrate ...
  10. The Prog ID, or programmatic identifier, is a text string that your application can use instead of a GUID. The ProgID name ...
  11. The Progress dashboard displays critical information to help you track progress toward completing an iteration. For information ...
  12. The project "{0}" cannot be started directly. In order to debug this project, you must consume it from a Windows Store app ...
  13. The project "{0}" needs to be deployed before it can be started. Verify the project is selected to be deployed in the Solution ...
  14. The project "{0}" needs to be deployed before it can be started. Verify the project is selected to be deployed in the Solution ...
  15. The project %0 appears to be under source control, but the associated source control plug-in is not installed on this computer. ...
  16. The project %0 cannot be added to source control. In folder %1, it overlaps a project that is already bound to source control ...
  17. The project %0 cannot be open from source control in the folder %1. Instead, %2 will get the project files in the folder ...
  18. The project %0 cannot be opened from source control in the folder %1. Instead, %2 will get the project files in the folder ...
  19. The project %0 does not support source control integration, but the solution contains source control binding information ...
  20. The project %1 that you are adding to source control will be added to the same source control location as %2. It overlaps ...
  21. The project %s appears to have been placed under source control with a different provider configuration than the current ...
  22. The project %s cannot be included in a multiple selection. You must change the source control settings on this project by ...
  23. The project '%1' is under source control. An error occurred registering this project with source control. It is recommended ...
  24. The project '%1' is under source control. This version of Visual Studio .NET does not support source controlled projects. ...
  25. The project '%1' must be converted to the current project format. After it has been converted, you will not be able to edit ...
  26. The project '%1' requires Policy Management. Open this project in Visual Studio .NET Enterprise Developer or Visual Studio ...
  27. The project '%1' was created with a newer version of Visual Studio which is incompatible with your version. You can only ...
  28. The project '%1' was created with a newer version of Visual Studio. If you open it with this version of Visual Studio, some ...
  29. The project '%s' cannot be added to the solution because a project with the same project filename already exists in the solution. ...
  30. The project '%s' cannot be started directly. In order to debug this project, you must consume it from an application project ...
  31. The project '%s' has been modified outside the environment, and there are unsaved changes to the project. Press Save As to ...
  32. The project '%s' has been modified outside the environment. Press Reload to load the updated project from disk. Press Ignore ...
  33. The project '%s' must be converted to the current Visual C++ project format. After it has been converted, you will not be ...
  34. The project '%s' needs to be deployed before it can be started. Verify the project is selected to be deployed in the Solution ...
  35. The project '{0}' cannot be started directly. To debug this project, you must reference it from an application project that ...
  36. The project '{0}' contains a reference to assembly '{1}', this assembly is not available in the current edition of Visual ...
  37. The project '{0}' could not be opened because opening it would cause a folder to be rendered multiple times in the solution ...
  38. The project '{0}' was created with an earlier version of Silverlight Tools and needs to be upgraded to the latest format. ...
  39. The project already has a Web reference to the URL '%1'. Do you want to update this reference with the latest information ...
  40. The project cannot be created because one or more primary interop assemblies required by this project are not installed. ...
  41. The project cannot be deployed because the IIS Application Pool '{0}' has not been started. Start the Application Pool in ...
  42. The project cannot be opened or created because Microsoft Office Excel is busy. An add-in is opening a dialog box when Excel ...
  43. The project cannot be saved because another project or solution already exists in the folder '%s'. Please choose another ...
  44. The project cannot be upgraded with this version of Visual Studio. Please use Visual Studio 2012 with Update 2 or later to ...
  45. The project collection could not be located in the Team Foundation Server catalog. The ID of the project collection is {0}. ...
  46. The project consists entirely of configurations that require support for platforms which are not installed on this machine. ...
  47. The project contains no references to a load test plug-in class. Create an assembly that contains a class that implements ...
  48. The project contains no references to a request plug-in class. Create an assembly that contains a class that derives from ...
  49. The project contains no references to a Web test plug-in class. Create an assembly that contains a class that derives from ...
  50. The project could not be upgraded because the file {0} that must be modified cannot be changed. If the file is under source ...
  51. The Project Creation Wizard encountered a problem while creating groups on {0}. The reason for the failure cannot be determined ...
  52. The Project Creation Wizard encountered a problem while creating reports on the SQL Server Reporting Services on {0}. The ...
  53. The Project Creation Wizard encountered a problem while creating the project structure on {0}. The reason for the failure ...
  54. The Project Creation Wizard encountered a problem while uploading documents to the following server running SharePoint Products: ...
  55. The Project Creation Wizard was not able to connect to the server running SharePoint Products at the following location: ...
  56. The Project Creation Wizard was not able to connect to the SQL Server Reporting Services at {0}. The reason for the failed ...
  57. The Project Creation Wizard was not able to connect to the Team Foundation Server {0}. The reason for the failed connection ...
  58. The project currently contains references to more than one version of |1, a direct reference to version |4 and an indirect ...
  59. The Project dashboard displays critical information to help you track progress toward completing your project. For information ...
  60. The Project dashboard displays critical information to help you track progress toward completing your project. For information ...
  61. The project directory already exists. When a project is created, it must be placed within a new folder of the same name. ...
  62. The project failed to load because it has no valid project configuration within the active solution configuration. Open the ...
  63. The project file %0 is not bound to source control, but the solution contains source control binding information for it. ...
  64. The project file '%1' cannot be converted to this Visual Studio .NET version format because it is read-only on disk. Please ...
  65. The project file '%1' cannot be converted to this Visual Studio .NET version format because it is under source code control ...
  66. The project file '%s' cannot be opened. There is a missing project subtype. Subtype: '%s' is unsupported by this installation. ...
  67. The project file '%s' cannot be updated to this Microsoft Visual Studio 2013 version format because it is read-only on disk. ...
  68. The project file '%s' cannot be updated to this Microsoft Visual Studio 2013 version format because it is under source code ...
  69. The project file '{0}' cannot be opened. The project is targeting frameworks that are either not installed or are included ...
  70. The project file is read-only and cannot be checked out from source code control (or source code control is not set on the ...
  71. The Project Item "{0}" contains a Feature property "{1}" with a different value "{2}" than one already in the Feature manifest. ...
  72. The Project Item "{0}" contains a Feature property "{1}" with a value "{2}" different from the following items in Feature ...
  73. The Project Item "{0}" contains a Feature receiver assembly "{1}" that is different than the one specified by the manifest ...
  74. The Project Item "{0}" contains a Feature receiver class "{1}" that is different than the one specified by the manifest template ...
  75. The Project Item "{1}" cannot be deployed as part of a farm solution. Move the project item to a package where the Sandboxed ...