The {0} definitions in the signature and implementation are not compatible because the implementation defines the {1} '{2}' but the signature does not (or does, but not in the same order)
The {0} definitions in the signature and implementation are not compatible because the field {1} was present in the implementation ...
The {0} definitions in the signature and implementation are not compatible because the field {1} was present in the implementation ...
The {0} definitions in the signature and implementation are not compatible because the field {1} was required by the signature ...
The {0} definitions in the signature and implementation are not compatible because the implementation defines a struct but ...
The {0} definitions in the signature and implementation are not compatible because the implementation defines the {1} '{2}' ...
The {0} definitions in the signature and implementation are not compatible because the implementation is an abstract class ...
The {0} definitions in the signature and implementation are not compatible because the implementation says this type may ...
The {0} definitions in the signature and implementation are not compatible because the implementation says this type may ...
The {0} definitions in the signature and implementation are not compatible because the implementation type is not sealed ...