CreateNewNuGetPackageFromProjectAfterEachBuild 1.2.0-alpha

This is a prerelease version of CreateNewNuGetPackageFromProjectAfterEachBuild.
There is a newer version of this package available.
See the version list below for details.
dotnet add package CreateNewNuGetPackageFromProjectAfterEachBuild --version 1.2.0-alpha                
NuGet\Install-Package CreateNewNuGetPackageFromProjectAfterEachBuild -Version 1.2.0-alpha                
This command is intended to be used within the Package Manager Console in Visual Studio, as it uses the NuGet module's version of Install-Package.
<PackageReference Include="CreateNewNuGetPackageFromProjectAfterEachBuild" Version="1.2.0-alpha" />                
For projects that support PackageReference, copy this XML node into the project file to reference the package.
paket add CreateNewNuGetPackageFromProjectAfterEachBuild --version 1.2.0-alpha                
#r "nuget: CreateNewNuGetPackageFromProjectAfterEachBuild, 1.2.0-alpha"                
#r directive can be used in F# Interactive and Polyglot Notebooks. Copy this into the interactive tool or source code of the script to reference the package.
// Install CreateNewNuGetPackageFromProjectAfterEachBuild as a Cake Addin
#addin nuget:?package=CreateNewNuGetPackageFromProjectAfterEachBuild&version=1.2.0-alpha&prerelease

// Install CreateNewNuGetPackageFromProjectAfterEachBuild as a Cake Tool
#tool nuget:?package=CreateNewNuGetPackageFromProjectAfterEachBuild&version=1.2.0-alpha&prerelease                

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.

There are no supported framework assets in this package.

Learn more about Target Frameworks and .NET Standard.

This package has no dependencies.

NuGet packages (36)

Showing the top 5 NuGet packages that depend on CreateNewNuGetPackageFromProjectAfterEachBuild:

Package Downloads
ApolloDB

Description

ApolloAPI.Model

Description

MmBot.Jenkins

Description

MyAnimeListSharp

Search, Add, Update, Delete Anime/Manga information on MyAnimeList.net using Web API (http://myanimelist.net/modules.php?go=api)

SchoolsDB

Description

GitHub repositories (1)

Showing the top 1 popular GitHub repositories that depend on CreateNewNuGetPackageFromProjectAfterEachBuild:

Repository Stars
pedropaf/saas-ecom
Subscription support for ASP.NET MVC 5 apps using Stripe, including out-of-the-box view helpers. Available via NuGET
Version Downloads Last updated
1.8.16 126,227 10/18/2018
1.8.15 7,199 9/16/2018
1.8.14 53,376 5/16/2018
1.8.13 46,859 9/7/2017
1.8.11 48,077 3/22/2017
1.8.10 25,546 1/23/2017
1.8.9 110,115 3/27/2016
1.8.8 180,203 7/18/2015
1.8.7 14,655 6/16/2015
1.8.6 5,463 6/16/2015
1.8.5 22,095 3/23/2015
1.8.4 44,493 10/30/2014
1.8.4-alpha1 5,636 10/8/2014
1.8.3 13,087 8/20/2014
1.8.2 6,709 8/9/2014
1.8.1 6,357 7/15/2014
1.8.1-Prerelease3 5,406 7/10/2014
1.8.1-Prerelease2 5,163 7/5/2014
1.8.1-Prerelease1 5,330 6/14/2014
1.7.4-PreRelease 5,193 5/6/2014
1.7.3 11,847 3/2/2014
1.7.2 7,955 2/2/2014
1.7.1 7,779 1/18/2014
1.6.2 5,481 1/14/2014
1.6.1 5,596 1/13/2014
1.6.0 6,239 11/23/2013
1.5.2 6,313 11/7/2013
1.5.1 5,948 11/7/2013
1.5.0 6,199 10/28/2013
1.4.2 6,065 9/18/2013
1.4.1 6,282 9/18/2013
1.4.0 6,212 9/18/2013
1.3.0 8,669 7/12/2013
1.2.1 6,633 7/12/2013
1.2.0 6,245 7/12/2013
1.2.0-beta 6,037 7/12/2013
1.2.0-alpha 6,140 7/11/2013
1.1.0.1 6,549 7/8/2013
1.0.0 6,818 6/22/2013

Added new files to the PostBuildEvents folder to perform the actual packing and pushing. This allows the user to easily customize the pack and push options if needed. Also added a batch file that can be used to push the package so the user is not required to change their PowerShell Execution Policy setting.