Click or drag to resize

DeleteFileManager Class

Represents a resource manager which deletes an existing file when a transaction is successfully committed.
Inheritance Hierarchy

Namespace:  Novacta.Transactions.IO
Assembly:  Novacta.Transactions.IO (in Novacta.Transactions.IO.dll) Version: 1.0.0
Syntax
public sealed class DeleteFileManager : FileManager

The DeleteFileManager type exposes the following members.

Constructors
  NameDescription
Public methodDeleteFileManager
Initializes a new instance of the DeleteFileManager class.
Top
Properties
  NameDescription
Public propertyManagedFileStream
Provides the stream for the managed file.
(Inherited from FileManager.)
Top
Methods
  NameDescription
Public methodCommit
Notifies an enlisted object that a transaction is being committed.
(Inherited from FileManager.)
Public methodDispose
Performs application-defined tasks associated with freeing, releasing, or resetting unmanaged resources.
(Inherited from FileManager.)
Public methodEnlistVolatile
Enlists this instance as a volatile resource manager using the specified enlistment options.
(Inherited from FileManager.)
Public methodEquals
Determines whether the specified object is equal to the current object.
(Inherited from Object.)
Public methodGetHashCode
Serves as the default hash function.
(Inherited from Object.)
Public methodGetType
Gets the Type of the current instance.
(Inherited from Object.)
Public methodInDoubt
Notifies an enlisted object that the status of a transaction is in doubt.
(Inherited from FileManager.)
Public methodPrepare
Notifies an enlisted object that a transaction is being prepared for commitment.
(Inherited from FileManager.)
Public methodRollback
Notifies an enlisted object that a transaction is being rolled back (aborted).
(Inherited from FileManager.)
Public methodToString
Returns a string that represents the current object.
(Inherited from Object.)
Top
Remarks

When a DeleteFileManager instance is notified that a transaction is being prepared for commitment, it checks if a file having the specified path exists. If not, the operation cannot be executed and the transaction is forced to roll back.

See Also