7 packages tagged with “exclude”
This package contains extension methods that allow you to get the interfaces for a System.Type whilst excluding inherited interfaces.
Extends Microsoft.Extensions.FileSystemGlobbing with the functionality to expand braces (e.g. *.{jpg,png}) and to allow glob excludes to be defined in the glob pattern itself (e.g. '!**/*.exe' to exclude .exe files)
Additional filters for Swashbuckle.AspNetCore to exclude duplicated information from schema.
Smooth scroll is a feature complete jQuery utility with bookmark, page top and sticky box options. A highly customizable configuration object allows you to decide what feature to activate, set scroll speeds and start/complete callbacks independently for each feature, and activate bookmarks in many ways. Activate bookmarks via class, element, container or lists, and exclude in similar ways with ease. The sticky box has a user defined threshold for when it appears.
Additional string operations to remove first and last character of a string.
VB.NET source file that contains an extension method that removes unwanted characters from a string according to a given include and/or exclude character mask. See also NuGet-package "SingleFile.VB.ExtString.ConvertAccents" to substitute accented characters through unaccented ones. Supported versions: .NET Framework 3.5 .NET Framework 4.0 .NET Framework 4.5 .NET Framework 4.5.1 .NET Framework 4.5.2 .NET Framework 4.6 .NET Framework 4.6.1 Language requirement: Visual Basic 9 (shipped in 2007 with .NET 3.5) This package is part of the "SingleFile.VB" collection that consists of small utilities in the form of VB.NET source files, usually two of them per package, namely the code file and the test file (Microsoft standard unit tests) as well as the license files that are shared over all "Single.VB" packages. Some philosophy: Extension methods and other static utility functions are not shared accross projects resp. assemblies but included wherever they are needed. For that reason they are declared "Friend" and namespace-less as they are supposed to be part of the project's current namespace. Unit test files are added directly to the project and declared "Public" because of limitations of that framework, but they are only compiled in debug mode (through a compiler directive that checks for the "DEBUG" keyword). This allows to keep the tests very near to the code which simplifies access to internal members but does not bulk the published version. The reference to "Microsoft.VisualStudio.TestTools.UnitTesting" (assembly "Microsoft.VisualStudio.QualityTools.UnitTestFramework.dll") is only needed during development and may be declared with "Copy Local = False". The NuGet package version is global across all "Single.VB" packages, and they always reference other packages of the same version (most recent at the time of publishing). This greatly simplifies my dependency handling and therefore improves the quality of the NuGet packages, but may leed to an updated package that does not contain any code change. I apologize for that inconvenience. Your feedback and/or contribution is welcome. Please contact me on singlefile.vb@gmail.com.
Use Catcher.Run(() => ...) for preventing a task to throw during a "one-fails-all" operation like Task.WhenAll or AwaitMultiple.