Operation '{0}' in contract '{1}' has a MessageContract parameter (of type '{2}') without a wrapper name and with more than one body element. MessageContract parameters without a wrapper element are supported only if they have zero or one body element.
Operation '{0}' (in contract '{1}' with namespace '{2}') specifies the http body format to be JSON but the serialization ...
Operation '{0}' cannot be performed at this time. Another attempt will be made when the service instance is ready to process ...
Operation '{0}' could not be loaded as it uses an unsupported combination of Use and Style settings: Document with Encoded. ...
Operation '{0}' in contract '{1}' already has a '{2}' behavior, so a new one cannot be added. This usually indicates that ...
Operation '{0}' in contract '{1}' has a MessageContract parameter (of type '{2}') without a wrapper name and with more than ...
Operation '{0}' in contract '{1}' has a parameter or message contract body part with name '{2}' which contains one or more ...
Operation '{0}' in contract '{1}' has a path variable named '{2}' which does not have type 'string'. Variables for UriTemplate ...
Operation '{0}' in contract '{1}' has a query variable named '{2}' of type '{3}', but type '{3}' is not convertible by '{4}'. ...
Operation '{0}' in contract '{1}' has a Stream return value and also has out or ref parameters. When Stream is the return ...