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:
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:
Furthermore, if you attempt to install OneBuild via the Visual Studio Extension you get prompted for which project to install it to:
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.
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:
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:
Furthermore, if you attempt to install OneBuild via the Visual Studio Extension you get prompted for which project to install it to:
Summary It's safe to install OneBuild via either of the above but personally I'd stick with
Install-Package OneBuildwithin the Package Manager Console and be done with it.