15
Vote

add "Manage NuGet Packages..." context menu to windows azure projects

description

My windows azure project context menu doesn’t have the “Manage NuGet Packages...” option.

In the case of federated identity security there are a bunch of web role web.config settings that you want to pull from azure ServiceConfiguration.cscfg when that web role is hotsted in azure's compute emulator or cloud deployment environment versus your localhost dev/test wks iis hosting environment. Enabling nuget package support for azure projects could allow one to add those settings to the ServiceDefinition.csdef and ServiceConfiguration.cscfg as well as build configuration transform versions [ ServiceConfiguration.$(Configuration).cscfg ] taht are in place for test, uat/ppe and release/prd deployment cases.

If possible it would be good that NuGet package functionality in the case of windows azure projects is limited to just ServiceDefinition.csdef, ServiceConfiguration.cscfg and ServiceConfiguration.$(Configuration).cscfg modifications since a package including dll's wouldn't make sense in the case of a windows azure project.

comments

Haacked wrote Aug 1, 2011 at 9:53 PM

We need to investigate the target framework for such project types so we can make sure that NuGet packages can properly target such a framework and that we can filter it properly.

robertob wrote Jan 11, 2013 at 11:19 PM

Looks like this issue changed to from proposed to fixed today. Does that mean the vNext nuget package manager extension story will cover azure projects [ ccproj ] cases as well?

dotnetjunky wrote Jan 11, 2013 at 11:53 PM

yes :)

robertob wrote Jan 12, 2013 at 12:51 AM

excellent, keep up the great work folks!

deepakverma wrote Feb 21, 2013 at 9:19 PM

This is a good fix to support Azure project, but would be confusing for a novice user.
  1. there are two package option in the context menu of this project
    a. package (which actually packages the project for deployment)
    b. manage NuGet package
    probably package should be renamed to package for deployment. Otherwise there are chances a user might think it would create a NuGet package.
  2. when package manager dialog is launched it shows all the packages which makes it feel that any of the package can be installed here. But that's not the case, as also commented by @robertob in the original repro
"it would be good that NuGet package functionality in the case of windows azure projects is limited to just ServiceDefinition.csdef, ServiceConfiguration.cscfg and ServiceConfiguration.$(Configuration).cscfg"

deepakverma wrote Feb 22, 2013 at 6:22 PM

For #1 will open an issue on Azure tooling team.
Verified that NuGet package manager option now shows up for Azure project as well.

** Closed by deepakverma 02/22/2013 11:22AM

deepakverma wrote Jun 30, 2013 at 8:13 PM

this fix was reverted for now as cloud project doesn't allow to add packages.config (or any other file) to the project.

deepakverma wrote Jun 30, 2013 at 8:15 PM

Reactivating, if cloud project adds support and this can be implemented in a future release.