Creating NuGet packages is something currently bestdone by using a package manifest or by packaging your Visual Studio project. The reason for this is that artifacts are created in a reproducible way: the manifest is kept around; the project is kept around, and the same version of all code will always result in the same NuGetpackage. It can even be automated by creating a batch script that runs several
NuGet.exe commands at once.
In many situations, for example when exploring what other people do in their NuGet packages or when creating a test package, a dedicated user interface to work with NuGet packages is preferable. For this purpose, Luan Nguyen (
@dotnetjunky on Twitter) has created NuGet Package ...