mirror of https://github.com/raandree/NTFSSecurity
You can not select more than 25 topics
Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
210 lines
13 KiB
210 lines
13 KiB
/* Copyright (C) 2008-2016 Peter Palotas, Jeffrey Jangli, Alexandr Normuradov
|
|
*
|
|
* Permission is hereby granted, free of charge, to any person obtaining a copy
|
|
* of this software and associated documentation files (the "Software"), to deal
|
|
* in the Software without restriction, including without limitation the rights
|
|
* to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
|
|
* copies of the Software, and to permit persons to whom the Software is
|
|
* furnished to do so, subject to the following conditions:
|
|
*
|
|
* The above copyright notice and this permission notice shall be included in
|
|
* all copies or substantial portions of the Software.
|
|
*
|
|
* THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
|
|
* IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
|
|
* FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
|
|
* AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
|
|
* LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
|
|
* OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
|
|
* THE SOFTWARE.
|
|
*/
|
|
|
|
using System;
|
|
using System.IO;
|
|
using System.Linq;
|
|
using System.Security;
|
|
using SearchOption = System.IO.SearchOption;
|
|
|
|
namespace Alphaleonis.Win32.Filesystem
|
|
{
|
|
partial class Directory
|
|
{
|
|
// Since Directory.GetFileSystemEntries() is less efficient than Directory.EnumerateFileSystemEntries(),
|
|
// only .NET and AlphaFS Transactional methods are implemented. No additional overloaded methods.
|
|
|
|
#region .NET
|
|
|
|
/// <summary>Returns the names of all files and subdirectories in the specified directory.</summary>
|
|
/// <returns>An string[] array of the names of files and subdirectories in the specified directory.</returns>
|
|
/// <remarks>
|
|
/// <para>The EnumerateFileSystemEntries and GetFileSystemEntries methods differ as follows: When you use EnumerateFileSystemEntries,
|
|
/// you can start enumerating the collection of entries before the whole collection is returned; when you use GetFileSystemEntries,
|
|
/// you must wait for the whole array of entries to be returned before you can access the array.
|
|
/// Therefore, when you are working with many files and directories, EnumerateFiles can be more efficient.
|
|
/// </para>
|
|
/// </remarks>
|
|
/// <exception cref="ArgumentException"/>
|
|
/// <exception cref="ArgumentNullException"/>
|
|
/// <exception cref="DirectoryNotFoundException"/>
|
|
/// <exception cref="IOException"/>
|
|
/// <exception cref="NotSupportedException"/>
|
|
/// <exception cref="UnauthorizedAccessException"/>
|
|
/// <param name="path">The directory for which file and subdirectory names are returned.</param>
|
|
[SecurityCritical]
|
|
public static string[] GetFileSystemEntries(string path)
|
|
{
|
|
return EnumerateFileSystemEntryInfosCore<string>(null, path, Path.WildcardStarMatchAll, DirectoryEnumerationOptions.FilesAndFolders, PathFormat.RelativePath).ToArray();
|
|
}
|
|
|
|
/// <summary>Returns an array of file system entries that match the specified search criteria.</summary>
|
|
/// <returns>An string[] array of file system entries that match the specified search criteria.</returns>
|
|
/// <remarks>
|
|
/// <para>The EnumerateFileSystemEntries and GetFileSystemEntries methods differ as follows: When you use EnumerateFileSystemEntries,
|
|
/// you can start enumerating the collection of entries before the whole collection is returned; when you use GetFileSystemEntries,
|
|
/// you must wait for the whole array of entries to be returned before you can access the array.
|
|
/// Therefore, when you are working with many files and directories, EnumerateFiles can be more efficient.
|
|
/// </para>
|
|
/// </remarks>
|
|
/// <exception cref="ArgumentException"/>
|
|
/// <exception cref="ArgumentNullException"/>
|
|
/// <exception cref="DirectoryNotFoundException"/>
|
|
/// <exception cref="IOException"/>
|
|
/// <exception cref="NotSupportedException"/>
|
|
/// <exception cref="UnauthorizedAccessException"/>
|
|
/// <param name="path">The path to be searched.</param>
|
|
/// <param name="searchPattern">
|
|
/// The search string to match against the names of directories in <paramref name="path"/>.
|
|
/// This parameter can contain a combination of valid literal path and wildcard
|
|
/// (<see cref="Path.WildcardStarMatchAll"/> and <see cref="Path.WildcardQuestion"/>) characters, but does not support regular expressions.
|
|
/// </param>
|
|
[SecurityCritical]
|
|
public static string[] GetFileSystemEntries(string path, string searchPattern)
|
|
{
|
|
return EnumerateFileSystemEntryInfosCore<string>(null, path, searchPattern, DirectoryEnumerationOptions.FilesAndFolders, PathFormat.RelativePath).ToArray();
|
|
}
|
|
|
|
/// <summary>Gets an array of all the file names and directory names that match a <paramref name="searchPattern"/> in a specified path, and optionally searches subdirectories.</summary>
|
|
/// <returns>An string[] array of file system entries that match the specified search criteria.</returns>
|
|
/// <remarks>
|
|
/// <para>The EnumerateFileSystemEntries and GetFileSystemEntries methods differ as follows: When you use EnumerateFileSystemEntries,
|
|
/// you can start enumerating the collection of entries before the whole collection is returned; when you use GetFileSystemEntries,
|
|
/// you must wait for the whole array of entries to be returned before you can access the array.
|
|
/// Therefore, when you are working with many files and directories, EnumerateFiles can be more efficient.
|
|
/// </para>
|
|
/// </remarks>
|
|
/// <exception cref="ArgumentException"/>
|
|
/// <exception cref="ArgumentNullException"/>
|
|
/// <exception cref="DirectoryNotFoundException"/>
|
|
/// <exception cref="IOException"/>
|
|
/// <exception cref="NotSupportedException"/>
|
|
/// <exception cref="UnauthorizedAccessException"/>
|
|
/// <param name="path">The directory to search.</param>
|
|
/// <param name="searchPattern">
|
|
/// The search string to match against the names of directories in <paramref name="path"/>.
|
|
/// This parameter can contain a combination of valid literal path and wildcard
|
|
/// (<see cref="Path.WildcardStarMatchAll"/> and <see cref="Path.WildcardQuestion"/>) characters, but does not support regular expressions.
|
|
/// </param>
|
|
/// <param name="searchOption">
|
|
/// One of the <see cref="SearchOption"/> enumeration values that specifies whether the <paramref name="searchOption"/>
|
|
/// should include only the current directory or should include all subdirectories.
|
|
/// </param>
|
|
[SecurityCritical]
|
|
public static string[] GetFileSystemEntries(string path, string searchPattern, SearchOption searchOption)
|
|
{
|
|
var options = DirectoryEnumerationOptions.FilesAndFolders | ((searchOption == SearchOption.AllDirectories) ? DirectoryEnumerationOptions.Recursive : 0);
|
|
|
|
return EnumerateFileSystemEntryInfosCore<string>(null, path, searchPattern, options, PathFormat.RelativePath).ToArray();
|
|
}
|
|
|
|
#endregion // .NET
|
|
|
|
#region Transactional
|
|
|
|
/// <summary>Returns the names of all files and subdirectories in the specified directory.</summary>
|
|
/// <returns>An string[] array of the names of files and subdirectories in the specified directory.</returns>
|
|
/// <remarks>
|
|
/// <para>The EnumerateFileSystemEntries and GetFileSystemEntries methods differ as follows: When you use EnumerateFileSystemEntries,
|
|
/// you can start enumerating the collection of entries before the whole collection is returned; when you use GetFileSystemEntries,
|
|
/// you must wait for the whole array of entries to be returned before you can access the array.
|
|
/// Therefore, when you are working with many files and directories, EnumerateFiles can be more efficient.
|
|
/// </para>
|
|
/// </remarks>
|
|
/// <exception cref="ArgumentException"/>
|
|
/// <exception cref="ArgumentNullException"/>
|
|
/// <exception cref="DirectoryNotFoundException"/>
|
|
/// <exception cref="IOException"/>
|
|
/// <exception cref="NotSupportedException"/>
|
|
/// <exception cref="UnauthorizedAccessException"/>
|
|
/// <param name="transaction">The transaction.</param>
|
|
/// <param name="path">The directory for which file and subdirectory names are returned.</param>
|
|
[SecurityCritical]
|
|
public static string[] GetFileSystemEntriesTransacted(KernelTransaction transaction, string path)
|
|
{
|
|
return EnumerateFileSystemEntryInfosCore<string>(transaction, path, Path.WildcardStarMatchAll, DirectoryEnumerationOptions.FilesAndFolders, PathFormat.RelativePath).ToArray();
|
|
}
|
|
|
|
/// <summary>Returns an array of file system entries that match the specified search criteria.</summary>
|
|
/// <returns>An string[] array of file system entries that match the specified search criteria.</returns>
|
|
/// <remarks>
|
|
/// <para>The EnumerateFileSystemEntries and GetFileSystemEntries methods differ as follows: When you use EnumerateFileSystemEntries,
|
|
/// you can start enumerating the collection of entries before the whole collection is returned; when you use GetFileSystemEntries,
|
|
/// you must wait for the whole array of entries to be returned before you can access the array.
|
|
/// Therefore, when you are working with many files and directories, EnumerateFiles can be more efficient.
|
|
/// </para>
|
|
/// </remarks>
|
|
/// <exception cref="ArgumentException"/>
|
|
/// <exception cref="ArgumentNullException"/>
|
|
/// <exception cref="DirectoryNotFoundException"/>
|
|
/// <exception cref="IOException"/>
|
|
/// <exception cref="NotSupportedException"/>
|
|
/// <exception cref="UnauthorizedAccessException"/>
|
|
/// <param name="transaction">The transaction.</param>
|
|
/// <param name="path">The path to be searched.</param>
|
|
/// <param name="searchPattern">
|
|
/// The search string to match against the names of directories in <paramref name="path"/>.
|
|
/// This parameter can contain a combination of valid literal path and wildcard
|
|
/// (<see cref="Path.WildcardStarMatchAll"/> and <see cref="Path.WildcardQuestion"/>) characters, but does not support regular expressions.
|
|
/// </param>
|
|
[SecurityCritical]
|
|
public static string[] GetFileSystemEntriesTransacted(KernelTransaction transaction, string path, string searchPattern)
|
|
{
|
|
return EnumerateFileSystemEntryInfosCore<string>(transaction, path, searchPattern, DirectoryEnumerationOptions.FilesAndFolders, PathFormat.RelativePath).ToArray();
|
|
}
|
|
|
|
/// <summary>Gets an array of all the file names and directory names that match a <paramref name="searchPattern"/> in a specified path, and optionally searches subdirectories.</summary>
|
|
/// <returns>An string[] array of file system entries that match the specified search criteria.</returns>
|
|
/// <remarks>
|
|
/// <para>The EnumerateFileSystemEntries and GetFileSystemEntries methods differ as follows: When you use EnumerateFileSystemEntries,
|
|
/// you can start enumerating the collection of entries before the whole collection is returned; when you use GetFileSystemEntries,
|
|
/// you must wait for the whole array of entries to be returned before you can access the array.
|
|
/// Therefore, when you are working with many files and directories, EnumerateFiles can be more efficient.
|
|
/// </para>
|
|
/// </remarks>
|
|
/// <exception cref="ArgumentException"/>
|
|
/// <exception cref="ArgumentNullException"/>
|
|
/// <exception cref="DirectoryNotFoundException"/>
|
|
/// <exception cref="IOException"/>
|
|
/// <exception cref="NotSupportedException"/>
|
|
/// <exception cref="UnauthorizedAccessException"/>
|
|
/// <param name="transaction">The transaction.</param>
|
|
/// <param name="path">The directory to search.</param>
|
|
/// <param name="searchPattern">
|
|
/// The search string to match against the names of directories in <paramref name="path"/>.
|
|
/// This parameter can contain a combination of valid literal path and wildcard
|
|
/// (<see cref="Path.WildcardStarMatchAll"/> and <see cref="Path.WildcardQuestion"/>) characters, but does not support regular expressions.
|
|
/// </param>
|
|
/// <param name="searchOption">
|
|
/// One of the <see cref="SearchOption"/> enumeration values that specifies whether the <paramref name="searchOption"/>
|
|
/// should include only the current directory or should include all subdirectories.
|
|
/// </param>
|
|
[SecurityCritical]
|
|
public static string[] GetFileSystemEntriesTransacted(KernelTransaction transaction, string path, string searchPattern, SearchOption searchOption)
|
|
{
|
|
var options = DirectoryEnumerationOptions.FilesAndFolders | ((searchOption == SearchOption.AllDirectories) ? DirectoryEnumerationOptions.Recursive : 0);
|
|
|
|
return EnumerateFileSystemEntryInfosCore<string>(transaction, path, searchPattern, options, PathFormat.RelativePath).ToArray();
|
|
}
|
|
|
|
#endregion // Transactional
|
|
}
|
|
}
|
|
|