Visual Studio 2010

  1. The test settings file you are using specifies to run tests with code coverage enabled. To use this feature, Visual Studio ...
  2. The test settings have been configured to collect data and diagnostics for a diagnostic data adapter that has an empty assembly-qualified ...
  3. The test settings have been configured to collect data and diagnostics for an agent containing two diagnostic data adapters ...
  4. The test settings have been configured to collect data and diagnostics for two agents with the name '{0}'. Agent names must ...
  5. The test settings specify a remote machine for running tests, for which Visual Studio Premium or Visual Studio Ultimate is ...
  6. The test started running in response to request '{0}', but an error occurred before the test finished executing: {1}. {2} ...
  7. The test suite has the same name as another test suite that has the same parent. Each test suite that has the same parent ...
  8. The testing policy requires all check-in tests to pass because test impact information is unavailable. {0} test(s) have not ...
  9. The testing policy requires all check-in tests to pass. {0} test(s) have not yet passed and are not in the current solution. ...
  10. The testing policy requires all check-in tests to pass. {0} test(s) have not yet passed. Open this item to view and run tests. ...
  11. The testing policy requires all check-in tests to pass. {0} test(s) have not yet passed. Open this item to view the tests ...
  12. The testing policy requires all recommended check-in tests to pass. {0} test(s) have not yet passed. Open this item to view ...
  13. The text '|' is not valid because a parenthesis character is not matched. Make sure every opening parenthesis appears with ...
  14. The text '|' is not valid because a quotation mark is not matched. Make sure every opening quotation mark appears with a ...
  15. The text entered does not represent a well-formed XML comment. Click OK to edit the documentation text, or click Cancel to ...
  16. The text that appears in the "Other Actions" drop-down of the "Actions" group in the Ribbon for items that display this form ...
  17. The TextInfo.ANSICodePage and TextInfo.OEMCodePage properties must be the same when either one is a multi-byte code page. ...
  18. The thread tried to access a page that was not present, and the system was unable to load the page. For example, this exception ...
  19. The thread tried to read or write data that is misaligned on hardware that does not provide alignment. For example, 16-bit ...
  20. The time allowed for Windows services to start was increased from {0:N0} seconds to {1:N0} seconds. This affects all Windows ...
  21. The time range '|' is not valid because it is not in the form ' and '. Type the range again in the correct form, such as ...
  22. The time required to execute this query is greater than the query time-out limit set for this server. For more information, ...
  23. The time to collect and process performance counters ({0} ms) exceeded the length of the sampling interval. One or more sampling ...
  24. The time, in seconds, that Code Analysis should wait for analysis of a single item to complete before it aborts analysis. ...
  25. The timeout argument must receive an numeric value that is 0 (no timeout) or greater (minutes to wait). The value provided ...
  26. The token you have entered is not valid. The only valid characters in a comment token are alphanumeric characters, _, $, ...
  27. The tool '{0}' is already active in this editing context. You cannot activate the same instance of a task tool more than ...
  28. The ToolId property for a service definition cannot be the empty string. To represent the service definition not having a ...
  29. The total elapsed time spent processing all instances of this ASP.NET request or executing commands against the database, ...
  30. The total number of transactions issued in a load test. Transactions refer to either transactions defined in a Web test, ...
  31. The total number of Web test requests issued in a load test. The total includes both successful and failed requests, but ...
  32. The trace file could not be created in the specified directory ({0}). Make sure the directory exists and is writable by the ...
  33. The TraceLog Profiler detected an NGEN /profile assembly loaded into the process. Such assemblies are not supported. Collection ...
  34. The tradition continues! Visual Basic 2010 Express helps developers quickly create exciting interactive applications for ...
  35. The tradition continues! Visual C# 2010 Express helps developers quickly create exciting interactive applications for Windows. ...
  36. The tradition continues! Visual C++ 2010 Express helps developers quickly create exciting interactive applications for Windows. ...
  37. The Transact-SQL debugging session could not be started on the remote host. Verify that the instance of SQL Server is configured ...
  38. The trigger you selected on the Trigger tab cannot be used in combination with the build process template you specified on ...
  39. The Trust Center contains security and privacy settings. These settings help keep your computer secure. We recommend that ...
  40. The TSQL debugger has not been installed properly on the Visual Studio machine (ssdebugps.dll may not be registered properly). ...
  41. The two files selected for comparison are incompatible. Both files must either be sampling based or instrumentation based ...
  42. The two-column comma separated style shows a two-column view of the titles for items in the list with all the other field ...
  43. the type '%$T' (return type of GetEnumerator) must have a suitable public MoveNext member function and public Current property ...
  44. The type '%2!ls!' in '%1!ls!' conflicts with the imported namespace '%4!ls!' in '%3!ls!'. Using the type defined in '%1!ls!'. ...
  45. The type '%3!ls!' must be a non-nullable value type in order to use it as parameter '%2!ls!' in the generic type or method ...
  46. The type '%3!ls!' must be a reference type in order to use it as parameter '%2!ls!' in the generic type or method '%1!ls!' ...
  47. The type '%4!ls!' cannot be used as type parameter '%3!ls!' in the generic type or method '%1!ls!'. The nullable type '%4!ls!' ...
  48. The type '%4!ls!' cannot be used as type parameter '%3!ls!' in the generic type or method '%1!ls!'. The nullable type '%4!ls!' ...
  49. The type '%4!ls!' cannot be used as type parameter '%3!ls!' in the generic type or method '%1!ls!'. There is no boxing conversion ...
  50. The type '%4!ls!' cannot be used as type parameter '%3!ls!' in the generic type or method '%1!ls!'. There is no boxing conversion ...
  51. The type '%4!ls!' cannot be used as type parameter '%3!ls!' in the generic type or method '%1!ls!'. There is no implicit ...
  52. The type '{0}' cannot be loaded because it has the same display name ('{1}') as the type '{2}'. All types must have a unique ...
  53. The type '{0}' could not be found. Ensure that the assembly containing the type is referenced. If the assembly is part of ...
  54. The type '{0}' could not be resolved. This may occur if the code being tested depended on a typedef. C++ typedef resolution ...
  55. The type '{0}' could not be resolved. This may occur if the test project and code to be tested are being built for different ...
  56. The type '{0}' does not support the 'comparison' constraint because it is a record, union or struct with one or more structural ...
  57. The type '{0}' does not support the 'comparison' constraint. For example, it does not support the 'System.IComparable' interface ...
  58. The type '{0}' does not support the 'equality' constraint because it is a record, union or struct with one or more structural ...
  59. The type '{0}' has been marked as having an Explicit layout, but the field '{1}' has not been marked with the 'FieldOffset' ...
  60. The type '{0}' has not been implemented correctly. The implementor of the type should ensure that all parameters and return ...
  61. The type '{0}' implements 'System.IComparable' explicitly but provides no corresponding override for 'Object.Equals'. An ...
  62. The type '{0}' in the service contract mapping has different TargetNamespace('{1}') and Name('{2}') than the TargetNamespace('{3}') ...
  63. The type '{0}' is not a type whose values can be enumerated with this syntax, i.e. is not compatible with either seq , IEnumerable ...
  64. The type '{0}' is used in an invalid way. A value prior to '{1}' has an inferred type involving '{2}', which is an invalid ...
  65. The type '{0}' of the directive processor named '{1}' does not derive from Microsoft.VisualStudio.TextTemplating.DirectiveProcessor. ...
  66. The type '{0}' was not found. Verify that you are not missing an assembly reference and that all referenced assemblies have ...
  67. The type '{0}', specified as installer for components of type '{1}', is not an installer. It must inherit from System.Configuration.Installer. ...
  68. The type for column {0} in table {1} is currently {2} but is being changed to {3}. There is no implicit or explicit conversion. ...
  69. The type for variable '|1' will not be inferred because it is bound to a field in an enclosing scope. Either change the name ...
  70. The type for variable '|1' will not be inferred because it is bound to a field in an enclosing scope. Either change the name ...
  71. The type implements the interface '{0}' but this is not revealed by the signature. You should list the interface in the signature, ...
  72. The type name '%1!ls!' could not be found in the global namespace. This type has been forwarded to assembly '%2!ls!' Consider ...
  73. The type name '%1!ls!' could not be found in the namespace '%2!ls!'. This type has been forwarded to assembly '%3!ls!' Consider ...
  74. The type name '%1!ls!' could not be found. This type has been forwarded to assembly '%2!ls!'. Consider adding a reference ...
  75. The type name {0} conflicts in whole or in part with the namespace name '{1}' defined in the .NET Framework. Rename the type ...