The synchronous OperationContract method '{0}' in type '{1}' was matched with the task-based asynchronous OperationContract method '{2}' because they have the same operation name '{3}'. When a synchronous OperationContract method is matched to a task-based asynchronous OperationContract method, 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 '{2}' have the same return type. Alternatively, changing the name of one of the methods will prevent matching.
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 ...
The synchronous OperationContract method '{0}' in type '{1}' was matched with the task-based asynchronous OperationContract ...
The synchronous OperationContract method '{0}' in type '{1}' was matched with the task-based asynchronous OperationContract ...
The synchronous OperationContract method '{0}' in type '{1}' was matched with the task-based asynchronous OperationContract ...
The System Health Check has detected a problem that may cause Setup to fail. Description %1 Workaround / Remedy %2 More information ...