Visual Studio 2012
- The total number of Web test requests issued in a load test. The total includes both successful and failed requests, but ...
- The trace file could not be created in the specified directory ({0}). Make sure the directory exists and is writable by the ...
- The trace report cannot be displayed because it was collected by using a version of Concurrency Visualizer that is later ...
- The TraceLog Profiler detected an NGEN /profile assembly loaded into the process. Such assemblies are not supported. Collection ...
- The tradition continues! Visual Basic 2010 Express helps developers quickly create exciting interactive applications for ...
- The tradition continues! Visual C# 2010 Express helps developers quickly create exciting interactive applications for Windows. ...
- The tradition continues! Visual C++ 2010 Express helps developers quickly create exciting interactive applications for Windows. ...
- The Transact-SQL debugging session could not be started on the remote host. Verify that the instance of SQL Server is configured ...
- The trigger type for this build definition is set to continuous integration or rolling builds. To make sure the correct branches ...
- The trigger type for this build definition is set to schedule. To make sure the correct branch is built, a default branch ...
- The trigger you selected on the Trigger tab cannot be used in combination with the build process template you specified on ...
- The TSQL debugger has not been installed properly on the Visual Studio machine (ssdebugps.dll may not be registered properly). ...
- The two files selected for comparison are incompatible. Both files must either be sampling based or instrumentation based ...
- the type '%$T' (return type of GetEnumerator) must have a suitable public MoveNext member function and public Current property ...
- The type '%2!ls!' in '%1!ls!' conflicts with the imported namespace '%4!ls!' in '%3!ls!'. Using the type defined in '%1!ls!'. ...
- 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 ...
- 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!' ...
- 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!' ...
- 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!' ...
- 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 ...
- 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 ...
- The type '%4!ls!' cannot be used as type parameter '%3!ls!' in the generic type or method '%1!ls!'. There is no implicit ...
- The type '{0}' could not be resolved. This may occur if the code being tested depended on a typedef. C++ typedef resolution ...
- The type '{0}' could not be resolved. This may occur if the test project and code to be tested are being built for different ...
- The type '{0}' does not have 'null' as a proper value. To create a null value for a Nullable type use 'System.Nullable()'. ...
- The type '{0}' does not support the 'comparison' constraint because it is a record, union or struct with one or more structural ...
- The type '{0}' does not support the 'comparison' constraint. For example, it does not support the 'System.IComparable' interface ...
- The type '{0}' does not support the 'equality' constraint because it is a record, union or struct with one or more structural ...
- The type '{0}' does not support the operator '{1}'. Consider opening the module 'Microsoft.FSharp.Linq.NullableOperators'. ...
- The type '{0}' from assembly '{1}' is built with an older version of the Blend SDK, and is not supported in a {2} project. ...
- The type '{0}' has been marked as having an Explicit layout, but the field '{1}' has not been marked with the 'FieldOffset' ...
- The type '{0}' implements 'System.IComparable' explicitly but provides no corresponding override for 'Object.Equals'. An ...
- The type '{0}' in the service contract mapping has different TargetNamespace('{1}') and Name('{2}') than the TargetNamespace('{3}') ...
- The type '{0}' is an F# record type but its representation is private. You must specify BindingFlags.NonPublic to access ...
- The type '{0}' is an F# union type but its representation is private. You must specify BindingFlags.NonPublic to access private ...
- The type '{0}' is not a type whose values can be enumerated with this syntax, i.e. is not compatible with either seq , IEnumerable ...
- The type '{0}' is not a valid enumerator type , i.e. does not have a 'MoveNext()' method returning a bool, and a 'Current' ...
- The type '{0}' is the representation of an F# exception declaration but its representation is private. You must specify BindingFlags.NonPublic ...
- The type '{0}' is used in an invalid way. A value prior to '{1}' has an inferred type involving '{2}', which is an invalid ...
- The type '{0}' of the directive processor named '{1}' does not implement Microsoft.VisualStudio.TextTemplating.IDirectiveProcessor. ...
- The type '{0}' was not found. Verify that you are not missing an assembly reference and that all referenced assemblies have ...
- The type for column {0} in table {1} is currently {2} but is being changed to {3}. There is no implicit or explicit conversion. ...
- The type for variable '|1' will not be inferred because it is bound to a field in an enclosing scope. Either change the name ...
- The type implements the interface '{0}' but this is not revealed by the signature. You should list the interface in the signature, ...
- The type name '%1!ls!' could not be found in the global namespace. This type has been forwarded to assembly '%2!ls!' Consider ...
- The type name '%1!ls!' could not be found in the namespace '%2!ls!'. This type has been forwarded to assembly '%3!ls!' Consider ...
- The type name '%1!ls!' could not be found. This type has been forwarded to assembly '%2!ls!'. Consider adding a reference ...
- The type name {0} conflicts in whole or in part with the namespace name '{1}' defined in the .NET Framework. Rename the type ...
- The type name {0} conflicts in whole or in part with the namespace name '{1}'. Change either name to eliminate the conflict. ...
- The type of a field using the 'DefaultValue' attribute must admit default initialization, i.e. have 'null' as a proper value ...
- The type of actual parameter '%1$ls' should exactly match the type '%2$ls': This usually indicates that an enum formal was ...
- The type of build configuration to perform. 'Create' creates and agent and controller, 'Scale' adds agents to new or existing ...
- The type of service you're monitoring. Valid values include "Tfs", "Sps" and "Els". See ServiceDeploymentType enumeration. ...
- The Type of the role player provided in the DomainRoleAttribute for DomainRole '{0}' on DomainRelationship '{1}' is not a ...
- The Type on FilterDescriptor '{0}' cannot be set to 'Timestamp'. The Method '{1}' already contains a FilterDescriptor of ...
- The type parameter '%1!ls!' cannot be used with the 'as' operator because it does not have a class type constraint nor a ...
- The type parameters inferred for this value are not stable under the erasure of type abbreviations. This is due to the use ...
- The type provider '{0}' provided a method with a name '{1}' and metadata token '{2}', which is not reported among its methods ...
- The type provider '{0}' returned an invalid type from 'ApplyStaticArguments'. A type with name '{1}' was expected, but a ...
- The type provider does not have a valid constructor. A constructor taking either no arguments or one argument of type 'TypeProviderConfig' ...
- The type referenced through '{0}' is defined in an assembly that is not referenced. You must add a reference to assembly ...
- The type {0} can not be resolved within the current project. This can happen when setting WPF values in a Silverlight project, ...
- The type {0} could not be loaded. The assembly containing the class may be missing or may have additional references which ...
- The type {0} does not have a default query defined. A parameter-less query with IsDefault set to True is required. The type ...
- The type {0} is not strongly named. You must use strong name signing for assemblies that contain implementations of extensions. ...
- The typed dataset will not compile. Open the dataset in the Dataset Designer and verify each TableAdapter is set to a valid ...
- The TypeDescriptor '{0}' is of a DateTime type, but there is no Interpretation describing how the back-end interprets the ...
- The TypeDescriptor '{0}' references an Association '{1}' which could not be found on Entity with name '{2}' and namespace ...
- The TypeDescriptor '{0}' references an Identifier '{1}' which could not be found on Entity with name '{2}' and namespace ...
- The TypeDescriptor named '{0}' contains too many child TypeDescriptors that have the Associated Filter property set to the ...
- The TypeDescriptor with name '{0}' does not specify the name of the association being referred to in the Entity '{1}' in ...
- The TypeDescriptor with name '{0}' does not specify the name of the identifier being referred to in the Entity '{1}' in namespace ...
- The TypeDescriptor with name '{0}' has an invalid LobName. The LobName for a TypeDescriptor cannot be longer than {1} characters. ...
- The TypeDescriptor with name '{0}' has an invalid TypeName. The TypeName for a TypeDescriptor cannot be longer than {1} characters. ...
- The TypeName property of TypeDescriptor '{0}' is defined to be '{1}' which is a multi-dimension array that is not supported ...