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 task-based asynchronous OperationContract method is matched to a pair of asynchronous OperationContract methods, the two OperationContracts must have the same value for the '{5}' property. In this case, the values are different. To fix it, change the '{5} property of one of the OperationContracts to match the other. Alternatively, changing the name of one of the methods will prevent matching.
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 ...
The text that appears in the ALT attribute of the invisible image link that allows screen readers to skip repetitive content. ...