text/microsoft-resx 2.0 System.Resources.ResXResourceReader, System.Windows.Forms, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089 System.Resources.ResXResourceWriter, System.Windows.Forms, Version=4.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. The given set of options is not supported by this web request handler. Error while deserializing message {0}. 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 {0} message 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. Insecure web request for '{0}' aborted due to security requirements demanding HTTPS. The {0} message required protections {{{1}}} but the channel could only apply {{{2}}}. The customized binding element ordering is invalid. 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. The {0} message does not support extensions. The value for {0}.{1} on member {1} was expected to derive from {2} but was {3}. Error while reading message '{0}' parameter '{1}' with value '{2}'. Message parameter '{0}' with value '{1}' failed to base64 decode. Error while preparing message '{0}' parameter '{1}' for sending. 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 non-empty parameters were empty in the {0} message: {1} 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 to apply the {0} protection, but more than one applied. The maximum allowable number of redirects were exceeded while requesting '{0}'. The array must not be empty. The empty string is not allowed. Message parameter '{0}' had unexpected value '{1}'. Expected message {0} parameter '{1}' to have value '{2}' but had '{3}' instead. Expected message {0} but received {1} instead. Unexpected message type received. A null key was included and is not allowed. A null or empty key was included and is not allowed. A null value was included for key '{0}' and is not allowed. The type {0} or a derived type was expected, but {1} was given. {0} property has unrecognized value {1}. The URL '{0}' is rated unsafe and cannot be requested this way. Redirects on POST requests that are to untrusted servers is not supported. Web request to '{0}' failed. This exception must be instantiated with a recipient that will receive the error message, or a direct request message instance that this exception will respond to. '{0}' messages cannot be received with HTTP verb '{1}'. Expected direct response to use HTTP status code {0} but was {1} instead. The HTTP verb '{0}' is unrecognized and unsupported. A non-empty string was expected. The stream must have a known length. Unable to send all message data because some of it requires multi-part POST, but IMessageWithBinaryData.SendAsMultipart was false. An HttpContext.Current.Session object is required. This message factory does not support message type(s): {0} The following message parts had constant value requirements that were unsatisfied: {0} Unable to instantiate the message part encoder/decoder type {0}. This message has a timestamp of {0}, which is beyond the allowable clock skew for in the future. This blob is not a recognized encryption format. Failed to add extra parameter '{0}' with value '{1}'. The message part {0} was expected in the {1} message but was not found. Message too large for a HTTP GET, and HTTP POST is not allowed for this message type. Missing decryption key for bucket "{0}" handle "{1}" Unexpected buffer length. Decoding failed due to data corruption.