Visual Studio 2012

  1. Use: wdexpress solutionfile | projectfile | anyfile.ext switches The first argument for wdexpress is usually a solution file ...
  2. Used by Analysis Services processing. Indicates the maximum number of commands in parallel. If set to 0, the instance of ...
  3. Used by Visual Studio Enterprise tools to coordinate test runs. If this service is stopped, remote test runs will not be ...
  4. Used by Visual Studio Enterprise tools to execute test runs. If this service is stopped, remote test runs may not be able ...
  5. Used to implement standard C++ behavior for the for statement loops with Microsoft extensions (/Za, /Ze (Disable Language ...
  6. Used to specify a solution folder structure in the .vstemplate. If specified the project wizard will create a folder structure ...
  7. Used within the style of an item control to specify the place in the control's visual tree where the content is to be added. ...
  8. User "{0}" does not have a writable user environment key. Please make sure the associated application pool has the "Load ...
  9. User '[2]' has previously initiated an install for product '[3]'. That user will need to run that install again before they ...
  10. User '[2]' has previously initiated an install for product '[3]'. That user will need to run that install again before they ...
  11. User account required to run the remote debugger. This account must have the privilege to 'Log on as a service' in the Local ...
  12. User code should not create and raise exceptions of certain types that are reserved by the runtime or which are of a too ...
  13. User Control items are added to the following folder: {0}. An item with the specified name already exists in that folder. ...
  14. user defined binary operator ',' exists but no overload could convert all operands, default built-in binary operator ',' ...
  15. User does not have access to the invoked operation. Your session may have timed out. Please restart the application. Operation ...
  16. User Id: {0} Scenario: {1} Test: {2} URL: {3} Outcome: {4} Browser: {5} Network: {6} Start Time: {7} Duration: {8:F3} Agent: ...
  17. User mode ETW events were lost during collection. This report may be missing Markers or contain unresolved stack frames. ...
  18. User Story Status by Config: Helps the team identify gaps in test coverage for each test configuration for each user story. ...
  19. User with security identifier "{0}" does not have a writable user environment key. Please make sure the associated application ...
  20. User {0} is a member of {1} role in SCVMM server. When connecting with SCVMM 2008 R2 server, Team Foundation Server requires ...
  21. User {0} is not authorized to grant permissions to test controller service account. To fix this error, run this tool with ...
  22. User-defined functions, user-defined aggregates, CLR types, and methods on CLR types are not allowed in expressions in this ...
  23. UserControl chosen as the templated item because it supports visual state management Loaded/unloaded events explicitly subscribe ...
  24. Uses of this construct may result in the generation of unverifiable .NET IL code. This warning can be disabled using '-nowarn:9' ...
  25. Using '%1$ls' in a default locale to perform a case-insensitive compare to constant string '%2$ls'. Yields unexpected results ...
  26. Using '%1$ls' to perform a case-insensitive compare to constant string '%2$ls'. Yields unexpected results in non-English ...
  27. Using 'is' to test compatibility with 'dynamic' is essentially identical to testing compatibility with 'object' and will ...
  28. Using a local machine user account for the Team Foundation Server service logon may prevent you from adding domain user accounts ...
  29. Using a Type Provider from a source that is unknown or not trusted can expose your computer to security threats, as it will ...
  30. Using base types as parameters to methods improves re-use of these methods if you only use methods & properties from the ...
  31. Using Bing Map API routing service to calculate the driving distance between two Geolocations. http://www.microsoft.com/maps/developers/mapapps.aspx ...
  32. Using events defined in an assembly that was referenced with 'Embed Interop Types' set to true requires a reference that ...
  33. Using file associations requires that the application be full trust, target .NET Framework 3.5 or higher, and be available ...
  34. Using Isolation mode to run tests as required by effective Platform:{0} and .Net Framework:{1} settings for test run. Use ...
  35. Using Isolation mode to run the tests as diagnostic data adapters were enabled in the runsettings. Use the /inIsolation parameter ...
  36. Using out parameters might indicate a design flaw. Although there are legitimate times to use out parameters, their use frequently ...
  37. Using possibly uninitialized memory '%1$ls': The variable has had its address taken but no assignment to it has been discovered. ...
  38. Using statement A Using block does three things: it creates and initializes variables in the resource list, it runs the code ...
  39. Using the iteration variable in a lambda expression may have unexpected results. Instead, create a local variable within ...
  40. Using the iteration variable in a query expression may have unexpected results. Instead, create a local variable within the ...
  41. Using the MSBuild v3.5 solution wrapper generator with a tools version of {0} because the solution file format was version ...
  42. Using this version instead of original version "{0}" in "{1}" because there is a more recent version of this framework file. ...
  43. UTA004: Illegal use of attribute on {0}.{1}. The TestMethodAttribute can be defined only inside a class marked with the TestClass ...
  44. UTA005: Illegal use of attributes on {0}.{1}.The TestInitializeAttribute can be defined only inside a class marked with the ...
  45. UTA006: Illegal use of attributes on {0}.{1}. The TestCleanupAttribute can be defined only inside a class marked with the ...
  46. UTA007: Method {1} defined in class {0} does not have correct signature. Test method marked with the TestMethod attribute ...
  47. UTA007: Method {1} defined in class {0} does not have correct signature. Test method marked with the TestMethod attribute ...
  48. UTA007: Method {1} defined in class {0} does not have correct signature. Test method marked with the TestMethod attribute ...
  49. UTA008: Method {1} defined in class {0} does not have correct signature. Assembly initialization method marked with the AssemblyInitialize ...
  50. UTA009: Method {1} defined in class {0} does not have correct signature. Assembly cleanup method marked with the AssemblyCleanup ...
  51. UTA027: Method {1} defined in class {0} does not have correct signature. Class cleanup method marked with the ClassCleanup ...
  52. UTA028: Method {1} defined in class {0} does not have correct signature. Test initialization method marked with the TestInitialize ...
  53. UTA029: Method {1} defined in class {0} does not have correct signature. Test cleanup method marked with the TestCleanup ...
  54. UTA030: Method {1} defined in class {0} does not have correct signature. Class initialization method marked with the ClassInitialize ...
  55. UTA031: class {0} does not have valid TestContext property. TestContext must be of type TestContext, must be non-static, ...
  56. UTA042: Invalid use of DeploymentItem attribute on {0}.{1}. The DeploymentItem attribute can be defined only on a method ...
  57. UTA047: Invalid use of DataSource attribute on {0}.{1}. The DataSource attribute can be defined only on a method inside a ...
  58. UTA049: {0}.{1} has invalid DataSource attribute. Either DataSourceSettingName or ConnectionString and TableName must be ...
  59. UTA055: Illegal use of attributes on {0}.{1}. The TimeoutAttribute can be defined only inside a class marked with the TestClass ...
  60. UTA056: {0}.{1} has invalid WorkItem attribute. The work item id '{2}' must be a valid integer value and cannot be less than ...
  61. UTA057: The test '{0}' cannot be executed because the assembly '{1}' is not fully trusted by .NET Framework Security Policy. ...
  62. UTA058: The test engine cannot run tests in the assembly '{0}' because the assembly is not fully trusted by .NET Framework ...
  63. UTA059: The test DLL '{0}' was built using Visual Studio 2005, and cannot be run. To resolve this issue please rebuild the ...
  64. Valid Chars : String is interpreted as a set of valid characters. Empty string means that all possible characters are valid. ...
  65. Validates that the response time for the request is less than or equal to the response time goal as specified on the request. ...
  66. Validates that the response URL after redirects are followed is the same as the recorded response URL. QueryString parameters ...
  67. Validation passes if the text is found when this property is set true, or when the text is not found and this property is ...
  68. Validation rule '{0}' received unexpected value '{1}'. (This could be caused by assigning the wrong ValidationStep to the ...
  69. Value entered ('{0}') is not valid, reverted to previous value. Conversion Error: Input string was not in a correct format. ...
  70. value for Name property is not valid. Name must start with a letter or an underscore and can contain only letters, digits, ...
  71. Value is True if a higher value for this counter is better, for example Available MBytes. This property is used for reporting. ...
  72. Value of type '|1' cannot be converted to '|2'. Type mismatch could be due to mixing a file reference to '|3' in project ...
  73. Value of type '|1' cannot be converted to '|2'. Type mismatch could be due to the mixing of a file reference with a project ...
  74. Value of type '|1' cannot be converted to '|2'. You can use the 'Value' property to get the string value of the first element ...
  75. Value restriction. The value '{0}' has been inferred to have generic type {1} Either define '{2}' as a simple data term, ...