SingleFile.VB.ExtInt64.ToEnglishOrdinal by Christoph Hafner (project owner) and the community (contributions)

<PackageReference Include="SingleFile.VB.ExtInt64.ToEnglishOrdinal" Version="1.0.25" />

 SingleFile.VB.ExtInt64.ToEnglishOrdinal 1.0.25

VB.NET source file that contains an extension method that translates an Int64 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 [email protected]

<package xmlns="http://schemas.microsoft.com/packaging/2012/06/nuspec.xsd">
  <metadata>
    <id>SingleFile.VB.ExtInt64.ToEnglishOrdinal</id>
    <version>1.0.25</version>
    <title>ExtInt64_ToEnglishOrdinal.vb</title>
    <authors>Christoph Hafner (project owner) and the community (contributions)</authors>
    <owners>Christoph Hafner (project owner) and the community (contributions)</owners>
    <licenseUrl>http://opensource.org/licenses/MIT</licenseUrl>
    <requireLicenseAcceptance>false</requireLicenseAcceptance>
    <description>VB.NET source file that contains an extension method that translates an Int64 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 [email protected]</description>
    <summary>Extension method that translates an Int64 into an English ordinal.</summary>
    <releaseNotes>SingleFile.VB (1.0.25)
VB.NET Source File Collection
Packaged on 2016-01-22 00:16

Initial release.</releaseNotes>
    <tags>SingleFile.VB.ExtInt64.ToEnglishOrdinal ExtInt64_ToEnglishOrdinal.vb Test_ExtInt64_ToEnglishOrdinal.vb English ordinal number 1st 2nd 3rd 4th Int64 System.Int64 Long extension method SingleFile.VB SingleFile VB.NET Source Christoph Hafner [email protected]</tags>
    <dependencies>
      <dependency id="SingleFile.VB.LicenseInfo.MitLicense" version="1.0.25" />
    </dependencies>
    <frameworkAssemblies>
      <frameworkAssembly assemblyName="mscorlib" targetFramework="" />
      <frameworkAssembly assemblyName="Microsoft.VisualStudio.QualityTools.UnitTestFramework" targetFramework="" />
    </frameworkAssemblies>
  </metadata>
</package>