Found 575 packages
VB.NET source file that contains an abstract base class called "LicenseInfo" that is used by various concrete licenses implementations and also by the AcknowledgementAttribute. Do not install this package manually, as it is installed automatically through referencing NuGet packages where 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.
VB.NET source file that contains a class "AcknowledgementAttribute" that may be used on any type (or method, property etc.) to give credit to the contributor of the code, including the exact license that applies. 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.
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.
Microsoft Information Protection SDK File API for C++/.NET Microsoft Information Protection (MIP) is the unification of Microsoft's classification, labeling, and protection services, into a single administration experience and software development kit (SDK). Unified administration is provided across Office 365, Azure Information Protection, Windows Information Protection, and other Microsoft services. Third parties can use the SDK to integrate with applications, using a standard, consistent data labeling schema and protection service. The MIP SDK exposes the labeling and protection services from Office 365 Security and Compliance Center to third-party applications and services. Developers can use the SDK to build native support for applying labels and protection to files. Developers can reason over which actions should be taken when specific labels are detected, and reason over MIP-encrypted information. Get Started at: https://aka.ms/mipsdkdocs https://aka.ms/mipsdksamples https://aka.ms/mipsdkblog
jQuery UI is an open source library of interface components — interactions, full-featured widgets, and animation effects — based on the stellar jQuery javascript library . Each component is built according to jQuery's event-driven architecture (find something, manipulate it) and is themeable, making it easy for developers of any skill level to integrate and extend into their own code. NOTE: This package is maintained on behalf of the library owners by the NuGet Community Packages project at http://nugetpackages.codeplex.com/
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.
The Open XML SDK provides tools for working with Office Word, Excel, and PowerPoint documents. It supports scenarios such as: - High-performance generation of word-processing documents, spreadsheets, and presentations. - Populating content in Word files from an XML data source. - Splitting up (shredding) a Word or PowerPoint file into multiple files, and combining multiple Word/PowerPoint files into a single file. - Extraction of data from Excel documents. - Searching and replacing content in Word/PowerPoint using regular expressions. - Updating cached data and embedded spreadsheets for charts in Word/PowerPoint. - Document modification, such as removing tracked revisions or removing unacceptable content from documents.
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.
A library to programmatically extract the contents of a single file application to a directory.
Microsoft Information Protection SDK File API for .NET Microsoft Information Protection (MIP) is the unification of Microsoft's classification, labeling, and protection services, into a single administration experience and software development kit (SDK). Unified administration is provided across Office 365, Azure Information Protection, Windows Information Protection, and other Microsoft services. Third parties can use the SDK to integrate with applications, using a standard, consistent data labeling schema and protection service. The MIP SDK exposes the labeling and protection services from Office 365 Security and Compliance Center to third-party applications and services. Developers can use the SDK to build native support for applying labels and protection to files. Developers can reason over which actions should be taken when specific labels are detected, and reason over MIP-encrypted information. Get Started at: https://aka.ms/mipsdkdocs https://aka.ms/mipsdksamples https://aka.ms/mipsdkblog
Scripting engine services specifically for single file applications
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.
VB.NET source file that contains an extension method that replaces accented characters within a string through non-accented ones, which is useful to create logon names, email addresses etc. German upper-case umlauts like "Ä" are converted either to "Ae" or "AE" depending the context, "ß" analogously may become "ss" or "SS". There is support for a lot of western characters, but as I am no linguist it might contain some errors as e.g. I as a Swiss am not sure whether an Islandic/Faroese "ð" should be converted to a "d", "dh" or a "th"... See also NuGet-package "SingleFile.VB.ExtString.RemoveUnwantedChars" to remove unsupported characters after substituting the accented 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.
VB.NET source file that contains a generic utility class that can be taken as base class for inner class implementations. It provides access to the outer instance and a property called DebuggerDisplayValue that can be used in the classes <DebuggerDisplay("{DebuggerDisplayValue}")> attribute. 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 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 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.
A library for reading and modifying bundles from single-file published .NET applications.
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.
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.
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.
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.