This article describes how to build and publish the NuGet package.
-
Increment the build numbers in the
scripts\assets\*.nuspec
files. -
Ensure that dependencies listed in *.nuspec files are consistent with NuGet packages used within the solution. Look at the
packages.config
files in each project. -
Run
scripts\build.cmd
and ensure everything builds properly. -
Run
scripts\runtests.cmd
and ensure all tests pass. -
Run
scripts\package.cmd
and ensure you have four *.nupkg files in\artifacts
. -
Set your NuGet API key. You only need to do this once.
-
Browse to https://www.nuget.org/
-
Sign-in with your credentials.
-
Browse to your account.
-
Copy your API key to the clipboard.
-
Run this command in the command-line:
nuget.exe setApiKey YOURAPIKEY
-
-
Update
publish-chatter.cmd
andpublish-force.cmd
to use the latest NuGet packages. -
Run
publish-chatter.cmd
. Ensure that the packages are pushed to both the NuGet Gallery and the symbol server.$ publish-chatter.cmd Pushing DeveloperForce.Chatter 1.1.0 to the NuGet gallery (https://www.nuget.org)... Your package was pushed. Pushing DeveloperForce.Chatter 1.1.0 to the symbol server (http://nuget.gw.symbolsource.org/Public/NuGet)... Your package was pushed. Pushing DeveloperForce.Chatter 1.1.0 to the symbol server (http://nuget.gw.symbolsource.org/Public/NuGet)... Your package was pushed.
-
Run
publish-force.cmd
. Ensure that the packages are pushed to both the NuGet Gallery and the symbol server.$ publish-force.cmd Pushing DeveloperForce.Force 1.1.0 to the NuGet gallery (https://www.nuget.org)... Your package was pushed. Pushing DeveloperForce.Force 1.1.0 to the symbol server (http://nuget.gw.symbolsource.org/Public/NuGet)... Your package was pushed. Pushing DeveloperForce.Force 1.1.0 to the symbol server (http://nuget.gw.symbolsource.org/Public/NuGet)... Your package was pushed.
-
Check and ensure the latest NuGets have been published.
-
Ideally test and make sure the latest NuGet packages work. ;-)
You're done!