The Type '{0}' is not unique. This may be caused by the types only differing in case which is not compatible with the current language option.
The type '{0}' in the service contract mapping has different TargetNamespace('{1}') and Name('{2}') than the TargetNamespace('{3}') ...
The type '{0}' is ambiguous: it could come from assembly '{1}' or from assembly '{2}'. Please specify the assembly explicitly ...
The type '{0}' is an abstract type. For PUT, POST and DELETE operations, the type specified must be a concrete type with ...
The type '{0}' is not a valid device adapter, because it does not implement the interface '{1}'. Use another type, or modify ...
The Type '{0}' is not unique. This may be caused by the types only differing in case which is not compatible with the current ...
The type '{0}' of the member '{1}' in the conceptual side type '{2}' does not match with the type '{3}' of the member '{4}' ...
The type '{0}' that is being loaded conflicts with the type '{1}' that is already loaded because they have the same namespace ...
The type '{0}'('{1}') of the member '{2}' in the conceptual type '{3}' doesn't match with the type '{4}'('{5}') of the member ...
The type '{0}', provided as the Factory attribute value in the 'system.serviceModel/serviceHostingEnvironment/serviceActivations' ...