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, any additional attributes must be declared on the task-based asynchronous OperationContract method. In this case, the asynchronous OperationContract method '{2}' has one or more attributes of type '{5}'. To fix it, remove the '{5}' attribute or attributes from method '{2}'. Alternatively, changing the name of one of the methods will prevent matching.
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. ...
The ThreadLocal object is not tracking values. To use the Values property, use a ThreadLocal constructor that accepts the ...