Create, update and deploy Nuget Packages with a GUI
Failed to load latest commit information.
.github add probot config Aug 16, 2018
Build consolidate build files Sep 12, 2018
Common Move to NuGet.Packaging for creation and reading of packages (#252) Nov 27, 2017
Core move windows.winmd hint path detection to Directory.Build.props Sep 6, 2018
PackageExplorer.Package.Nightly R2r (#431) Jun 13, 2018
PackageExplorer.Package R2r (#431) Jun 13, 2018
PackageExplorer Merge pull request #465 from campersau/settings Sep 8, 2018
PackageViewModel support uap settings Sep 6, 2018
Packages update NuGetPackageExplorer.Types version and creation May 13, 2017
Tools/7za920 Normalize line-endings to match .gitattributes Nov 22, 2015
Types Update to latest nuget libs Aug 11, 2018
images add images (#295) Dec 18, 2017
lib Use private version with fixes Sep 22, 2017
.editorconfig add a few other defaults Jun 28, 2018
.gitattributes Add standard .gittatributes to normalize line-endings moving forward Nov 22, 2015
.gitignore update .gitignore Jul 2, 2018
CodeAnalysisDictionary.xml Normalize line-endings to match .gitattributes Nov 22, 2015
Directory.Build.props move windows.winmd hint path detection to Directory.Build.props Sep 6, 2018 Typos in issue template (#347) Feb 18, 2018
LICENSE.txt renaming license to avoid pack issue with directory Nov 30, 2017
NuGet.config Convert exe to sdk style project Dec 13, 2017
NuGetPackageExplorer.ruleset Normalize line-endings to match .gitattributes Nov 22, 2015
NuGetPackageExplorer.sln Update build to use tasks Jul 2, 2018 Create Feb 18, 2017 update-nuget (#316) Jan 20, 2018 Update Sep 13, 2018
azure-pipelines.yml Update and rename .azure-pipelines.yml to azure-pipelines.yml Sep 15, 2018
build.cmd Update build.cmd Sep 11, 2018
global.json latest extras Jun 28, 2018
nuget.png add icon that chocolatey uses (#289) Dec 17, 2017
version.json bump to 4.4 (#427) Jun 7, 2018


Build Status Twitter Follow Join the chat at

How to install

You could install with the Microsoft Store or Chocolatey. The Microsoft Store is the preferred version for Windows 10 Anniversary Update and later. It auto-updates and is the full application.

There also a nightly build available for direct install on Windows 10 Anniversary Update and higher. The nightly build installs alongside the release version with no interference.

Build Number Link
Nightly build number Install
Stable build number Microsoft Store
Chocolatey build number Chocolatey

Microsoft Store (recommended, Windows 10 Anniversary Update needed)

Get it on Windows 10


Chocolatey is another great way to install and update your application.

  1. Run PowerShell (as Admin)
  2. Install Chocolatey: iwr -UseBasicParsing | iex
  3. Install NuGet Package Explorer: choco install nugetpackageexplorer

What is NuGet Package Explorer?

NuGet Package Explorer (NPE) is an application that makes it easy to create and explore NuGet packages. You can load a .nupkg or .snupkg file from disk or directly from a feed such as

To build packages from the command line, use NuGet command-line tools, as documented on the official NuGet site.


Current development state / looking for developers

Currently NPE isn't actively developed, but we do accept (not too large) pull requests (PR).

If you'd like to help, please check the GitHub issues. If you'd like to contribute more structurally, we would be happy to add you to our team!


Please check the FAQ first and search for duplicate issues before reporting them.

Creating a Package

  1. Launch NPE and select File > New (Ctrl-N), or select Create a new package from the Common tasks dialog when Package Explorer starts:

    Package Explorer's common tasks dialog

  2. Select Edit > Edit Package Metadata (Ctrl-K) to open the editor for the underlying .nuspec file. Details for the metadata can be found in the nuspec reference.

    Editing package metadata with the Package Explorer

  3. Open the files you want to include in the package in Windows explorer, then drag them into the Package contents pane of Package Explorer. Package Explorer will attempt to infer where the content belongs and prompt you to place it in the correct directory within the package. (You can also explicitly add specific folders using the Content menu.)

    For example, if you drag an assembly into the Package contents window, it will prompt you to place the assembly in the lib folder:

    Package Explorer infers content location and prompts for confirmations

    The package's lib folder with added content

  4. Save your package with File > Save (Ctrl-S).

Publishing a Package

  1. Create a free account on, or log in if you already have one. When creating a new account, you'll receive a confirmation email. You must confirm the account before you can upload a package.

  2. Once logged in, click your username (on the upper right) to navigate to your account settings.

  3. Under API Key, click copy to clipboard to retrieve the API key you'll need in the next step.

    Copying the API key from the profile

  4. Assuming your package is loaded in Package Explorer, select File > Publish (Ctrl-P) to bring up the Publish Package dialog.

    Publish Package Dialog

  5. Paste your API key into Publish key and click Publish to push the package to

  6. In your profile on, click Manage my Packages to see the one that you just published; you'll also receive a confirmation email. Note that it might take a while for your package to be indexed and appear in search results, during which time you'll see a message that the package hasn't yet been indexed.


Requirements to build the project: