The {0} definitions in the signature and implementation are not compatible because the implementation type is sealed but the signature implies it is not. Consider adding the [] attribute to the signature.
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 ...
The {0} definitions in the signature and implementation are not compatible because the implementation type is sealed but ...
The {0} definitions in the signature and implementation are not compatible because the order of the fields is different in ...
The {0} definitions in the signature and implementation are not compatible because the respective type parameter counts differ ...
The {0} definitions in the signature and implementation are not compatible because the signature declares a {1} while the ...
The {0} definitions in the signature and implementation are not compatible because the signature defines the {1} '{2}' but ...