Create, update and deploy Nuget Packages with a GUI
C# Other
Latest commit 7904e7c Sep 23, 2017 @304NotModified 304NotModified committed on GitHub Merge pull request #228 from onovotny/package-project
Package project
Permalink
Failed to load latest commit information.
Build newlines Oct 26, 2016
CodeExecutor Update to package project Sep 22, 2017
Common Factor things out into common props Sep 23, 2017
Core Update to package project Sep 22, 2017
PackageExplorer.Package bump tpv Sep 22, 2017
PackageExplorer Factor things out into common props Sep 23, 2017
PackageViewModel Update to package project Sep 22, 2017
Packages update NuGetPackageExplorer.Types version and creation May 13, 2017
Tools/7za920 Normalize line-endings to match .gitattributes Nov 22, 2015
Types Factor things out into common props Sep 23, 2017
images Doc updates Mar 25, 2017
lib Use private version with fixes Sep 22, 2017
.gitattributes Add standard .gittatributes to normalize line-endings moving forward Nov 22, 2015
.gitignore Added support for Tizen and .NET Core App (#226) Aug 30, 2017
CodeAnalysisDictionary.xml Normalize line-endings to match .gitattributes Nov 22, 2015
Directory.Build.props Factor things out into common props Sep 23, 2017
ISSUE_TEMPLATE.md Update ISSUE_TEMPLATE.md Mar 27, 2017
LICENSE Add MIT license file. Oct 15, 2015
NuGetPackageExplorer.ruleset Normalize line-endings to match .gitattributes Nov 22, 2015
NuGetPackageExplorer.sln Factor things out into common props Sep 23, 2017
PackageExplorer_TemporaryKey.pfx Initial checkin May 28, 2011
PrivacyPolicy.md Create PrivacyPolicy.md Feb 18, 2017
README-developers.md Update developers readme (#180) Mar 29, 2017
README.md Factor things out into common props Sep 23, 2017
appveyor.yml appveyor Sep 23, 2017
build.cmd verbosity:minimal build Jan 25, 2016
buildcertificate.pfx Initial checkin May 28, 2011
password.txt Initial checkin May 28, 2011
version.json Factor things out into common props Sep 23, 2017

README.md

Logo

Build status Twitter Follow Join the chat at https://gitter.im/NuGetPackageExplorer/NuGetPackageExplorer Chocolatey Rager Releases

How to install

You could install with the Windows 10 Store, ClickOnce or Chocolatey. The Windows Store is the preferred version for Windows 10 Anniversary Update and later.

Windows Store (recommended, Windows 10 Anniversary Update needed)

Get it on Windows 10

Chocolatey

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

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

ClickOnce

There are a lot of installing issues with ClickOnce, including a SmartScreen-related error.

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

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 file from disk or directly from a feed such as nuget.org.

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

image

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!

Issues

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 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 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 nuget.org 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 nuget.org.

  6. 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.

Build

Requirements to build the project: