ImageGear for .NET
Using a Non-Transactional Resource
ImageGear for .NET User Guide > Using ImageGear for .NET > Using ImageGear.Web.DataProviders Namespace > Implementing Annotations in an Image Data Provider > Enabling Annotation within a Custom Image Data Provider > Background Information on Transactions > Using a Non-Transactional Resource

If your custom provider is based on a non-transactional system, then your code has to detect the ambient TransactionScope and handle the read and write requests from within the TransactionScope.

Microsoft introduced Transactional NTFS (abbreviated TxF) in Vista (For details refer to: http://msdn.microsoft.com/en-us/library/bb968806(VS.85).aspx). The Transactional NTFS brings the concept of atomic transactions to the NTFS file system, and can be used to support the handling of read and write requests from within the TransactionScope.

Prior Operating Systems, like Windows Server 2003, do not have support for TxF and it is not included in the .NET Framework (through version 4.0). This means that when using older operating systems, custom image data providers that store annotations in files must either manage the file resources without the assistance of TxF or access the TxF unmanaged API via InteropServices.

 

 

©2014. Accusoft Corporation. All Rights Reserved.

Send Feedback