Method {0} on type {1} is an implementation of the service contract interface {2}. Service Description altering attributes cannot be specified on service implementation. Please place custom attribute on the interface declaration: interface: {2}, method: {3}, attribute: {4}.
Method '{1}' has {0}, but enclosing type '{2}' does not have ServiceContractAttribute. {0} can only be used on methods in ...
Method '|1' cannot implement partial method '|2' because '|3' already implements it. Only one method can implement a partial ...
Method '|1' has a link demand, but overrides or implements the following methods which do not have a link demand. A security ...
Method {0} is not supported on this proxy, this can happen if the method is not marked with OperationContractAttribute or ...
Method {0} on type {1} is an implementation of the service contract interface {2}. Service Description altering attributes ...
Method {0}.{1} can not be reflected. Parameter '{2}' has invalid accessor: If you are using the Rpc\Literal method, you can ...
Method {0}.{1} can not be reflected. Parameter '{2}' may not be used with Rpc\Literal SOAP messages because it is declared ...
Method, operator, or accessor '%1!ls!' is marked external and has no attributes on it. Consider adding a DllImport attribute ...
Methods decorated with the SuppressUnmanagedCodeSecurity attribute have an implicit LinkDemand placed upon all of their callers. ...