The new home for NuGetPackageExplorer (moved from https://npe.codeplex.com)
C# Other
Latest commit 4106cc7 Nov 7, 2016 @304NotModified 304NotModified committed on GitHub Update README.md
Permalink
Failed to load latest commit information.
Build newlines Oct 26, 2016
CodeExecutor Show "strong name" in assembly properties, Apr 13, 2016
Common update version number to 3.19 Oct 26, 2016
Core update target frameworks Oct 25, 2016
PackageExplorer update version number to 3.19 Oct 26, 2016
PackageViewModel Added serviceable to GUI Jun 12, 2016
Packages Normalize line-endings to match .gitattributes Nov 22, 2015
Tools/7za920 Normalize line-endings to match .gitattributes Nov 22, 2015
Types Added serviceable to GUI Jun 12, 2016
lib Remove otherwise resouces error. Apr 13, 2016
.gitattributes Add standard .gittatributes to normalize line-endings moving forward Nov 22, 2015
.gitignore Change Windows8Shim target framework to Client profile. Aug 31, 2012
CodeAnalysisDictionary.xml Normalize line-endings to match .gitattributes Nov 22, 2015
ISSUE_TEMPLATE.md Update ISSUE_TEMPLATE.md Mar 5, 2016
LICENSE Add MIT license file. Oct 15, 2015
NuGet.exe update package content. Oct 30, 2011
NuGet.ruleset Normalize line-endings to match .gitattributes Nov 22, 2015
NuGetPackageExplorer.ruleset Normalize line-endings to match .gitattributes Nov 22, 2015
NuGetPackageExplorer.sln 3.11 release Feb 23, 2016
PackageExplorer_TemporaryKey.pfx Initial checkin May 28, 2011
README-developers.md Update README-developers.md Feb 29, 2016
README.md Update README.md Nov 7, 2016
appveyor.yml Update version number Oct 25, 2016
build.cmd verbosity:minimal build Jan 25, 2016
buildcertificate.pfx Initial checkin May 28, 2011
nuget.png Added nuspec Apr 16, 2016
nupack.ico Initial checkin May 28, 2011
nuspec.ico Initial checkin May 28, 2011
password.txt Initial checkin May 28, 2011

README.md

Logo

Twitter Follow

Rager Releases

Latest clickonce release (uninstall first if previous version is 3.9 or lower)

Chocolatey

Join the chat at https://gitter.im/NuGetPackageExplorer/NuGetPackageExplorer

Build status

NuGet Package Explorer is a ClickOnce & Chocolatey application that makes it easy to create and explore NuGet packages. After installing it, you can double click on a .nupkg file to view the package content, or you can load packages directly from nuget feeds like nuget.org.

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

image

Current development state / looking for developers

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

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

Creating a Package

  1. Launch Package Explorer 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 nuget.org, 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 user name (on the upper right) to navigate to your account settings.

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

![Copying the API key from the nuget.org profile](https://cloud.githubusercontent.com/assets/1339874/19167409/6fd8d238-8bc0-11e6-86b4-49af64483d78.png)
  1. Assuming your package is loaded in Package Explorer, select File > Publish (Ctrl+P) to bring up the Publish Package dialog:

    Publish Package Dialog

  2. Paste your API key intp Publish key and click Publish to push the package to nuget.org.

  3. In your profile on nuget.org, 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.