QuickIO.NET online help is available on
All method signatures are based on the existing .NET Framework namespace
For this reason modern patterns and C# development policies cannot be applied perfectly.
QuickIO.NET distinguishes and recognizes four types of paths.
- UNC Share Path
- UNC Local Path
- Regular Share Path
- Regular Local Path
The reason for this is that long path names (up to 32767 characters) are supported only in UNC format by the Win32 API .
All internal calls to the Win32 API are done in the UNC format. Default message output (like in exceptions) are in the regular format.
QuickIODirectoryInfo types provide a property
PathInfo of the
QuickIOPathInfo which contains both path types. Or you can use the properties
Internal Path Handling
Any internal function of QuickIO.NET is using an instance of
QuickIOPathInfo, which represents the path to a file or a folder.
However all methods accept the path as a string and convert it internally.
// Method receives path and overloads QuickIOPathInfo
public static void Create( string path, bool recursive = false )
Create( new QuickIOPathInfo( path ), recursive );
// Receive QuickIOPathInfo
public static void Create( QuickIOPathInfo pathInfo, bool recursive = false )
InternalQuickIO.CreateDirectory( pathInfo, recursive );
As already mentioned, the class QuickIOPathInfo provides the output of the path in regular and UNC format.
The QuickIOPathInfo knows whether the path represents a file or a folder. For this purpose the
SystemEntryType property is provided.
PathLocation property specifies whether it is a local path or a path to a network share.
Read the full documentation:
QuickIOPathInfo Online Help
QuickIOPathInfo throws an
PathNotFoundException if the specified path does not exist! You have to use the static create methods to create new files or folders!
Please check http://quickIO.net/Examples