Visual Studio 2012

  1. The lab agent received instruction to start the build agent service but that instruction was ignored because startup mode ...
  2. The lab agent received instruction to start the build agent service but that instruction was ignored because the build agent ...
  3. The label has been modified since it was opened in the editor and you no longer have the latest version. Please close the ...
  4. The label name '{0}' is not supported. It must be less than 64 characters, and cannot contain any of the following characters: ...
  5. The Language element specified in the app manifest is invalid. It must be one of the values supported by the Windows Phone ...
  6. The language identifier (LCID) specified in the process template does not exist on the server running SharePoint Products. ...
  7. The language identity (ID) specified in the process template cannot be validated. If the SharePoint Web application does ...
  8. The language to use for the generated code. Choose from 'CS', 'VB', 'JS', 'VJS', 'CPP' or provide a fully-qualified name ...
  9. The language-neutral word breaker could not be loaded. (Default simple word breaking is used.) This might affect search relevancy. ...
  10. The last breakpoint hit. If multiple breakpoints were hit simultaneously, it is undefined which breakpoint in particular ...
  11. The last Configuration Manager action caused SCC to reload the solution and one or more projects and was cancelled. Please ...
  12. The last Win32 error can be reset as a result of making managed calls, due to P/Invokes called by the runtime itself. In ...
  13. The latest version of Silverlight must be installed prior to installing this application. Please install Silverlight, then ...
  14. The latest version of the solution or project file containing the item(s) will not reflect this change until your next checkin. ...
  15. The latest version of the solution or project file containing the item(s) will not reflect this change until your next checkin. ...
  16. The left bounds of the substring that needs to be extracted from the script area of the ListView WebPart. For example 'ctx.listName ...
  17. The length of the default directory specified in the setup.sdb file cannot be greater then 100 characters. The directory ...
  18. The length of the full path for the solution, project or item you are creating exceeds the maximum path length allowed by ...
  19. The length of the full path of the Office document exceeds the maximum path length allowed. Reduce the length of the document ...
  20. The length of the full path of the Office document exceeds the maximum path length allowed. Reduce the length of the name ...
  21. The length of the install path is too long. If setup is being run from a network drive, map the network drive to a shorter ...
  22. The length of the name for the solution will cause the path to exceed the maximum path length allowed by the system. You ...
  23. The length of the name of the file(s) selected is too long. Please select fewer files or files with shorter path lengths. ...
  24. The length of the unattend file name and path cannot be greater then 250 characters. Rerun setup using a shorter unattend ...
  25. The line endings in this file are not consistently a CR/LF pair but are consistent throughout the file. Do you want the line ...
  26. The lines show moving averages (7 day and 8 week) for the number of work items that were changed into each state per day. ...
  27. The list below contains specific changesets that have been checked in to the source branch but not merged into the target ...
  28. The list from which you are removing one or more columns has one or more cells with values which have been changed. If any ...
  29. The list of builds cannot be retrieved. Verify that the Team Build Web service is configured properly, and then try again. ...
  30. The list of code coverage files to process could not be read from the RunUpdate table in the Team Foundation Build database: ...
  31. The list of code coverage updates to process could not be updated in the team build database. Some code coverage data may ...
  32. The list of custom message class names contains incorrect formatting. These are the guidelines for the list: Use the fully ...
  33. The list of folders to search for files. Checking the "Add subfolders" checkbox indicates that all of the subfolders for ...
  34. The list of referenced types contains more than one type with data contract name '{0}' in namespace '{1}'. Verify the list ...
  35. The list of test runs to process could not be read from the TestRun or Platforms_Flavors table in the Team Foundation Build ...
  36. The load test contains an old definition for the LoadTest CounterSet and needs to be updated. To do so, edit the load test: ...
  37. The load test network emulation configuration is invalid for a local run: more than one network type can only be specified ...
  38. The load test network emulation configuration is invalid for agent '{0}': more than one network type can only be specified ...
  39. The load test results database could not be opened. Check that the load test results database specified by the connect string ...
  40. The load test results repository is out of space. Allocate more space to the repository (if possible), or delete results ...
  41. The load test results repository was created with a previous version and is not compatible. You can either upgrade this repository ...
  42. The load test results repository was created with a previous version and is not compatible. You can either upgrade this repository ...
  43. The loader was unable to read code from '{0}'. Be sure the file has a valid language extension and is not currently open ...
  44. The LoadTest Results Store Type is 'Database', but the results repository connect string has not been specified. The load ...
  45. The local folder you chose to store your solution contains one or more solution files that have the same name as those in ...
  46. The local Help viewer requires a number of command-line options in order to launch the correct content. Windows does not ...
  47. The local path '{0}' contains an illegal wildcard. The only wildcard character allowed is an '*' to map a Team Foundation ...
  48. The local version of this file in your workspace is out of date. Would you like to view the server version or the workspace ...
  49. The location of the content source is invalid: {0}. Check the location, and then specify the correct URL or path to the .msha ...
  50. The location specified cannot be created. Check that the location is not a reserved system name, and that the disk is writeable ...
  51. The location specified is not a valid absolute or UNC path. Enter a valid absolute path (such as C:\FolderName) or UNC path ...
  52. The location that IntelliTrace will write the collected data into log files. The identity that is running the application ...
  53. The location you have chosen for your project is volatile and will be deleted when the application exits. Please choose another ...
  54. The login name '{0}' already exists. Do you want to use this login to read and write data to the central database for your ...
  55. The machine role is already part of test environment '{0}'. Remove the machine role from that test environment before adding ...
  56. The machine role is already part of test environment '{0}'. Remove the machine role from that test environment before adding ...
  57. The machine settings has changed from when the test agent configuration was last performed. Run the test agent configuration ...
  58. The managed coclass wrapper class '%1!ls!' for interface '%2!ls!' cannot be found (are you missing an assembly reference?) ...
  59. The managed code projects and the native code projects using C++/CLI extensions in this solution will be automatically updated ...
  60. The Managed Resource Editor does not support the requested file type. Would you like to open the default editor for "{0}"? ...
  61. The management service identity for service bus. This identity will have access to perform managment functions on the namespace. ...
  62. The Manifest Designer cannot load the manifest because the document has one or more errors. Fix the error(s), reload the ...
  63. The Manifest Designer requires at least one supported file type or data format. Check the box "Supports any file type" or ...
  64. The Manifest Designer requires at least one supported file type. Check the box "Supports any file type" or explicitly add ...
  65. The manifest file at '%1' does not contain sufficient permissions to launch your application for debugging. Please edit your ...
  66. The Manual Test type is used when the test tasks are to be completed by a test engineer as opposed to an automated script ...
  67. The manual test {0} is open in Microsoft Word. When you change a property of the test, Microsoft Word saves the test file. ...
  68. The marker for the following environment is out of date because the environment was updated by another client: '{0}'. Try ...
  69. The maximum number of items has already been deserialized into a single dictionary by the JavaScriptSerializer. To change ...
  70. The maximum number of unique Web test request URLs to report on has been exceeded; performance data for other requests will ...
  71. The maximum number of {0} errors has been reached. {1} total errors, {2} total warnings, and {3} total messages were encountered. ...
  72. The member '%1!ls!' either overrides/implements other members or is overridden/implemented by members in other types where ...
  73. The member '%1!ls!' either overrides/implements other members or is overridden/implemented by members in other types. The ...
  74. The member '%1!ls!' was defined in a referenced assembly. Renaming its references will result in build errors. Do you want ...
  75. The member '%1!ls!' was defined in a referenced assembly. Updating its references will result in build errors. Do you want ...