SingleFile.VB.LicenseInfo.MitLicense
1.0.26
See the version list below for details.
dotnet add package SingleFile.VB.LicenseInfo.MitLicense --version 1.0.26
NuGet\Install-Package SingleFile.VB.LicenseInfo.MitLicense -Version 1.0.26
<PackageReference Include="SingleFile.VB.LicenseInfo.MitLicense" Version="1.0.26" />
paket add SingleFile.VB.LicenseInfo.MitLicense --version 1.0.26
#r "nuget: SingleFile.VB.LicenseInfo.MitLicense, 1.0.26"
// Install SingleFile.VB.LicenseInfo.MitLicense as a Cake Addin #addin nuget:?package=SingleFile.VB.LicenseInfo.MitLicense&version=1.0.26 // Install SingleFile.VB.LicenseInfo.MitLicense as a Cake Tool #tool nuget:?package=SingleFile.VB.LicenseInfo.MitLicense&version=1.0.26
VB.NET source file that contains a subclass of LicenseInfo with the details to the "MIT License" (worded by the Massachusetts Institute of Technology) to be included through an Acknowledgement attribute in source code and libraries.
Supported versions:
.NET Framework 2.0
.NET Framework 3.0
.NET Framework 3.5
.NET Framework 3.5 Client Profile
.NET Framework 4.0
.NET Framework 4.0 Client Profile
.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 8 (shipped in 2005 with .NET 2.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.
Learn more about Target Frameworks and .NET Standard.
-
- SingleFile.VB.Acknowledgement (>= 1.0.26)
- SingleFile.VB.LicenseInfo (>= 1.0.26)
NuGet packages (27)
Showing the top 5 NuGet packages that depend on SingleFile.VB.LicenseInfo.MitLicense:
Package | Downloads |
---|---|
SingleFile.VB.ExtString.EnumerateLines
VB.NET source file that contains an extension method that yields each line of a given text. The following line separators are recognized: CRLF (0D0A), LFCR (0A0D), LF (0A), CR (0D), VT (0B), FF (0C), LS (2028) and PS (2029). 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 11 (shipped in 2012 with .NET 4.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.ExtString.FillIn
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. |
|
SingleFile.VB.ExtArray.Shuffle
VB.NET source file that contains an extension method that allows to shuffle an array or other IList. 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.ExtString.RemoveUnwantedChars
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. |
|
SingleFile.VB.ExtArray.GetEmptyArray
VB.NET source file that contains a module with a function to get an empty array of an arbitrary type (always the same instance is returned). This is slightly faster and uses slightly less memory than returning a new empty array every time needed. Supported versions: .NET Framework 2.0 .NET Framework 3.0 .NET Framework 3.5 .NET Framework 3.5 Client Profile .NET Framework 4.0 .NET Framework 4.0 Client Profile .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 8 (shipped in 2005 with .NET 2.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.
SingleFile.VB (from 1.0.17 to 1.0.25)
VB.NET Source File Collection
Packaged on 2016-05-19 22:26
- Package "SingleFile.VB.ExtByte.ToEnglishOrdinal" added.
- Package "SingleFile.VB.ExtSByte.ToEnglishOrdinal" added.
- Package "SingleFile.VB.ExtInt16.ToEnglishOrdinal" added.
- Package "SingleFile.VB.ExtUInt16.ToEnglishOrdinal" added.
- Package "SingleFile.VB.ExtInt32.ToEnglishOrdinal" added.
- Package "SingleFile.VB.ExtUInt32.ToEnglishOrdinal" added.
- Package "SingleFile.VB.ExtInt64.ToEnglishOrdinal" added.
- Package "SingleFile.VB.ExtUInt64.ToEnglishOrdinal" added.
- Package "SingleFile.VB.ExtByte.IsMultipleOf" added.
- Package "SingleFile.VB.ExtSByte.IsMultipleOf" added.
- Package "SingleFile.VB.ExtArray.GetEmptyArray" added.
- Package "SingleFile.VB.ExtString.FillIn" now uses "SingleFile.VB.ExtArray.GetEmptyArray". Watch out: Sometimes the update copies the files needed into the project but does not add it to it. In this case, click on the "Show all files" button and include these files manually.
- Package description improved.
- Minimum required language version for each project determined and added to the package description (and lots of minor syntax changes made to decrease the requirements).
- SingleFile.VB.ExtBigInteger.ToByteArray: .NET 3.5 version removed as it references System.Numerics.dll that was added with .NET 4.0.
- SingleFile.VB.ExtByteArray.ToBigInteger: .NET 3.5 version removed as it references System.Numerics.dll that was added with .NET 4.0.