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 define the same number and types of parameters. In this case, some of the arguments are different. To fix it, ensure that the OperationContracts define the same number and types of arguments, in the same order. Alternatively, changing the name of one of the methods will prevent matching.
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. ...
The TextInfo.ANSICodePage and TextInfo.OEMCodePage properties must be the same when either one is a multi-byte code page. ...