SingleFile.VB.ExtString.FillIn 1.0.27

dotnet add package SingleFile.VB.ExtString.FillIn --version 1.0.27                
NuGet\Install-Package SingleFile.VB.ExtString.FillIn -Version 1.0.27                
This command is intended to be used within the Package Manager Console in Visual Studio, as it uses the NuGet module's version of Install-Package.
<PackageReference Include="SingleFile.VB.ExtString.FillIn" Version="1.0.27" />                
For projects that support PackageReference, copy this XML node into the project file to reference the package.
paket add SingleFile.VB.ExtString.FillIn --version 1.0.27                
#r "nuget: SingleFile.VB.ExtString.FillIn, 1.0.27"                
#r directive can be used in F# Interactive and Polyglot Notebooks. Copy this into the interactive tool or source code of the script to reference the package.
// Install SingleFile.VB.ExtString.FillIn as a Cake Addin
#addin nuget:?package=SingleFile.VB.ExtString.FillIn&version=1.0.27

// Install SingleFile.VB.ExtString.FillIn as a Cake Tool
#tool nuget:?package=SingleFile.VB.ExtString.FillIn&version=1.0.27                

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.

There are no supported framework assets in this package.

Learn more about Target Frameworks and .NET Standard.

NuGet packages (2)

Showing the top 2 NuGet packages that depend on SingleFile.VB.ExtString.FillIn:

Package Downloads
SingleFile.VB.ExtDouble.TruncToInt64

VB.NET source file with an extension method that allows to truncate (instead of bankers round) Double values into Int64 ones, optionally throwing an exception if the value is out-of-range. 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.

SingleFile.VB.ExtBigInteger.ToByteArray

VB.NET source file that contains an extension method that allows to convert a positive BigInteger into a byte array, taking into account the desired 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.

GitHub repositories

This package is not used by any popular GitHub repositories.

Version Downloads Last updated
1.0.27 2,904 5/20/2016
1.0.26 2,704 5/19/2016

Tests improved, they now explicitly set the decimal separator and grouping symbol for the cultures used to test the number formats as on some systems they are defined differently (Windows 8.1 confustion for "de-CH", "fr-CH" and "it-CH").