FileOpenTransacted Method (KernelTransaction, String, FileMode, FileAccess, FileShare, Int32, Boolean)

public static FileStream OpenTransacted(
	KernelTransaction transaction,
	string path,
	FileMode mode,
	FileAccess access,
	FileShare share,
	int bufferSize,
	bool useAsync
)

Public Shared Function OpenTransacted ( 
	transaction As KernelTransaction,
	path As String,
	mode As FileMode,
	access As FileAccess,
	share As FileShare,
	bufferSize As Integer,
	useAsync As Boolean
) As FileStream

public:
static FileStream^ OpenTransacted(
	KernelTransaction^ transaction, 
	String^ path, 
	FileMode mode, 
	FileAccess access, 
	FileShare share, 
	int bufferSize, 
	bool useAsync
)

static member OpenTransacted : 
        transaction : KernelTransaction * 
        path : string * 
        mode : FileMode * 
        access : FileAccess * 
        share : FileShare * 
        bufferSize : int * 
        useAsync : bool -> FileStream 

Parameters

transaction

Type: Alphaleonis.Win32.FilesystemKernelTransaction
The transaction.

path

Type: SystemString
The file to open.

mode

Type: System.IOFileMode
A constant that determines how to open or create the file.

access

Type: System.IOFileAccess
A FileAccess value that specifies the operations that can be performed on the file.

share

Type: System.IOFileShare
A constant that determines how the file will be shared by processes.

bufferSize

Type: SystemInt32
A positive Int32 value greater than 0 indicating the buffer size. The default buffer size is 4096.

useAsync

Type: SystemBoolean
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 and BeginWrite 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.

Return Value

Reference