Visual Studio 2013

  1. The testing policy requires all check-in tests to pass. {0} test(s) have not yet passed and are not in the current solution. ...
  2. 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. ...
  3. The testing policy requires all check-in tests to pass. {0} test(s) have not yet passed. Open this item to view the tests ...
  4. The testing policy requires all recommended check-in tests to pass. {0} test(s) have not yet passed. Open this item to view ...
  5. The text entered does not represent a well-formed XML comment. Click OK to edit the documentation text, or click Cancel to ...
  6. The text template that is used to generate code from each model element in the namespace. The template path can be absolute ...
  7. The texture coordinates of the current pixel, as determined by interpolating between the texture coordinate attributes of ...
  8. The thread tried to access a page that was not present, and the system was unable to load the page. For example, this exception ...
  9. The thread tried to read or write data that is misaligned on hardware that does not provide alignment. For example, 16-bit ...
  10. The thumbprint of the SSL certificate. You can follow the instructions on the following page to obtain an SSL certificate ...
  11. The time allowed for Windows services to start was increased from {0:N0} seconds to {1:N0} seconds. This affects all Windows ...
  12. The time in seconds, normalized to the range 0, 1) such that when time reaches 1, it resets to 0. You can use this as a parameter ...
  13. The time in seconds. You can use this as a parameter in shader calculations, for example, to animate texture coordinates, ...
  14. The time to collect and process performance counters ({0} ms) exceeded the length of the sampling interval. One or more sampling ...
  15. The time, in seconds, that Code Analysis should wait for analysis of a single item to complete before it aborts analysis. ...
  16. The timeout argument must receive an numeric value that is 0 (no timeout) or greater (minutes to wait). The value provided ...
  17. The timeout is the maximum amount of time allowed for a deployment to be performed on the target server. If the timeout is ...
  18. The timeout is the maximum amount of time allowed for a deployment to be performed on the target server. If the timeout is ...
  19. The token you have entered is not valid. The only valid characters in a comment token are alphanumeric characters, _, $, ...
  20. The tool '{0}' is already active in this editing context. You cannot activate the same instance of a task tool more than ...
  21. The tool AppCert.exe wasn't found. Either the Windows Software Development Kit is not installed properly or this version ...
  22. The ToolId property for a service definition cannot be the empty string. To represent the service definition not having a ...
  23. The tools and components listed below this node are provided to add additional functionality to your Team Foundation Server ...
  24. The total amount of tile_static memory (%d bytes) exceeds the limit of %d bytes when compiling the call graph for the concurrency::parallel_for_each ...
  25. The total elapsed time spent processing all instances of this ASP.NET request or executing commands against the database, ...
  26. The total number of samplers (%d captured and %d predefined) exceed %d when compiling the call graph for the concurrency::parallel_for_each ...
  27. The total number of transactions issued in a load test. Transactions refer to either transactions defined in a Web test, ...
  28. The total number of Web test requests issued in a load test. The total includes both successful and failed requests, but ...
  29. The trace file could not be created in the specified directory ({0}). Make sure the directory exists and is writable by the ...
  30. The trace report cannot be displayed because it was collected by using a version of Concurrency Visualizer that is later ...
  31. The TraceLog Profiler detected an NGEN /profile assembly loaded into the process. Such assemblies are not supported. Collection ...
  32. The Transact-SQL debugging session could not be started on the remote host. Verify that the instance of SQL Server is configured ...
  33. The trial for Release Management Client for Visual Studio 2013 has expired. Thank you for your participation. Upgrade to ...
  34. The trial for Release Management Client for Visual Studio 2013 will expire soon. Thank you for your participation. Upgrade ...
  35. The trial for Release Management Server for Team Foundation Server 2013 has expired. Thank you for your participation. Upgrade ...
  36. The trial for Release Management Server for Team Foundation Server 2013 will expire soon. Thank you for your participation. ...
  37. The trigger type for this build definition is set to continuous integration or rolling builds. To make sure the correct branches ...
  38. The trigger type for this build definition is set to schedule. To make sure the correct branch is built, a default branch ...
  39. The trigger you selected on the Trigger tab cannot be used in combination with the build process template you specified on ...
  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 type '%$T' (return type of GetEnumerator) must have a suitable public MoveNext member function and public Current property ...
  43. The type '%2!ls!' in '%1!ls!' conflicts with the imported namespace '%4!ls!' in '%3!ls!'. Using the type defined in '%1!ls!'. ...
  44. 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 ...
  45. 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!' ...
  46. 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!' ...
  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!'. There is no boxing conversion ...
  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 implicit ...
  51. The type '{0}' could not be resolved. This may occur if the code being tested depended on a typedef. C++ typedef resolution ...
  52. The type '{0}' could not be resolved. This may occur if the test project and code to be tested are being built for different ...
  53. The type '{0}' does not have 'null' as a proper value. To create a null value for a Nullable type use 'System.Nullable()'. ...
  54. The type '{0}' does not support the 'comparison' constraint because it is a record, union or struct with one or more structural ...
  55. The type '{0}' does not support the 'comparison' constraint. For example, it does not support the 'System.IComparable' interface ...
  56. The type '{0}' does not support the 'equality' constraint because it is a record, union or struct with one or more structural ...
  57. The type '{0}' does not support the operator '{1}'. Consider opening the module 'Microsoft.FSharp.Linq.NullableOperators'. ...
  58. The type '{0}' from assembly '{1}' is built with an older version of the Blend SDK, and is not supported in a {2} project. ...
  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}' implements 'System.IComparable' explicitly but provides no corresponding override for 'Object.Equals'. An ...
  61. The type '{0}' in the service contract mapping has different TargetNamespace('{1}') and Name('{2}') than the TargetNamespace('{3}') ...
  62. The type '{0}' is an F# record type but its representation is private. You must specify BindingFlags.NonPublic to access ...
  63. The type '{0}' is an F# union type but its representation is private. You must specify BindingFlags.NonPublic to access private ...
  64. The type '{0}' is not a type whose values can be enumerated with this syntax, i.e. is not compatible with either seq , IEnumerable ...
  65. The type '{0}' is not a valid enumerator type , i.e. does not have a 'MoveNext()' method returning a bool, and a 'Current' ...
  66. The type '{0}' is the representation of an F# exception declaration but its representation is private. You must specify BindingFlags.NonPublic ...
  67. The type '{0}' is used in an invalid way. A value prior to '{1}' has an inferred type involving '{2}', which is an invalid ...
  68. The type '{0}' of the directive processor named '{1}' does not implement Microsoft.VisualStudio.TextTemplating.IDirectiveProcessor. ...
  69. The type '{0}' was not found. Verify that you are not missing an assembly reference and that all referenced assemblies have ...
  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 ...