text/microsoft-resx 2.0 System.Resources.ResXResourceReader, System.Windows.Forms, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089 System.Resources.ResXResourceWriter, System.Windows.Forms, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089 Argument's {0}.{1} property is required but is empty or null. HttpContext.Current is null. There must be an ASP.NET request in process for this operation to succeed. DataContractSerializer could not be initialized on message type {0}. Is it missing a [DataContract] attribute? DataContractSerializer could not be initialized on message type {0} because the DataContractAttribute.Namespace property is not set. An instance of type {0} was expected, but received unexpected derived type {1}. The directed message's Recipient property must not be null. Error occurred while sending a direct message or getting the response. This exception was not constructed with a root request message that caused it. Expected message {0} but received no recognizable message. The message expired at {0} and it is now {1}. At least one of GET or POST flags must be present. This method requires a current HttpContext. Alternatively, use an overload of this method that allows you to pass in information without an HttpContext. Messages that indicate indirect transport must implement the {0} interface. The message required protections {0} but the channel could only apply {1}. Some part(s) of the message have invalid values: {0} The incoming message had an invalid or missing nonce. An item with the same key has already been added. A message response is already queued for sending in the response stream. This message has already been processed. This could indicate a replay attack in progress. This channel does not support replay protection. The following required parameters were missing from the {0} message: {1} The binding element offering the {0} protection requires other protection that is not provided. The list is empty. The list contains a null element. Message signature was incorrect. This channel does not support signing messages. To support signing messages, a derived Channel type must override the Sign and IsSignatureValid methods. The stream's CanRead property returned false. The stream's CanWrite property returned false. Expected at most 1 binding element offering the {0} protection, but found {1}. Expected message {0} but received {1} instead. The type {0} or a derived type was expected, but {1} was given. {0} property has unrecognized value {1}.