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 Probable I/O race condition detected while copying memory. The I/O package is not thread safe by default. In multithreaded applications, a stream must be accessed in a thread-safe way, such as a thread-safe wrapper returned by TextReader's or TextWriter's Synchronized methods. This also applies to classes like StreamWriter and StreamReader. Empty path name is not legal. FileStream was asked to open a device that was not a file. For support for devices like 'com1:' or 'lpt1:', call CreateFile, then use the FileStream constructors that take an OS handle as an IntPtr. [Unknown] Unable seek backward to overwrite data that previously existed in a file opened in Append mode. BindHandle for ThreadPool failed on this handle. The specified directory '{0}' cannot be created. Stream does not support writing. File name cannot be null. The target file '{0}' is a directory, not a file. Unable to read beyond the end of the stream. The process cannot access the file because it is being used by another process. Empty file name is not legal. Path must not be a drive. Unable to truncate data that previously existed in a file opened in Append mode. Could not find a part of the path '{0}'. Second path fragment must not be a drive or UNC name. Stream does not support seeking. Invalid handle. Source and destination path must have identical roots. Move will not work across volumes. Unable to find the specified file. Specified file length was too large for the file system. The file is too long. This operation is currently limited to supporting files less than 2 gigabytes in size. Synchronous operations should not be performed on the UI thread. Consider wrapping this method in Task.Run. The specified file name or path is too long, or a component of the specified path is too long. Append access can be requested only in write-only mode. Source and destination path must be different. Enum value was out of legal range. Offset and length were out of bounds for the array or count is greater than the number of elements from index to the end of the source collection. Access to the path is denied. The process cannot access the file '{0}' because it is being used by another process. Access to the path '{0}' is denied. Search pattern cannot contain '..' to move up directories and can be contained only internally in file/directory names, as in 'a..b'. Could not find a part of the path. Path cannot be null. Handle does not support asynchronous operations. The parameters to the FileStream constructor may need to be changed to indicate that the handle was opened synchronously (that is, it was not opened for overlapped I/O). Non-negative number required. Cannot access a closed Stream. Path cannot be the empty string or all whitespace. The file '{0}' already exists. Cannot create '{0}' because a file or directory with the same name already exists. Invalid File or Directory attributes value. Stream does not support reading. The directory specified, '{0}', is not a subdirectory of '{1}'. The OS handle's position is not what FileStream expected. Do not use a handle simultaneously in one FileStream and in Win32 code or another FileStream. This may cause data loss. Cannot access a closed file. The stream's length cannot be changed. Combining FileMode: {0} with FileAccess: {1} is invalid. Illegal characters in path. Handle does not support synchronous operations. The parameters to the FileStream constructor may need to be changed to indicate that the handle was opened asynchronously (that is, it was opened explicitly for overlapped I/O). Buffer cannot be null. Positive number required. File encryption is not supported on this platform. Could not find file '{0}'. Invalid seek origin. IO operation will not work. Most likely the file will become too long or the handle was not opened to support synchronous IO operations.