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 The {0} operation was called on an incoming request with WebSocket version '{1}', expected '{2}'. A WebSocket operation was called on a request or response that is not a WebSocket. The {0} operation was called on an incoming WebSocket request without required '{1}' header. The WebSocket protocol '{0}' is invalid because it contains the invalid character '{1}'. An error occurred when sending the WebSocket HTTP upgrade response during the {0} operation. The HRESULT returned is '{1}' The received message type is invalid after calling {0}. {0} should only be used if no more data is expected from the remote endpoint. Use '{1}' instead to keep being able to receive data but close the output channel. Unsupported WebSocket version. The '{0}' instance cannot be used for communication because it has been transitioned into the '{1}' state. The WebSocket client request requested '{0}' protocol(s), but server is only accepting '{1}' protocol(s). The message type '{0}' is not allowed for the '{1}' operation. Valid message types are: '{2}, {3}'. To close the WebSocket, use the '{4}' operation instead. The WebSocket is in an invalid state ('{0}') for this operation. Valid states are: '{1}' The WebSocket request or response contained unsupported header(s). The close status description '{0}' is too long. The UTF8-representation of the status description must not be longer than {1} bytes. The close status description '{0}' is invalid. When using close status code '{1}' the description must be null. The buffer type '{0}' is invalid. Valid buffer types are: '{1}', '{2}', '{3}', '{4}', '{5}'. The WebSocket client did not request any protocols, but server attempted to accept '{0}' protocol(s). The WebSocket is in an invalid state for this operation. The '{0}' method has already been called before on this instance. Use '{1}' instead to keep being able to receive data but close the output channel. An exception caused the WebSocket to enter the Aborted state. Please see the InnerException, if present, for more details. This operation is not supported for a relative URI. The byte array must have a length of at least '{0}' bytes. The WebSocket is not connected. The WebSocket instance cannot be used for communication because it has been transitioned into an invalid state. Empty string is not a valid subprotocol value. Please use \"null\" to specify no value. The received message type '{2}' is invalid after calling {0}. {0} should only be used if no more data is expected from the remote endpoint. Use '{1}' instead to keep being able to receive data but close the output channel. The WebSocket request or response operation was called with unsupported protocol(s). The value of the '{0}' parameter ({1}) must be less than or equal to {2}. The WebSocket has already been started. The remote party closed the WebSocket connection without completing the close handshake. The {0} operation was called on an incoming request that did not specify a '{1}: {2}' header or the {2} header not contain '{3}'. {2} specified by the client was '{4}'. The WebSocket schemes must be registered with the HttpWebRequest class. The argument must be a value greater than {0}. The WebSocket client sent a blank '{0}' header; this is not allowed by the WebSocket protocol specification. The client should omit the header if the client is not negotiating any sub-protocols. The WebSocket protocol is not supported on this platform. The '{0}' header value '{1}' is invalid. Duplicate protocols are not allowed: '{0}'. Only Uris starting with 'ws://' or 'wss://' are supported. There is already one outstanding '{0}' call for this WebSocket instance. ReceiveAsync and SendAsync can be called simultaneously, but at most one outstanding operation for each of them is allowed at the same time. The close status code '{0}' is reserved for system use only and cannot be specified when calling this method. An internal WebSocket error occurred. Please see the innerException, if present, for more details. The server returned status code '{0}' when status code '101' was expected. Exception in {0}::{1} - {2}. Unable to connect to the remote server