|
- /* 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.GetFiles() is less efficient than Directory.EnumerateFiles(),
- // only .NET and AlphaFS Transactional methods are implemented. No additional overloaded methods.
-
- #region .NET
-
- /// <summary>Returns the names of files (including their paths) in the specified directory.</summary>
- /// <returns>An array of the full names (including paths) for the files in the specified directory, or an empty array if no files are found.</returns>
- /// <remarks>
- /// <para>The returned file names are appended to the supplied <paramref name="path"/> parameter.</para>
- /// <para>The order of the returned file names is not guaranteed; use the Sort() method if a specific sort order is required.</para>
- /// <para>The EnumerateFiles and GetFiles methods differ as follows: When you use EnumerateFiles, you can start enumerating the collection of names
- /// before the whole collection is returned; when you use GetFiles, you must wait for the whole array of names 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>
- [SecurityCritical]
- public static string[] GetFiles(string path)
- {
- return EnumerateFileSystemEntryInfosCore<string>(null, path, Path.WildcardStarMatchAll, DirectoryEnumerationOptions.Files, PathFormat.RelativePath).ToArray();
- }
-
- /// <summary>Returns the names of files (including their paths) that match the specified search pattern in the specified directory.</summary>
- /// <returns>An array of the full names (including paths) for the files in the specified directory that match the specified search pattern, or an empty array if no files are found.</returns>
- /// <remarks>
- /// <para>The returned file names are appended to the supplied <paramref name="path"/> parameter.</para>
- /// <para>The order of the returned file names is not guaranteed; use the Sort() method if a specific sort order is required.</para>
- /// <para>The EnumerateFiles and GetFiles methods differ as follows: When you use EnumerateFiles, you can start enumerating the collection of names
- /// before the whole collection is returned; when you use GetFiles, you must wait for the whole array of names 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>
- [SecurityCritical]
- public static string[] GetFiles(string path, string searchPattern)
- {
- return EnumerateFileSystemEntryInfosCore<string>(null, path, searchPattern, DirectoryEnumerationOptions.Files, PathFormat.RelativePath).ToArray();
- }
-
- /// <summary>Returns the names of files (including their paths) that match the specified search pattern in the current directory, and optionally searches subdirectories.</summary>
- /// <returns>An array of the full names (including paths) for the files in the specified directory that match the specified search pattern and option, or an empty array if no files are found.</returns>
- /// <remarks>
- /// <para>The returned file names are appended to the supplied <paramref name="path"/> parameter.</para>
- /// <para>The order of the returned file names is not guaranteed; use the Sort() method if a specific sort order is required.</para>
- /// <para>The EnumerateFiles and GetFiles methods differ as follows: When you use EnumerateFiles, you can start enumerating the collection of names
- /// before the whole collection is returned; when you use GetFiles, you must wait for the whole array of names 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[] GetFiles(string path, string searchPattern, SearchOption searchOption)
- {
- var options = DirectoryEnumerationOptions.Files | ((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 files (including their paths) in the specified directory.</summary>
- /// <returns>An array of the full names (including paths) for the files in the specified directory, or an empty array if no files are found.</returns>
- /// <remarks>
- /// <para>The returned file names are appended to the supplied <paramref name="path"/> parameter.</para>
- /// <para>The order of the returned file names is not guaranteed; use the Sort() method if a specific sort order is required.</para>
- /// <para>The EnumerateFiles and GetFiles methods differ as follows: When you use EnumerateFiles, you can start enumerating the collection of names
- /// before the whole collection is returned; when you use GetFiles, you must wait for the whole array of names 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>
- [SecurityCritical]
- public static string[] GetFilesTransacted(KernelTransaction transaction, string path)
- {
- return EnumerateFileSystemEntryInfosCore<string>(transaction, path, Path.WildcardStarMatchAll, DirectoryEnumerationOptions.Files, PathFormat.RelativePath).ToArray();
- }
-
- /// <summary>Returns the names of files (including their paths) that match the specified search pattern in the specified directory.</summary>
- /// <returns>An array of the full names (including paths) for the files in the specified directory that match the specified search pattern, or an empty array if no files are found.</returns>
- /// <remarks>
- /// <para>The returned file names are appended to the supplied <paramref name="path"/> parameter.</para>
- /// <para>The order of the returned file names is not guaranteed; use the Sort() method if a specific sort order is required.</para>
- /// <para>The EnumerateFiles and GetFiles methods differ as follows: When you use EnumerateFiles, you can start enumerating the collection of names
- /// before the whole collection is returned; when you use GetFiles, you must wait for the whole array of names 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>
- [SecurityCritical]
- public static string[] GetFilesTransacted(KernelTransaction transaction, string path, string searchPattern)
- {
- return EnumerateFileSystemEntryInfosCore<string>(transaction, path, searchPattern, DirectoryEnumerationOptions.Files, PathFormat.RelativePath).ToArray();
- }
-
- /// <summary>Returns the names of files (including their paths) that match the specified search pattern in the current directory, and optionally searches subdirectories.</summary>
- /// <returns>An array of the full names (including paths) for the files in the specified directory that match the specified search pattern and option, or an empty array if no files are found.</returns>
- /// <remarks>
- /// <para>The returned file names are appended to the supplied <paramref name="path"/> parameter.</para>
- /// <para>The order of the returned file names is not guaranteed; use the Sort() method if a specific sort order is required.</para>
- /// <para>The EnumerateFiles and GetFiles methods differ as follows: When you use EnumerateFiles, you can start enumerating the collection of names
- /// before the whole collection is returned; when you use GetFiles, you must wait for the whole array of names 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[] GetFilesTransacted(KernelTransaction transaction, string path, string searchPattern, SearchOption searchOption)
- {
- var options = DirectoryEnumerationOptions.Files | ((searchOption == SearchOption.AllDirectories) ? DirectoryEnumerationOptions.Recursive : 0);
-
- return EnumerateFileSystemEntryInfosCore<string>(transaction, path, searchPattern, options, PathFormat.RelativePath).ToArray();
- }
-
- #endregion // Transactional
- }
- }
|