Skip to main content
CreateNewNuGetPackageFromProjectAfterEachBuild package icon

CreateNewNuGetPackageFromProjectAfterEachBuild

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 folder to your project to house the PowerShell script that is called from the project's Post-Build event to create the NuGet package. If it does not seem to be working, check the Output window for any errors that may have occurred.

Total Downloads
1.0M
1,046,805
Published
Mar 27, 2016
Latest stable version

Install

.NET CLI
dotnet add package CreateNewNuGetPackageFromProjectAfterEachBuild --version 1.8.9
Package Manager Console
Install-Package CreateNewNuGetPackageFromProjectAfterEachBuild -Version 1.8.9
PackageReference
<PackageReference Include="CreateNewNuGetPackageFromProjectAfterEachBuild" Version="1.8.9" />

Frameworks

No framework metadata available.

Dependencies

No declared dependencies.

Adoption guide

Assess this package against its supported frameworks, license, maintenance signals and dependency graph before making it a project standard.

No SPDX license expression is published. Review the license text and your organisation's policy before redistribution.

No target framework metadata is available. Confirm compatibility in a representative project before standardising on this package.

How to read this guidance

Sources: published NuGet v3 registry metadata and explicit NuBrowse editorial guides. Refresh: package metadata is refreshed from NuGet when the page loads. Limit: this is not a security, legal or compatibility guarantee; validate the selected version in your project.

Useful next steps

Move from package metadata to a concrete selection or review workflow.