Updating a package removes developmentDependency attribute from packages.config #1263

Closed
daveaglick opened this Issue Aug 26, 2015 · 2 comments

Projects

None yet

4 participants

@daveaglick

It seems to reason that if a package is a development dependency before updating, it should remain one after a package update. Steps to reproduce:

  • Create a new console project
  • Run Install-Package boostrap -version 3.3.4 from the Package Manager Console
  • Open packages.config and add developmentDependency="true" for both the bootstrap package and jQuery package (which is installed as a dependency of boostrap)
  • Open the Package Management GUI for the project
  • Update the bootstrap package to 3.3.5 using default behavior
  • Go back to packages.config and notice that developmentDependency="true" is no longer on the bootstrap package (though it's still on the jQuery package, probably because it wasn't updated)
@emgarten
Contributor

This is related to #1130

@emgarten emgarten added this to the 3.2 milestone Aug 28, 2015
@emgarten emgarten self-assigned this Aug 28, 2015
@emgarten
Contributor

Visual Studio 2013 persisted the developmentDependency property, I've fixed NuGet 3.2.0 to persist this also.

NuGetArchive/NuGet3@945d8b6

@emgarten emgarten closed this Aug 28, 2015
@emgarten emgarten was unassigned by yishaigalatzer Sep 1, 2015
@MeniZalzman MeniZalzman added 3 - Done and removed 2 - Working labels Sep 1, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment