NuGet Package Explorer 2.0 release notes

1. Compatible with NuGet 1.5

NuGet 1.5 adds a couple of new metadata to the .nuspec file format. These include the Copyright, Release Notes and References elements. NPE 2.0 adds support for these attributes in the metadata editor.





As an added bonus, NPE 2.0 also adds a convenient command to the file context menu to allow quickly adding an assembly to the References collection.



2. Added Package Analysis command

NPE 2.0 adds a new command called Package Analysis. Think of it as the equivalent of FxCop for NuGet package authoring. When you choose Tools – Analyze Package command, NPE will analyze the contents of the current package, including metadata, based on a set of default rules and reports all potential issues with it. These rules represent best practices for package authoring that are recommended by the NuGet team. The rules are extensible via plugins (read #4 below for more details).




3. Work with Basic Authentication feeds

NPE 2.0 now works with package feeds that require Basic Authentication. When requesting packages from these feeds, the familiar credential dialog will pop up asking for your username and password. This means you can use NPE to open your private MyGet feeds.



4. More extensibility points for plugins

NPE 1.5 introduced the concept of plugins. However, prior to 2.0, you can only write custom viewers for package file content. In 2.0, there are two new extensibility points:

  • Custom package command - You can write a custom package command which will be displayed as a menu item under Tools. The command has access to an IPackage instance, which represents the currently opened package.
  • Custom rule – You can write a custom rule which augments the set of default rules used by the Analyze Package command.

For more details on the API, refer to the plugin tutorial.


5. Package Dependencies show as hyperlinks

Now in the package metadata panel, if a package has a dependency on another package, the dependency will be displayed as a hyperlink. Clicking the hyperlink will open the Package Chooser dialog and automatically search for the dependency package’s ID.


Last edited Aug 30, 2011 at 5:30 PM by dotnetjunky, version 5