Visual Studio 2012

  1. Team Foundation Server is reporting that the test controller is online, however it is not reachable from this machine in ...
  2. Team Foundation Server is still being contacted for symbol path information. You may have to enter the symbol path for this ...
  3. Team Foundation Server is unable to provision the following account in the Build Service Accounts group: '{0}'. Confirm that ...
  4. Team Foundation Server might not be able to communicate with physical hosts using the new Team Foundation Server service ...
  5. Team Foundation Server might not be able to communicate with the following System Center Virtual Machine Manager (SCVMM) ...
  6. Team Foundation Server stopped the operation on this environment because the environment was unresponsive. The Visual Studio ...
  7. Team Foundation Server supports an internal embedded proxy service for local machine needs. An additional proxy service will ...
  8. Team Foundation Server Trial can be extended in the event that your trial period expires and you are in the process of purchasing ...
  9. Team Foundation Server {0} does not exist or is not accessible at this time. Technical information (for administrator): {1} ...
  10. Team Foundation service accounts is a member of {0} role in SCVMM server. When connecting with SCVMM 2008 R2 server, Team ...
  11. Team Foundation Service enables everyone on your team to collaborate more effectively, be more agile, and deliver better ...
  12. Team Foundation Version Control (TFVC) uses a single, centralized server repository to track and version files. Local changes ...
  13. Team Project "{0}" from Team Foundation Server at "{1}" could not be found. Symbols additional symbol paths will be used. ...
  14. Team Project creation is currently disabled because the server is under temporary maintenance. Please check the service status ...
  15. Team project portals are not enabled for this project collection. This deployment of Team Foundation Server is not configured ...
  16. Team Web Access is not configured correctly. The account that the application pool is running under does not have read and ...
  17. Teams responsible for testing the product can use the Build Quality report to help monitor the success or failure rate of ...
  18. Teams responsible for testing the product can use the Test Team Productivity report to help track the overall activity of ...
  19. Teams responsible for testing the product can use the Test Team Progress report to help monitor test activities and report ...
  20. Teams responsible for testing the product can use the Testing Gaps report to help determine where there are deficiencies ...
  21. TEMPLATE GENERIC argument list following class %$[TEMPLATE GENERIC name must list parameters in the order used in %$[TEMPLATE ...
  22. template instantiation resulted in unexpected function type of 1 (the meaning of a name may have changed since the template ...
  23. Template {0} is configured to add its output to the solution, but a solution element could not be located for the configured ...
  24. Terminating the process in its current state can cause undesired results including loss of data and system instability. There ...
  25. Test Activity Per Build: Helps the team monitor the quality of builds by showing test results for all tests that have been ...
  26. Test Activity Per User: Helps the team track the volume of tests that individual team members have run over the past eight ...
  27. Test agent cannot be run as an interactive process because it is configured to run as a service. Run the Test Agent Configuration ...
  28. Test agent is not configured to run interactively under this account. Run the Test Agent Configuration Tool to change the ...
  29. Test agent process is not started as it is not associated with any test controller. Ignore this warning if this machine will ...
  30. Test agent service is not started as it is not associated with any test controller. Ignore this warning if this machine will ...
  31. Test Case Authoring Status: Helps the team track the status of completing the definition of test cases so that they can be ...
  32. Test cases could not added to test suite {0} because another user performed a conflicting operation. Refresh the client and ...
  33. Test container '{0}' skipped. This test container has test methods that are not supported when executing unit tests for Windows ...
  34. Test Controller is either not running or not configured with Team Foundation Server. Ensure that test controller is configured ...
  35. Test controller is not configured for this environment. Open the environment and specify the test controller in the Advanced ...
  36. Test controller is not configured with the lab service account. You will need to ensure that a) test agent can communicate ...
  37. Test environment '{0}' associated with team project '{1}' could not be loaded, as the test controller is not associated with ...
  38. Test environment '{0}' cannot be registered with the current team project, since the controller '{1}' is not associated with ...
  39. Test environment {0} already exists in this team project for test controller {1}. The test environment must be unique under ...
  40. Test impact data cannot be collected because the IntelliTrace log file was full. In the IntelliTrace diagnostic adapter settings, ...
  41. Test List Editor is deprecated. You cannot run tests from this editor. For more information on migrating from VSMDI files ...
  42. Test method {0}.{1} threw exception {2}, but exception {3} or a type derived from it was expected. Exception message: {4} ...
  43. Test Plan Progress: Helps the team determine how much testing the team has completed and whether it is likely to finish test ...
  44. Test results have been modified by another user or session. You must reload the test run and update the test results again. ...
  45. Test Run deployment issue: Bad deployment item: '{0}': output directory '{1}' specifies the item to be deployed outside deployment ...
  46. Test Run deployment issue: Failed to access output directory '{1}' specified by deployment item '{0}', the item will not ...
  47. Test run will use DLL(s) built for framework {0} and platform {1}. Following DLL(s) will not be part of run: {2} Go to {3} ...
  48. Test settings cannot be loaded from the following file {0}. Verify that the path and the content of the file are correct. ...
  49. Test Status by Area: Helps the team identify gaps in test coverage of product areas. This report requires that team members ...
  50. test(s) run. {1, -10} test(s) passed. {2, -10} test(s) failed. {3, -10} test(s) had error(s). {4, -10} test(s) aborted. {5, ...
  51. TestAgentConfig help command command The name of the command you want help on List of commands: ConfigureAsService Configure ...
  52. TestControllerConfig help command command The name of the command you want help on List of commands: Configure Configure ...
  53. TestFileNames Run tests from the specified files. Separate multiple test file names by spaces. Examples: mytestproject.dll ...
  54. Testing software has gotten even easier with Visual Studio. See exactly what code has been exercised by testers and what ...
  55. Text cannot be copied in the document because the ending location of '{0}' is before the current cursor position of '{1}'. ...
  56. Text keyword Sets the string comparison method specified in Option Compare to a text sort order that is not case sensitive. ...
  57. TextButtonStyle is used to style a Button using subheader-styled text with no other adornment. There are two styles that ...
  58. TextField doesn't support combining AutoSize and MultipleLine options. To create a multiple line TextField that resizes when ...
  59. TextRadioButtonStyle is used to style a RadioButton using subheader-styled text with no other adornment. This style is used ...
  60. TF10109: Source control cannot locate the source control service on Team Foundation Server {0}. Check that you have a network ...
  61. TF10131: The shelveset name {0} contains more than 64 characters, contains one of the following characters: "/:<>\|*?; or ...
  62. TF10131: The workspace name {0} contains more than 64 characters, contains one of the following characters: "/:<>\|*?; or ...
  63. TF10148: Some changes contained within the shelveset {0} were not unshelved. To remove the shelveset from the server delete ...
  64. TF10149: You cannot create files in the root folder. Create a team project and then add the files under the team project ...
  65. TF10159: The label name '{0}' is not supported. It must be less than 64 characters, cannot end with a space, and cannot contain ...
  66. TF10169: Unsupported pending change attempted on team project folder {0}. Use the Project Creation Wizard in Team Explorer ...
  67. TF10174: You do not have permission to delete the team project {0}. Contact your Team Foundation Server administrator and ...
  68. TF10175: The team project folder {0} does not exist. Contact your Team Foundation Server administrator and ask that it be ...
  69. TF10180: The Team Foundation source control server {0} is not available. The server's state was changed to '{1}' on {2} with ...
  70. TF10200: The path '{0}' contains one or more characters which are not allowed. Characters which are not allowed include '"', ...
  71. TF10202: The path '{0}' ends with a character which is not allowed. Characters which are not allowed include '.' and ' '. ...
  72. TF10205: The computer name '{0}' contains characters which are not allowed. Characters which are not allowed include '`', ...
  73. TF10209: Source control cannot show differences between the specified file and the local file. Either the local file doesn't ...
  74. TF10216: Team Foundation services are currently unavailable. Try again later. If the problem persists, contact your Team ...
  75. TF10217: Team Foundation was unable to complete your request due to an unexpected error. For more details, see the event ...