1
Vote

Simplify installing a packge from a local/network location

description

Currently I have jump though a few hoops in installing a package which I have on my machine:
1) Add the folder via the Nuget settings
2) Then search and install this package.
It invlolves multiple clicks.

Why can't we make it a simple enough experience - just browse to the package and install directly similar to browsing to an assembly and adding a reference to it?

The scenario here is that Azure SDK ships a set of Nuget packages for Azure services bundled in the SDK itself. This is to enable them to work when customer is not online. These nUget packages are downloaded in the Azure SDK install folder. But if I have to install them then I have to explicitly add this install folder path first and then install the package from there. I want an experience of just browsing to this Nuget and installing.

NPM package manager has a similar feature.

comments

gblock wrote Feb 22, 2013 at 2:07 AM

I'd recommend we do what npm for node does here
  1. Allow installation of a package from a folder, url or git repo.
  2. Allow dependencies for that package to be pulled down from the main gallery by default
  3. Allow the manifests for individual packages to specify a package dependency as a folder, url or git repo as well in addition to just supplying the package name / version.

dotnetjunky wrote Feb 26, 2013 at 6:12 PM

Good suggestion.