UI Translation

.NET Framework

  1. The type '{0}' appears in two structurally incompatible initializations within a single LINQ to Entities query. A type can ...
  2. The type '{0}' cannot be serialized because its default accessor is decorated with declarative security permission attributes. ...
  3. The type '{0}' cannot be serialized because its parameterless constructor is decorated with declarative security permission ...
  4. The type '{0}' cannot be serialized because the {1}({2}) method is decorated with declarative security permission attributes. ...
  5. The type '{0}' cannot be serialized to JSON because its IsReference setting is '{1}'. The JSON format does not support references ...
  6. The type '{0}' could not be found. Ensure that the assembly containing the type is referenced. If the assembly is part of ...
  7. The type '{0}' could not be loaded. If the type is located in the App_Code folder, please check that it compiles. If the ...
  8. The type '{0}' doesn't have any key members. A RelationshipType or EntityType must either have key members or a BaseType ...
  9. The type '{0}' has not been implemented correctly. The implementor of the type should ensure that all parameters and return ...
  10. The type '{0}' in config has '{1}' generic parameter(s) but '{2}' generic argument(s) were provided. The number of generic ...
  11. The type '{0}' in config has '{1}' generic parameters(s). Parameter '{2}' cannot be accessed. Parameter index must be greater ...
  12. The type '{0}' in the service contract mapping has different TargetNamespace('{1}') and Name('{2}') than the TargetNamespace('{3}') ...
  13. The type '{0}' is ambiguous: it could come from assembly '{1}' or from assembly '{2}'. Please specify the assembly explicitly ...
  14. The type '{0}' is an abstract type. For PUT, POST and DELETE operations, the type specified must be a concrete type with ...
  15. The type '{0}' is not a valid device adapter, because it does not implement the interface '{1}'. Use another type, or modify ...
  16. The Type '{0}' is not unique. This may be caused by the types only differing in case which is not compatible with the current ...
  17. The type '{0}' of the member '{1}' in the conceptual side type '{2}' does not match with the type '{3}' of the member '{4}' ...
  18. The type '{0}' that is being loaded conflicts with the type '{1}' that is already loaded because they have the same namespace ...
  19. The type '{0}'('{1}') of the member '{2}' in the conceptual type '{3}' doesn't match with the type '{4}'('{5}') of the member ...
  20. The type '{0}', provided as the Factory attribute value in the 'system.serviceModel/serviceHostingEnvironment/serviceActivations' ...
  21. The type '{0}', provided as the Service attribute value in the ServiceHost directive, or provided in the configuration element ...
  22. The type '{0}', specified as installer for components of type '{1}', is not an installer. It must inherit from System.Configuration.Installer. ...
  23. The type '{2}' must be a non-nullable value type in order to use it as parameter '{1}' in the generic type or method '{0}' ...
  24. The type '{3}' cannot be used as type parameter '{2}' in the generic type or method '{0}'. The nullable type '{3}' does not ...
  25. The type '{3}' cannot be used as type parameter '{2}' in the generic type or method '{0}'. The nullable type '{3}' does not ...
  26. The type '{3}' cannot be used as type parameter '{2}' in the generic type or method '{0}'. There is no boxing conversion ...
  27. The type '{3}' cannot be used as type parameter '{2}' in the generic type or method '{0}'. There is no boxing conversion ...
  28. The type '{3}' cannot be used as type parameter '{2}' in the generic type or method '{0}'. There is no implicit reference ...
  29. The type contains two attributes with the same name '{0}'. Multiple attributes with the same name in one type are not supported. ...
  30. The type contains two elements with the same name '{0}'. Multiple elements with the same name in one type are not supported ...
  31. The type definition of this field has layout information but has an invalid managed/unmanaged type combination or is unmarshalable. ...
  32. The type for the property '{0}' cannot be serialized using the binary serializer, since the type is not marked as serializable. ...
  33. The type for variable '|1' will not be inferred because it is bound to a field in an enclosing scope. Either change the name ...
  34. The type for variable '|1' will not be inferred because it is bound to a field in an enclosing scope. Either change the name ...
  35. The type has explicit layout, and has been exported as an empty record. Types with explicit layout can only be properly exported ...
  36. The type name '%1!ls!' could not be found in the global namespace. This type has been forwarded to assembly '%2!ls!' Consider ...
  37. The type name '%1!ls!' could not be found in the namespace '%2!ls!'. This type has been forwarded to assembly '%3!ls!' Consider ...
  38. The type name '%1!ls!' could not be found. This type has been forwarded to assembly '%2!ls!'. Consider adding a reference ...
  39. The type name '{0}' is used for both an EntityContainer and a type. Duplicates are not allowed, please change one of the ...
  40. The type of authentication that your SMTP server uses, if any. If your SMTP server uses Basic authentication , provide the ...
  41. The Type of object passed as parameter '{0}' is not derived from {1}. Ensure that the type of object passed is either of ...
  42. The type of page you have requested is not served because it has been explicitly forbidden. {0} Please review the URL below ...
  43. The type of parameter '{0}' does not match the type '{1}' specified in operation '{2}' of the implemented contract '{3}'. ...
  44. The type of the TypeUsage object specified for the metadata parameter is not compatible with the type to which an EdmMember ...
  45. The type of the value object did not match the specified RegistryValueKind or the object could not be properly converted. ...
  46. The type or member named '{0}' could not be loaded because it has two incompatible attributes: '{1}' and '{2}'. To fix the ...
  47. The type or method has {1} generic parameter(s), but {0} generic argument(s) were provided. A generic argument must be provided ...
  48. The type parameter '%1!ls!' cannot be used with the 'as' operator because it does not have a class type constraint nor a ...
  49. The type serialized in the .resources file was not the same type that the .resources file said it contained. Expected '{0}' ...
  50. The type specified for the argument in collection '{0}' at position {1} does not match the expected type. The type specified ...
  51. The type specified in the configuration property "inherits" must inherit from the type System.Web.Profile.HttpProfileBase ...
  52. The type {0} has a redirected member {1} which is deprecated. This member does not exist in the winmd and hence will not ...
  53. The type {0} may not be used in this context. To use {0} as a parameter, return type, or member of a class or struct, the ...
  54. The type {0} provided as the Factory attribute value in the ServiceHost directive does not implement a default constructor. ...
  55. The type {0} registered as a policy extension does not have a public default constructor. Policy extensions must have a public ...
  56. The type {0} registered as a WSDL extension does not have a public default constructor. WSDL extensions must have a public ...
  57. The type {0} was not expected. Use the XmlInclude or SoapInclude attribute to specify types that are not known statically. ...
  58. The type {1} defines a MessageContract but also derives from a type {0} that does not define a MessageContract. All of the ...
  59. The types in the assembly '{0}' cannot be loaded because the assembly contains the EdmSchemaAttribute, and the closure of ...
  60. The types of all properties in the Dependent Role of a referential constraint must be the same as the corresponding property ...
  61. The underlying channel factory could not be created because no binding information was found in the configuration file for ...
  62. The underlying channel factory could not be created because no Binding was passed to the ChannelFactory. Please supply a ...
  63. The underlying type '{0}' of the enumeration type '{1}' defined in the conceptual model does not match the underlying type ...
  64. The Undo operation encountered a context that is different from what was applied in the corresponding Set operation. The ...
  65. The uninstall of Microsoft .NET Framework 3.0 cannot continue because a later version of Microsoft .NET Framework is dependent ...
  66. The UnitySerializationHolder object is designed to transmit information about other types and is not serializable itself. ...
  67. The UnmanagedType passed to DefineUnmanagedMarshal is not a simple type. None of the following values may be used: UnmanagedType.ByValTStr, ...
  68. The update map does not match the workflow definition. Please make sure that this is the correct map for this definition, ...
  69. The Update method on ObjectDataSource '{0}' must have a parameter that fits the OldValuesParameterFormatString. Check your ...
  70. The update operation cannot be performed, because the adapter's connection is not associated with a valid store connection. ...
  71. The UpdatedWorkflowDefinition provided to the map builder is invalid for implementation map creation because it does not ...
  72. The URI '{0}' is not valid for DELETE operation. The URI must refer to a single resource from an entity set or from a property ...
  73. The URI '{0}' is not valid for MERGE operation. The URI must point to a single resource for MERGE operations. MERGE operation ...
  74. The URI '{0}' is not valid for POST operation. For POST operations, the URI must refer to a service operation or an entity ...
  75. The Uri specified ({0}) is invalid. When using ListenUriMode.Unique, do not specify a port because the channel manager will ...
Deutsch (Deutschland)
German (Germany) Español (España)
Spanish (Spain) Français (France)
French (France) italiano
Italian 日本語
Japanese 한국어
Korean Português
Portuguese Русский
Russian English
English (United States)