Operation '{0}' in contract '{1}' uses GET, but also has a parameter of MessageContract type '{2}'. GET operations cannot have a body. To use a MessageContract parameter type, switch from WebGetAttribute to WebInvokeAttribute.
Operation '{0}' in contract '{1}' is specified as two-way, but is missing a SendReply. Please add a SendReply activity for ...
Operation '{0}' in contract '{1}' specifies an 'out' or 'ref' parameter. Operations with 'out' or 'ref' parameters are not ...
Operation '{0}' in contract '{1}' specifies Method '{2}' on the WebGetAttribute/WebInvokeAttribute, but the only allowed ...
Operation '{0}' in contract '{1}' uses a MessageContract that has SOAP headers. SOAP headers are not supported by the None ...
Operation '{0}' in contract '{1}' uses GET, but also has a parameter of MessageContract type '{2}'. GET operations cannot ...
Operation '{0}' in contract '{1}' uses GET, but also has body parameter '{2}'. GET operations cannot have a body. Either ...
Operation '{0}' in contract '{1}' uses UriTemplate parameters, but also uses a Message parameter. Message and UriTemplate ...
Operation '{0}' in contract '{1}' uses UriTemplate parameters, but also uses a MessageContract parameter. MessageContract ...
Operation '{0}' of contract '{1}' specifies at least one response body parameter that is not a return value of the operation. ...