The synchronous OperationContract method '{0}' in type '{1}' was matched with the asynchronous OperationContract methods '{2}' and '{3}' because they have the same operation name '{4}'. When a synchronous OperationContract method is matched to a pair of asynchronous OperationContract methods, the two OperationContracts must define the same return type. In this case, the return types are different. To fix it, ensure that method '{0}' and method '{3}' have the same return type. Alternatively, changing the name of one of the methods will prevent matching.
The supporting signature is not signed with a derived key. The binding's supporting token parameter '{0}' requires key derivation. ...
The supporting token in the renew message has a different generation '{0}' than the current session token's generation '{1}'. ...
The surrogate pair (0x{0}, 0x{1}) is invalid. A high surrogate character (0xD800 - 0xDBFF) must always be paired with a low ...
The symmetric security protocol can either be configured with a symmetric token provider and a symmetric token authenticator ...
The synchronous OperationContract method '{0}' in type '{1}' was matched with the asynchronous OperationContract methods ...
The synchronous OperationContract method '{0}' in type '{1}' was matched with the asynchronous OperationContract methods ...
The synchronous OperationContract method '{0}' in type '{1}' was matched with the asynchronous OperationContract methods ...
The synchronous OperationContract method '{0}' in type '{1}' was matched with the asynchronous OperationContract methods ...
The synchronous OperationContract method '{0}' in type '{1}' was matched with the task-based asynchronous OperationContract ...