Visual Studio 2013

  1. The target process aborted before activation completed. More information may be available in the Debug pane of the Output ...
  2. The target process is running a version of the Microsoft .NET Framework newer than this version of Visual Studio. Visual ...
  3. The target type of the conditional style, this controls what type of objects the conditional expressions will be applied ...
  4. The Task returned from this Async Function will be dropped, and any exceptions in it ignored. Consider changing it to an ...
  5. The Team Foundation Server file cache folder is used to cache frequently accessed TFS resources for more efficient communication ...
  6. The Team Foundation Server has not been configured for Lab Management. Before you enable Lab Management for this team project ...
  7. The Team Foundation Server is unable to unconfigure this team project collection due to a failure while deleting lab assets ...
  8. The Team Foundation Server rollback is complete. Some packages may need to be manually uninstalled through the Windows Control ...
  9. The team project collection references a SharePoint Web application that is not referenced in the deployment of Team Foundation ...
  10. The Team Project Collection will be stopped while the detach operation is in progress. The message below will be displayed ...
  11. The Team Project Collection you are attempting to attach already exists in this Team Foundation Server. If you wish to clone ...
  12. The team project could not be deleted. Either the delete operation failed, or project creation failed but the partially-created ...
  13. The Team Project Creation Wizard was unable to connect to the Team Foundation Server {0}. Without a connection, the wizard ...
  14. The Team Project Creation Wizard was unable to connect to the Team Foundation Server {0}. Without a connection, the wizard ...
  15. The Team Project Creation Wizard was unable to connect to the Team Foundation Server {0}. Without a connection, the wizard ...
  16. The team project {0} does not support {1}. Project configuration does not exist. Contact your Team Foundation Server administrator. ...
  17. The team project {0} does not support {1}. The required category '{2}' does not exist in the team project. Contact your Team ...
  18. The team project {0} does not support {1}. The required field '{2}' is missing for work item type '{3}' in the team project. ...
  19. The team project {0} does not support {1}. The team project configuration does not contain valid entry for '{2}'. Contact ...
  20. the template argument list of the partial specialization includes a nontype argument whose type depends on a template parameter ...
  21. the template parameter list for class template '%$S' does not match the template parameter list for template parameter '%$S' ...
  22. The template {0} specified by the adapter manager {1} produced an output item that is not supported by its corresponding ...
  23. The templates you select will be downloaded, installed to your computer, and opened in Visual Studio. Most of the templates ...
  24. The test adapter ('{0}') required to execute this test could not be loaded. Check that the test adapter is installed properly. ...
  25. The test agent is either not running or not properly configured on the machine. Click Repair/Install Agents'. Alternatively, ...
  26. The test agent on the machines that use the selected role will be configured to run as interactive process. Specify the user ...
  27. The test agent will run as an interactive process. In this mode, you can run automated tests that need to interact with the ...
  28. The test agent will run as Windows service. This is the recommended mode when you need to run automated tests that do not ...
  29. The test assembly '{0}' cannot be loaded on machine '{1}' because access is denied. Please grant the user '{2}' permission ...
  30. The test assembly '{0}' cannot be loaded on machine '{1}' because access is denied. Please grant the user '{2}' permission ...
  31. The test automation associated with the following test case could not be found: {0}]. Run the test case again using a build ...
  32. The test cannot be run. Confirm that there is a solution open, and that the test you want to run is contained in the current ...
  33. The test case with id {0} refers the shared step with id {1} which either does not exist or you do not have permission to ...
  34. The test configuration cannot be deleted because it is referenced in one or more test results. You can set the state of the ...
  35. The test configuration has been modified by another user or session. You must reload the test configuration and update it ...
  36. The test controller for test run {0} does not match the test environment being used. Make sure the test run uses the same ...
  37. The test controller has been associated with another Team Foundation Server. Click the remove button on the left to remove ...
  38. The test controller is currently running tests. You must wait until the tests are finished, and then you can add the test ...
  39. The test controller is currently unavailable. Ask your administrator to connect to the test controller machine, launch the ...
  40. The test controller is not available. Ask your administrator to connect to the test controller machine and check that it ...
  41. The test controller is not configured for this environment. Open the environment, click the Advanced tab, and specify the ...
  42. The Test dashboard provides an overview of the readiness of the test team and progress toward testing the product. For information ...
  43. The Test dashboard provides an overview of the readiness of the test team and progress toward testing the product. For information ...
  44. The Test Discovery Add-Ins installed through a VSIX installation are ignored. Use the /UseVsixExtensions parameter to include ...
  45. The test execution process crashed while running the tests. To investigate further, open {0} file in Visual Studio and choose ...
  46. The Test Executor Add-Ins installed through a VSIX installation are ignored. Use the /UseVsixExtensions parameter to include ...
  47. The test is configured to use ASP.NET, but the name specified in the AspNetDevelopmentServer attribute is invalid. The name ...
  48. The Test Logger Add-Ins installed through a VSIX installation are ignored. Use the /UseVsixExtensions parameter to include ...
  49. The test machine configuration does not match the configuration specified on the environment. Team Foundation Server is expecting ...
  50. The test method {0}.{1} has multiple attributes derived from ExpectedExceptionBaseAttribute defined on it. Only one such ...
  51. The test or test run is configured to run in ASP.NET in IIS, but the current user ({0}) is not in the Administrators group. ...
  52. The test plan with id {0} does not exist or it's area path is not owned by the default project team. Include it in the default ...
  53. The test property type '{0}' of property '{1}' is not supported. Use one of the supported property type (primitive types, ...
  54. The test result share {0} is not accessible. You might not have permission to use this network resource. Contact the administrator ...
  55. The test result you requested does not exist on {0}, probably because the result has not yet been published. If the test ...
  56. The test result, {0}, could not be upgraded for the following test run: {1}. This test result is missing from the following ...
  57. The test results you are attempting to view using a link cannot be found. The test results might have been deleted by another ...
  58. The Test Run '{0}' is in the process of being published. In order to properly link this Test Result with a Work Item, this ...
  59. The test run associated with this IntelliTrace log file no longer exists. You may have to enter the symbol path for this ...
  60. The test run associated with this IntelliTrace log file was not associated with a build from Team Build. You may have to ...
  61. The test run contains manual tests which cannot be run remotely. In order to continue with the run, manual tests will be ...
  62. The test run is a partial run, it was created from subset of results of the original run. The test run does not contain diagnostics ...
  63. The test run results could not be saved because the full path to the test results (.trx) file exceeds the maximum length ...
  64. The test run you are attempting to view using a link cannot be found. The test run might have been deleted by another user, ...
  65. The test settings file "{0}" already exists. Do you want to replace the existing file? Yes: replace it with a new test settings ...
  66. The test settings file you are using specifies a remote machine for running tests, for which Visual Studio Premium or Visual ...
  67. The test settings file you are using specifies to run tests with data collectors enabled. To use this feature, Visual Studio ...
  68. The test settings file {0}, specified in the MSTestAdapter settings, is not available. Either access to the file is denied ...
  69. The test settings have been configured to collect data and diagnostics for a diagnostic data adapter that has an empty assembly-qualified ...
  70. The test settings have been configured to collect data and diagnostics for an agent containing two diagnostic data adapters ...
  71. The test settings have been configured to collect data and diagnostics for two agents with the name '{0}'. Agent names must ...
  72. The test settings specify a remote machine for running tests, for which Visual Studio Premium or Visual Studio Ultimate is ...
  73. The test started running in response to request '{0}', but an error occurred before the test finished executing: {1}. {2} ...
  74. The test suite has the same name as another test suite that has the same parent. Each test suite that has the same parent ...
  75. The testing policy requires all check-in tests to pass because test impact information is unavailable. {0} test(s) have not ...