Related to http://nuget.codeplex.com/workitem/675
Duped by http://nuget.codeplex.com/workitem/1058
I have a solution with two Class Library projects, each with NuSpec files in there: Project B -> Project A
I want to turn them both into packages.
When I run nuget pack ProjectB.csproj, ideally it would recognize that ProjectB has a project reference to ProjectA which has its own nuspec file and would automatically add a <dependency id="ProjectB" version="{ProjectBVersion}" />.
Right now, I have to manually put the dependency node in ProjectB and remember to keep it in sync with the ProjectA assembly version.
Comments: My workflow is as follows: I have several interdependent projects that again have some nuget dependencies. Some of these are projects that almost never change and some change more often. I choose to ignore any potential version numbering problem (which can happen in any scenario). When building these projects I have want to generate one nuget package for each source project. These nuget packages should then naturally include dependencies to any external nuget packages and also the dependencies that are found implicit via the project references to other projects that also have nuget specs. All my dependencies in this scenario have either an nuget package reference or have their own nuspec file. In these nuget packages are then one single dll library and some dependencies. C(nuspec) -> B(nuspec) -> A(nuget) (external nuget package ala log4net) D(nuspec) -> B(nuspec) -> A(nuget) E(nuspec) -> A(nuget) A is i.e log4net, a nuget package from the nuget gallery B, C, D, E are all inhouse developed libraries published at an inhouse gallery. Developers use these libraries. Now I can modify B and release a new version of package . VisualStudio automatically updates the assembly override for those who choose to use the new version of B. This works very well for us and we have a "hacked" version of nuget in order to generate the packages using the sources I have posted earlier. It would be nice if there was an option for nuget.exe which could then tell it to either auto include project dependencies to projects with nuspec or to just ignore them etc.
Duped by http://nuget.codeplex.com/workitem/1058
I have a solution with two Class Library projects, each with NuSpec files in there: Project B -> Project A
I want to turn them both into packages.
When I run nuget pack ProjectB.csproj, ideally it would recognize that ProjectB has a project reference to ProjectA which has its own nuspec file and would automatically add a <dependency id="ProjectB" version="{ProjectBVersion}" />.
Right now, I have to manually put the dependency node in ProjectB and remember to keep it in sync with the ProjectA assembly version.
Comments: My workflow is as follows: I have several interdependent projects that again have some nuget dependencies. Some of these are projects that almost never change and some change more often. I choose to ignore any potential version numbering problem (which can happen in any scenario). When building these projects I have want to generate one nuget package for each source project. These nuget packages should then naturally include dependencies to any external nuget packages and also the dependencies that are found implicit via the project references to other projects that also have nuget specs. All my dependencies in this scenario have either an nuget package reference or have their own nuspec file. In these nuget packages are then one single dll library and some dependencies. C(nuspec) -> B(nuspec) -> A(nuget) (external nuget package ala log4net) D(nuspec) -> B(nuspec) -> A(nuget) E(nuspec) -> A(nuget) A is i.e log4net, a nuget package from the nuget gallery B, C, D, E are all inhouse developed libraries published at an inhouse gallery. Developers use these libraries. Now I can modify B and release a new version of package . VisualStudio automatically updates the assembly override for those who choose to use the new version of B. This works very well for us and we have a "hacked" version of nuget in order to generate the packages using the sources I have posted earlier. It would be nice if there was an option for nuget.exe which could then tell it to either auto include project dependencies to projects with nuspec or to just ignore them etc.