Top 20 NuGet nuget Packages

NetSqlAzMan is for all Microsoft .NET 4.0 developers that need to manage loosely-coupled applicative authorizations, that is, weakly coupled with source code, in a light and fast way having all these authorizations in a relational database such as MS Sql Server (2000/MSDE/2005/2008/Express).

Generic part of service for publishing of NuGet packages

Create NuGet packages during your build. Adds NuGetPack.exe to your solution

Simple Git Version implementation based on LibGit2Sharp. Used by SimpleGitVersion.MsBuild.

NuGet interface for Orchard CMS

NuPack create a nuget package on build action for .NET 4.0+

Provides the core functionality to deploy updates to your application via a nuget package

PowerShell tools for various tasks implemented as scripts, mostly standalone.

Get license of NuGet packages in 'packages' folder of a solution. Infer license from projectUrl and licenseUrl in the package's metadata. Download license text from GtiHub and spdx.org.

Client library for the NuGet Search Service

Add a NuGet package only for dll reference? By using dotnetCampus.SourceYard, you can pack a NuGet package with source code. By installing the new source code package, all source codes behaviors just like it is in your project.

.NET core tool that verifies that all NuGet packages in a solution are consolidated

Package Description

PowerShell module to create and manage Nuspec manifests and NuGet packages.

.NET Standard library that provides some nuget package related functionality against the nuget V3 API.

PowerShell module packaging support for .NET SDK-style projects

Add a text file `package.blacklist` to your project, with the blacklisted package IDs on separate lines. A task will run `BeforeBuild` that will fail if any packages are found on the blacklist.

Central Package Versions for ASP.NET legacy projects

Automatically creates a NuGet package from your project each time it builds. The NuGet package is placed in the project's output directory. If you want to use a .nuspec file, place it in the same directory as the project's project file (e.g. .csproj, .vbproj, .fsproj). This adds a PostBuildScripts...