9 packages tagged with “Int32”
A collection of useful extension methods.
Editors contains part-based and masked editors for everything from date/time to currency entry, with unique designs that are specifically crafted to support input by keyboard, mouse, touch, and pen in WPF applications. Edit box controls support .NET data types input such as dates, times, numbers, brushes, colors, enumerations, sizes, and many more. Other controls include a regex-based masked textbox, auto-complete box, calculator, month calendar, star rating, gradient stop slider, and various color component pickers. Documentation is available on the Actipro web site (https://www.actiprosoftware.com/docs/controls/wpf/index?v=25.1), and samples can be downloaded from the Actipro WPF Controls GitHub repository (https://github.com/Actipro/WPF-Controls). NOTE: This is a commercial software product and requires proper paid licensing for legal usage. See Actipro's web site (https://www.actiprosoftware.com/purchase) for links to purchase developer licenses, or view the Sales FAQ for more information about evaluations and licensing.
Makes it easier to convert simple types.
Basic extensions for string, int, Linq, List, Object, Properties, StringBuilder, and Dictionary to simplify routine tasks.
Extension methods to read/write different datatypes to Span<byte>. See documentation on GitHub for examples.
A library that presents a wrapper structure named 'Numeric' which can contain different types of numbers.
VB.NET source file that contains an extension method that determines whether an Int32 value is a multiple of another value (Decimal). Zero values are handled correctly without throwing any DivideByZeroException. 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.
VB.NET source file that contains an extension method that translates an Int32 into an English ordinal (1, 2, 3 becomes "1st", "2nd", "3rd"). 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.
Random Extension Methods for SByte, Byte, Int16, UInt16, Int32, UInt32, Int64, UInt64, short, int, long