Visual Studio 2013

  1. UTA007: Method {1} defined in class {0} does not have correct signature. Test method marked with the TestMethod attribute ...
  2. UTA008: Method {1} defined in class {0} does not have correct signature. Assembly initialization method marked with the AssemblyInitialize ...
  3. UTA009: Method {1} defined in class {0} does not have correct signature. Assembly cleanup method marked with the AssemblyCleanup ...
  4. UTA027: Method {1} defined in class {0} does not have correct signature. Class cleanup method marked with the ClassCleanup ...
  5. UTA028: Method {1} defined in class {0} does not have correct signature. Test initialization method marked with the TestInitialize ...
  6. UTA029: Method {1} defined in class {0} does not have correct signature. Test cleanup method marked with the TestCleanup ...
  7. UTA030: Method {1} defined in class {0} does not have correct signature. Class initialization method marked with the ClassInitialize ...
  8. UTA031: class {0} does not have valid TestContext property. TestContext must be of type TestContext, must be non-static, ...
  9. UTA042: Invalid use of DeploymentItem attribute on {0}.{1}. The DeploymentItem attribute can be defined only on a method ...
  10. UTA047: Invalid use of DataSource attribute on {0}.{1}. The DataSource attribute can be defined only on a method inside a ...
  11. UTA049: {0}.{1} has invalid DataSource attribute. Either DataSourceSettingName or ConnectionString and TableName must be ...
  12. UTA055: Illegal use of attributes on {0}.{1}. The TimeoutAttribute can be defined only inside a class marked with the TestClass ...
  13. UTA056: {0}.{1} has invalid WorkItem attribute. The work item id '{2}' must be a valid integer value and cannot be less than ...
  14. UTA057: The test '{0}' cannot be executed because the assembly '{1}' is not fully trusted by .NET Framework Security Policy. ...
  15. UTA058: The test engine cannot run tests in the assembly '{0}' because the assembly is not fully trusted by .NET Framework ...
  16. UTA059: The test DLL '{0}' was built using Visual Studio 2005, and cannot be run. To resolve this issue please rebuild the ...
  17. Valid Chars : String is interpreted as a set of valid characters. Empty string means that all possible characters are valid. ...
  18. Validates that the response time for the request is less than or equal to the response time goal as specified on the request. ...
  19. Validates that the response URL after redirects are followed is the same as the recorded response URL. QueryString parameters ...
  20. Validation passes if the text is found when this property is set true, or when the text is not found and this property is ...
  21. Value entered ('{0}') is not valid, reverted to previous value. Conversion Error: Input string was not in a correct format. ...
  22. Value is True if a higher value for this counter is better, for example Available MBytes. This property is used for reporting. ...
  23. Value of type '|1' cannot be converted to '|2'. Type mismatch could be due to mixing a file reference to '|3' in project ...
  24. Value of type '|1' cannot be converted to '|2'. Type mismatch could be due to the mixing of a file reference with a project ...
  25. Value of type '|1' cannot be converted to '|2'. You can use the 'Value' property to get the string value of the first element ...
  26. Value restriction. The value '{0}' has been inferred to have generic type {1} Either define '{2}' as a simple data term, ...
  27. Value restriction. The value '{0}' has been inferred to have generic type {1} Either make the arguments to '{2}' explicit ...
  28. Value restriction. The value '{0}' has generic type {1} Either make '{2}' into a function with explicit arguments or, if ...
  29. Value restriction. The value '{0}' has generic type {1} Either make the arguments to '{2}' explicit or, if you do not intend ...
  30. Value restriction. This member has been inferred to have generic type {0} Constructors and property getters/setters cannot ...
  31. Value types that redefine System.ValueType.Equals should redefine the equality operator as well to ensure that these members ...
  32. values cannot be converted to 'Char'. Use 'Microsoft.VisualBasic.ChrW' to interpret a numeric value as a Unicode character ...
  33. ValueToVisibilityConverter expects that the argument "parameter" be a non-null object of the same type as the argument "value". ...
  34. Vanity-enabled Azure Deployment must prefix the UrlHostNameAlias with "app.". Correct this setting in your ini file and try ...
  35. Variable '|1' is passed by reference before it has been assigned a value. A null reference exception could result at runtime. ...
  36. Variable '|1' is passed by reference before it has been assigned a value. A null reference exception could result at runtime. ...
  37. Variable '|1' is used before it has been assigned a value. A null reference exception could result at runtime. Make sure ...
  38. VBA code that you add to this document while debugging or running the project will be overwritten the next time that you ...
  39. VC++ Directories editing in Tools > Options has been deprecated. VC++ Directories are now available as a user property sheet ...
  40. Verifiable instrumentation works in all applications, but is less efficient. If disabled, data collection will run faster, ...
  41. Verify local Help content is installed. Verify you are able to get local Help content, and that the 500 error is specific ...
  42. Verify that 'Visual Studio Team Foundation Build Service Host' windows service dependencies are installed and not disabled ...
  43. Verify that a lab service account is configured in Team Foundation Server Administration Console for your team project collection, ...
  44. Verify that all the characters in the team project name are valid. Check that the following file extension' is not blocked ...
  45. Verify that the test agent account is a member of 'TeamTestAgentService' user group on {0}. You must use shadow accounts ...
  46. Verify that the value has proper arguments that can be passed to the annotation tool. The arguments should have "%f" as a ...
  47. Verify that Visual Studio remote debugger components have been installed on the server. To work around this issue, start ...
  48. Verifying that the SharePoint Central Administration Application Pool Identity match the service account cached by SP object ...
  49. Verifying that the web site and virtual directory chosen for this installation are the same as the ones chosen in previous ...
  50. Version %s of the common language runtime is not supported by this compiler. Using this version may cause unexpected results ...
  51. Version '{0}' of My Namespace extension '{1}' already exists in the current project. Do you want to overwrite it with version ...
  52. Version of the SCVMM console installed on the Team Foundation Server application tier machine is not compatible with the ...
  53. Versionspec: Date/Time D"any .Net Framework-supported format" or any of the date formats of the local machine Changeset number ...
  54. View a shelveset by entering its id. You can enter just the shelveset name to find shelvesets that you own. To go to a shelveset ...
  55. View has indexes. If you remove schema binding from it, the indexes will be dropped. Do you want to remove schema binding? ...
  56. View the shelveset that contains this code review to see information such as the list of files being reviewed and the changes ...
  57. View the shelveset that contains this suspended work to see information such as which files you changed and what changes ...
  58. Viewing managed memory data is not supported in this edition of Visual Studio. You need to upgrade to Visual Studio Ultimate. ...
  59. Virtual machine templates is configured to be joined to a domain. Virtual machines in a network isolated environment cannot ...
  60. Virtual methods defined on the class should not be called from constructors. If a derived class has overridden the method, ...
  61. VirtualAssociationSetEnd '{0}' and VirtualAssociationSetEnd '{1}' have different number of VirtualAssociationSetEndProperties. ...
  62. Visit Microsoft Help and Support site for Knowledge Base article on troubleshooting the installation of Visual Studio 2010. ...
  63. Visit Microsoft Help and Support site for Knowledge Base article on troubleshooting the installation of Visual Studio 2010. ...
  64. Visual Basic 6.0 (.vbp) files cannot be opened in Visual Studio. For more information about upgrading from Visual Basic 6.0, ...
  65. Visual Basic for VSTA Visual Basic provides a familiar, easy to understand and modern object-oriented programming language ...
  66. Visual Basic generates EventHandler delegates for events that use the following pattern: Event MyEvent(ByVal Sender As Object, ...
  67. Visual Basic Visual Basic provides a familiar, easy to understand and modern object-oriented programming language designed ...
  68. Visual Basic Visual Basic provides a familiar, easy to understand and modern object-oriented programming language designed ...
  69. Visual C# and Visual Basic for VSTA CSharp and Visual Basic for VSTA provides a familiar, easy to understand and modern object-oriented ...
  70. Visual C# for VSTA Visual C# is a modern, type-safe, and object-oriented programming language designed for developing applications ...
  71. Visual C# Visual C# is a modern, type-safe, and object-oriented programming language designed for developing applications ...
  72. Visual C# Visual C# is a modern, type-safe, and object-oriented programming language designed for developing applications ...
  73. Visual C++ did not find a suitable location to store its browsing database and IntelliSense files for the solution "%s." ...
  74. Visual C++ Event Log - This output window provides information to diagnose unexpected behavior with C++ IntelliSense or browsing. ...
  75. Visual C++ now provides improved safety in its C and C++ Libraries. This includes new and improved functions, additional ...