ISerializable type with data contract name '{0}' in namespace '{1}' cannot be imported. The data contract name cannot be customized for ISerializable type and the generated name '{2}' does not match the expected name '{0}'. Check if the required name has been mapped to a different type or if it is an invalid CLR name which cannot be generated or if the type requires an outer type which is not present.
is protected with a LinkDemand for {1}. In the level 2 security rule set, it should be protected by being security critical ...
is the path to a text file that contains a list of assembly manifest file paths. Individual paths in the text file must be ...
is the path to a text file that contains a list of assembly names. Individual names in the text file must be separated by ...
ISerializable name/types returned by GetObjectData does not match name/types declared with SerializationTypeInfoAttribute ...
ISerializable type with data contract name '{0}' in namespace '{1}' cannot be imported. The data contract name cannot be ...
ISerializable type with data contract name '{0}' in namespace '{1}' cannot be imported. The data contract namespace cannot ...
ISessionIDManager.InitializeRequest has not been called for this request yet. In each request, please first call ISessionIDManager.InitializeRequest ...
IsNot' operand of type '|1' can be compared only to 'Nothing' because '|1' is a type parameter with no class constraint. ...
IsNullable may not be set to 'false' for a Nullable type. Consider using '{0}' type or removing the IsNullable property from ...