The task-based asynchronous 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 targetNamespace '{0}' of included/redefined schema should be the same as the targetNamespace '{1}' of the including schema. ...
The Task provider delegate specified for this IAsyncInfo instance returned a Task object that was not started. Task instances ...
The task provider delegate used to create this asynchronous operation returned null, but a valid Task object was expected. ...
The Task returned from this Async Function will be dropped, and any exceptions in it ignored. Consider changing it to an ...
The task-based asynchronous OperationContract method '{0}' in type '{1}' was matched with the asynchronous OperationContract ...
The task-based asynchronous OperationContract method '{0}' in type '{1}' was matched with the asynchronous OperationContract ...
The task-based asynchronous OperationContract method '{0}' in type '{1}' was matched with the asynchronous OperationContract ...
The task-based asynchronous OperationContract method '{0}' in type '{1}' was matched with the asynchronous OperationContract ...
The template file to be used for creating this event notification is not found. The {0} events that were part of this message ...