The methods {0} and {1} use the same request element <{2} xmlns='{3}'> and the methods {0} and {4} use the same SOAPAction '{5}'. Each method on the XML Web service must have a unique SOAPAction or request element. If you are using the Rpc style, you can change the message name with the RequestElementName and RequestElementNamespace parameters to SoapRpcMethodAttribute. For document style using wrapped parameter style, use the RequestElementName and RequestElementNamespace parameters to SoapDocumentMethodAttribute. For the bare parameter style, you must change the element that represents the parameter. Alternatively, you can specify a unique SoapAction for each method using the Action parameter to SoapRpcMethodAttribute or SoapDocumentMethodAttribute.
The Method with name '{1}' in Type '{0}' could not be invoked because the application does not have permission to invoke ...
The method {0} does not have a request element. You can use a RoutingStyle of SoapAction on the XML Web service, use the ...
The methods 'Single' and 'SingleOrDefault' can only be used as a final query operation. Consider using the method 'FirstOrDefault' ...
The methods {0} and {1} use the same request element . When the RoutingStyle of the XML Web service is RequestElement, request ...
The methods {0} and {1} use the same request element and the methods {0} and {4} use the same SOAPAction '{5}'. Each method ...
The methods {0} and {1} use the same SOAPAction '{2}'. When the RoutingStyle of the XML Web service is SoapAction, SOAPAction ...
The mode '{0}' requires at least one 'incsdl' or 'inssdl' argument. Verify that at least one .csdl or .ssdl file is in the ...
The MSBuild cache file "{0}" is inaccessible. Ensure you have access to the directory and that this file is not deleted during ...
The MSBuild task is skipping the remaining targets and projects because the StopOnFirstFailure parameter was set to true. ...