Xceed .NET Libraries Documentation
TarArchive Constructor(FileSystemEvents,Object,AbstractFile)


Xceed.Tar Assembly > Xceed.Tar Namespace > TarArchive Class > TarArchive Constructor : TarArchive Constructor(FileSystemEvents,Object,AbstractFile)
A Xceed.FileSystem.FileSystemEvents object that will be used to raise events. Cannot be a null reference (Nothing in Visual Basic).
Opaque data that will be passed back to the event handler when an event is raised.
An Xceed.FileSystem.AbstractFile object that represents the TAR file to access. For example, to access/create a TAR file in memory use a Xceed.FileSystem.MemoryFile. If the TAR file is on disk, then use a Xceed.FileSystem.DiskFile and so on.
Initializes a new instance of the TarArchive class enabling event notifications while the object is being created.
Syntax
'Declaration
 
Public Function New( _

   ByVal events As FileSystemEvents, _

   ByVal userData As Object, _

   ByVal tarFile As AbstractFile _

)
'Usage
 
Dim events As FileSystemEvents

Dim userData As Object

Dim tarFile As AbstractFile

 

Dim instance As New TarArchive(events, userData, tarFile)
public TarArchive( 

   FileSystemEvents events,

   object userData,

   AbstractFile tarFile

)

Parameters

events
A Xceed.FileSystem.FileSystemEvents object that will be used to raise events. Cannot be a null reference (Nothing in Visual Basic).
userData
Opaque data that will be passed back to the event handler when an event is raised.
tarFile
An Xceed.FileSystem.AbstractFile object that represents the TAR file to access. For example, to access/create a TAR file in memory use a Xceed.FileSystem.MemoryFile. If the TAR file is on disk, then use a Xceed.FileSystem.DiskFile and so on.
Remarks

Once the TarArchive object is created, it does not keep a reference on the event object.

It is important to always use the same instance of the AbstractFile representing the actual TAR file when creating new instances of either TarArchive, TarredFile or TarredFolder otherwise, when updating the TAR file through different instances, information can be lost. Instances obtained from calls to GetFile, GetFiles (and all) are safe, and share the same original AbstractFile.

This implementation of Tar is fully read/write compatible with the USTAR format. It is read compatible with GNU Tar archives whose entries do not use the header extensions of this format.

Requirements

Target Platforms: Windows 7, Windows Vista SP1 or later, Windows XP SP3, Windows Server 2008 (Server Core not supported), Windows Server 2008 R2 (Server Core supported with SP1 or later), Windows Server 2003 SP2

See Also

Reference

TarArchive Class
TarArchive Members
Overload List