Click or drag to resize

CachedFileStream(String, FileMode, FileAccess, FileShare, Int32, Boolean) Constructor

Initializes a new instance of the FileStream class with the specified path, creation mode, read/write and sharing permission, the access other FileStreams can have to the same file, the buffer size, and additional file options.

Namespace: GSF.IO
Assembly: GSF.Core (in GSF.Core.dll) Version: 2.4.218-beta+101eee949414e414795e55a6e73d88938f0177b8
Syntax
public CachedFileStream(
	string path,
	FileMode mode,
	FileAccess access,
	FileShare share,
	int blockSize,
	bool useAsync
)
View Source

Parameters

path  String
A relative or absolute path for the file that the current FileStream object will encapsulate.
mode  FileMode
A constant that determines how to open or create the file.
access  FileAccess
A constant that determines how the file can be accessed by the FileStream object. This gets the CanRead and CanWrite properties of the FileStream object. CanSeek is true if path specifies a disk file.
share  FileShare
A constant that determines how the file will be shared by processes.
blockSize  Int32
A positive Int32 value greater than 0 indicating the block size. For blockSize values between one and eight, the actual block size is set to eight bytes.
useAsync  Boolean
Specifies whether to use asynchronous I/O or synchronous I/O. However, note that the underlying operating system might not support asynchronous I/O, so when specifying true, the handle might be opened synchronously depending on the platform. When opened asynchronously, the BeginRead(Byte, Int32, Int32, AsyncCallback, Object) and BeginWrite(Byte, Int32, Int32, AsyncCallback, Object) methods perform better on large reads or writes, but they might be much slower for small reads or writes. If the application is designed to take advantage of asynchronous I/O, set the useAsync parameter to true. Using asynchronous I/O correctly can speed up applications by as much as a factor of 10, but using it without redesigning the application for asynchronous I/O can decrease performance by as much as a factor of 10.
Exceptions
ExceptionCondition
ArgumentNullExceptionpath is null.
ArgumentExceptionpath is an empty string (""), contains only white space, or contains one or more invalid characters. -or-path refers to a non-file device, such as "con:", "com1:", "lpt1:", etc. in an NTFS environment.
NotSupportedExceptionpath refers to a non-file device, such as "con:", "com1:", "lpt1:", etc. in a non-NTFS environment.
ArgumentOutOfRangeExceptionblockSize is negative or zero.-or- mode, access, or share contain an invalid value.
FileNotFoundExceptionThe file cannot be found, such as when mode is FileMode.Truncate or FileMode.Open, and the file specified by path does not exist. The file must already exist in these modes.
IOExceptionAn I/O error, such as specifying FileMode.CreateNew when the file specified by path already exists, occurred.-or-The stream has been closed.
SecurityExceptionThe caller does not have the required permission.
DirectoryNotFoundExceptionThe specified path is invalid, such as being on an unmapped drive.
UnauthorizedAccessExceptionThe access requested is not permitted by the operating system for the specified path, such as when access is Write or ReadWrite and the file or directory is set for read-only access.
PathTooLongExceptionThe specified path, file name, or both exceed the system-defined maximum length. For example, on Windows-based platforms, paths must be less than 248 characters, and file names must be less than 260 characters.
See Also