34 packages tagged with “ExtensionMethod”
Adds some convenient extension methods to strings.
C# and VB.NET Extension Methods | Over 1000 methods available.
Convenience methods for enums.
The .NET Extensions project provides the missing piece that you always expected to be part of the Framework Class Library. The project literally contains hundreds of extension methods for well known FCL data types. You can just add a reference and start using them today. "This library was immediately useful. I began using methods that I didn't even realize were implemented in it because it covers methods that naturally feel like they should be there." "It just work!, i don't have to add any using statement" "Where have you been all my life..." "Get this library from NuGet and you can immediately start using it without any "using" statements or anything. Starts to feel like they are actually part of the framework. Excellent library!"
A list of extension methods for commonly used functionality
Collection of common extensions and helpers for standard types
Popular .Net Core / .Net Framework extension methods Project Site: https://viacooky.github.io/Lett.Extensions/
This Package Contain Useful Library And Extension Method For Easy Develop High Tech .Net Application With EntityFramework. ForExample : Implementation Of Custom DbContext, DbContext Extension Method, DbSet Extension Method, ...
This Package Contain Useful Library And Extension Method For Easy Develop High Tech .Net Core Application With EntityFrameworkCore. ForExample : Implementation Of Custom DbContext, DbContext Extension Method, DbSet Extension Method, ...
the extension method for various type, String, Array, DataTable, Dictionary, etc
This Package Contain Useful Library And Extension Method For Easy Develop High Tech .Net Core Application With EntityFrameworkCore. ForExample : Implementation Of Custom Entity Validation, Extension Method, Annotation, StoredProcedure ...
DNTExtensions is a Library that contains some useful Extension methods
Several extension methods that provide code reuse. Developed by the company IronBug.
CustomExtensions - Custom Extension Methods For C# This is an open-source library of C# extension methods used to add functionality to commonly used classes and to enhance LINQ.
For Contact Us Please Send Mail Or Call To : Tel : +989301919109 Mail : mehrannoruzi@gmail.com
For Contact Me Please Send Mail Or Call To : Tel : +989301919109 Mail : mehrannoruzi@gmail.com
A collection of extension methods supplementing a variety of classes in the .NET Framework.
C# Extension Methods
VB.NET source file with a better implementation of String.Format(..) that does not throw an exception if an opening "{" is somewhere in the text or if not all placeholders are used. 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.
This contians the dotnet string extension methods that you were missing all those years like: .IsNull() .IsNotNull() .IsEmpty() .IsNotEmpty() .IsNullOrEmpty() .IsNotNullOrEmpty() .IsNullOrWhiteSpace() .IsNotNullOrWhiteSpace() .IsOnlyWhiteSpace() .IsNotOnlyWhiteSpace() .IsBase64String() .IsNotBase64String() .IsEmailAddress() .IsUri() .IsNumeric() .IsAlphaNumeric() .IsMatch(@"^\d{4}AAA\d{3}$") .IsMatch(CustomerNumberRegEx) .ContainsAny('A', 'B', 'C') .ContainsAny('A', 'B', 'C', CharacterComparison.InvariantCultureIgnoreCase) .ContainsAll('A', 'B', 'C') .ContainsAll('A', 'B', 'C', CharacterComparison.InvariantCultureIgnoreCase) .ContainsNone('1', ':') .EqualsAny("Hello", "World") .EqualsAny("hElLo", "wOrLd", StringComparison.CurrentCultureIgnoreCase) .EqualsNone("hey", "hi", "hello", "ola") .Until(':') .UntilLast("\r\n") .CountOccurrences('/') .CountOccurrences("cat", StringComparison.CurrentCultureIgnoreCase) .GetWordCount()
NuniToolbox is a collection of common functions for the lazy programmer
VB.NET source file that provides an extension method to convert byte arrays into positive BigInteger values, taking into account the given endianness. Supported versions: .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 10 (shipped in 2010 with .NET 4.0) 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.