Visual Studio 2010

  1. 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. ...
  2. User "{0}" does not have a writable user environment key. Please make sure the associated application pool has the "Load ...
  3. User account required to run the remote debugger. This account must have the privilege to 'Log on as a service' in the Local ...
  4. User code should not create and raise exceptions of certain types that are reserved by the runtime or which are of a too ...
  5. User Control items are added to the following folder: {0}. An item with the specified name already exists in that folder. ...
  6. user defined binary operator ',' exists but no overload could convert all operands, default built-in binary operator ',' ...
  7. User Id: {0} Scenario: {1} Test: {2} URL: {3} Outcome: {4} Browser: {5} Network: {6} Start Time: {7} Duration: {8:F3} Agent: ...
  8. User Story Status by Config: Helps the team identify gaps in test coverage for each test configuration for each user story. ...
  9. User with security identifier "{0}" does not have a writable user environment key. Please make sure the associated application ...
  10. User {0} is not authorized to grant permissions to test controller service account. To fix this error, run this tool with ...
  11. User-defined functions, user-defined aggregates, CLR types, and methods on CLR types are not allowed in expressions in this ...
  12. UserInfo : Provides an overview of the My.User object and the Login Form template. It implements a simple custom authentication ...
  13. Users accessing your web server with basic authentication must have the "Log on locally" user right granted in the Windows ...
  14. Users with Read permission can create new forms from this template, but cannot open it in design mode. Everyone has Read ...
  15. Uses of this construct may result in the generation of unverifiable .NET IL code. This warning can be disabled using '-nowarn:9' ...
  16. Using '%ls' in a default locale to perform a case-insensitive compare to constant string '%ls'. Yields unexpected results ...
  17. Using '%ls' to perform a case-insensitive compare to constant string '%ls'. Yields unexpected results in non-English locales ...
  18. Using 'is' to test compatibility with 'dynamic' is essentially identical to testing compatibility with 'object' and will ...
  19. Using 'sizeof %ls' as parameter '%d' in call to '%ls' where '%ls' might be an array of wide characters, did you intend to ...
  20. Using base types as parameters to methods improves re-use of these methods if you only use methods & properties from the ...
  21. Using file associations requires that the application be full trust, target .NET Framework 3.5 or higher, and be available ...
  22. Using Help Library Manager, you can download new content from MSDN Online's content publication web site for use in offline ...
  23. Using out parameters might indicate a design flaw. Although there are legitimate times to use out parameters, their use frequently ...
  24. Using statement A Using block does three things: it creates and initializes variables in the resource list, it runs the code ...
  25. Using the iteration variable in a lambda expression may have unexpected results. Instead, create a local variable within ...
  26. Using the iteration variable in a query expression may have unexpected results. Instead, create a local variable within the ...
  27. Using the right Windows technology will deliver a great user experience. Get an overview of the different technologies to ...
  28. UTA004: Illegal use of attribute on {0}.{1}. The TestMethodAttribute can be defined only inside a class marked with the TestClass ...
  29. UTA005: Illegal use of attributes on {0}.{1}.The TestInitializeAttribute can be defined only inside a class marked with the ...
  30. UTA006: Illegal use of attributes on {0}.{1}. The TestCleanupAttribute can be defined only inside a class marked with the ...
  31. UTA007: Method {1} defined in class {0} does not have correct signature. Test method marked with the TestMethod attribute ...
  32. UTA008: Method {1} defined in class {0} does not have correct signature. Assembly initialization method marked with the AssemblyInitialize ...
  33. UTA009: Method {1} defined in class {0} does not have correct signature. Assembly cleanup method marked with the AssemblyCleanup ...
  34. UTA027: Method {1} defined in class {0} does not have correct signature. Class cleanup method marked with the ClassCleanup ...
  35. UTA028: Method {1} defined in class {0} does not have correct signature. Test initialization method marked with the TestInitialize ...
  36. UTA029: Method {1} defined in class {0} does not have correct signature. Test cleanup method marked with the TestCleanup ...
  37. UTA030: Method {1} defined in class {0} does not have correct signature. Class initialization method marked with the ClassInitialize ...
  38. UTA031: class {0} does not have valid TestContext property. TestContext must be of type TestContext, must be non-static, ...
  39. UTA042: Invalid use of DeploymentItem attribute on {0}.{1}. The DeploymentItem attribute can be defined only on a method ...
  40. UTA047: Invalid use of DataSource attribute on {0}.{1}. The DataSource attribute can be defined only on a method inside a ...
  41. UTA049: {0}.{1} has invalid DataSource attribute. Either DataSourceSettingName or ConnectionString and TableName must be ...
  42. UTA055: Illegal use of attributes on {0}.{1}. The TimeoutAttribute can be defined only inside a class marked with the TestClass ...
  43. UTA056: {0}.{1} has invalid WorkItem attribute. The work item id '{2}' must be a valid integer value and cannot be less than ...
  44. UTA057: The test '{0}' cannot be executed because the assembly '{1}' is not fully trusted by .NET Framework Security Policy. ...
  45. UTA058: The test engine cannot run tests in the assembly '{0}' because the assembly is not fully trusted by .NET Framework ...
  46. UTA059: The test DLL '{0}' was built using Visual Studio 2005, and cannot be run. To resolve this issue please rebuild the ...
  47. Valid Chars : String is interpreted as a set of valid characters. Empty string means that all possible characters are valid. ...
  48. Valid dialog or user control resource files must be generated by the Visual Studio Form Designer and the Localizable property ...
  49. Validates that the response time for the request is less than or equal to the response time goal as specified on the request. ...
  50. Validates that the response URL after redirects are followed is the same as the recorded response URL. QueryString parameters ...
  51. ValidateText : Provides a comparison of two ways of validating text: by using regular expressions in a custom TextBox control ...
  52. Validation ($SCHEMA$): This attribute name must be followed by an equal (=) sign and a value. If the value is in quotation ...
  53. Validation ($SCHEMA$): This attribute requires a value. If the value is enclosed in quotation marks, the quotation marks ...
  54. Validation passes if the text is found when this property is set true, or when the text is not found and this property is ...
  55. Validation rule '{0}' received unexpected value '{1}'. (This could be caused by assigning the wrong ValidationStep to the ...
  56. value for Name property is not valid. Name must start with a letter or an underscore and can contain only letters, digits, ...
  57. Value is True if a higher value for this counter is better, for example Available MBytes. This property is used for reporting. ...
  58. Value of type '|1' cannot be converted to '|2'. Type mismatch could be due to mixing a file reference to '|3' in project ...
  59. Value of type '|1' cannot be converted to '|2'. Type mismatch could be due to the mixing of a file reference with a project ...
  60. Value of type '|1' cannot be converted to '|2'. You can use the 'Value' property to get the string value of the first element ...
  61. Value restriction. The value '{0}' has been inferred to have generic type {1} Either define '{2}' as a simple data term, ...
  62. Value restriction. The value '{0}' has been inferred to have generic type {1} Either make the arguments to '{2}' explicit ...
  63. Value restriction. The value '{0}' has generic type {1} Either make '{2}' into a function with explicit arguments or, if ...
  64. Value restriction. The value '{0}' has generic type {1} Either make the arguments to '{2}' explicit or, if you do not intend ...
  65. Value restriction. This member has been inferred to have generic type {0} Constructors and property getters/setters cannot ...
  66. Value types that redefine System.ValueType.Equals should redefine the equality operator as well to ensure that these members ...
  67. Value {0} exceeds the maximum value of SmallDateTime {1}. Modify the value to be less than or equal to the maximum value ...
  68. Value {0} exceeds the maximum value of SmallMoney {1}. Modify the value to be less than or equal to the maximum value of ...
  69. Value {0} is less than the minimum value of SmallDateTime {1}. Modify the value to be greater than or equal to the minimum ...
  70. Value {0} is less than the minimum value of SmallMoney {1}. Modify the value to be greater than or equal to the minimum value ...
  71. Value {0} is less than the minimum value of Time {1}. Modify the value to be greater than or equal to the minimum value of ...
  72. values cannot be converted to 'Char'. Use 'Microsoft.VisualBasic.ChrW' to interpret a numeric value as a Unicode character ...
  73. Values for advanceWidths and glyphOffsets constitute too large of a GlyphRun. The area of its bounding box, measured in renderingEmSize ...
  74. Values marked with 'LiteralAttribute' must currently be simple integer, character, Boolean, string or floating point constants ...
  75. Vardecimal support is enabled for the database but disabled for the project. See SQL Server Books Online for more information ...