New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

NuGet package not acting as a solution level package #9

Closed
lholman opened this Issue Nov 25, 2014 · 1 comment

Comments

Projects
None yet
1 participant
@lholman
Owner

lholman commented Nov 25, 2014

No description provided.

@lholman

This comment has been minimized.

Show comment
Hide comment
@lholman

lholman Dec 12, 2014

Owner

Tested with Visual Studio 2012 (11.0.61030.00 Update 4) and NuGet Package Manager 2.8.50926.602

So, it turns out this is an inconsistency with NuGet when a solution level package has dependencies on other solution level NuGet packages, explained here in more detail: https://nuget.codeplex.com/workitem/3487

NuGet Package Manager happily does the following, installing OneBuild and its dependencies (all solution level packages themselves) nicely in to the solution:

image

When you right-click your solution and select 'Manage NuGet Packages' (i.e. using the Visual Studio Extension) you see a 'Manage' button rather than the expected 'Uninstall' you get with a solution level package:

image

Furthermore, if you attempt to install OneBuild via the Visual Studio Extension you get prompted for which project to install it to:

image

Summary
It's safe to install OneBuild via either of the above but personally I'd stick with Install-Package OneBuild within the Package Manager Console and be done with it.

Owner

lholman commented Dec 12, 2014

Tested with Visual Studio 2012 (11.0.61030.00 Update 4) and NuGet Package Manager 2.8.50926.602

So, it turns out this is an inconsistency with NuGet when a solution level package has dependencies on other solution level NuGet packages, explained here in more detail: https://nuget.codeplex.com/workitem/3487

NuGet Package Manager happily does the following, installing OneBuild and its dependencies (all solution level packages themselves) nicely in to the solution:

image

When you right-click your solution and select 'Manage NuGet Packages' (i.e. using the Visual Studio Extension) you see a 'Manage' button rather than the expected 'Uninstall' you get with a solution level package:

image

Furthermore, if you attempt to install OneBuild via the Visual Studio Extension you get prompted for which project to install it to:

image

Summary
It's safe to install OneBuild via either of the above but personally I'd stick with Install-Package OneBuild within the Package Manager Console and be done with it.

@lholman lholman closed this Dec 12, 2014

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment