When i mentioned "vsix package manager" i was referring to the Nuget.Tools.vsix extension that adds the <project> | "Manage Nuget Packages..." UI.
Sounds like in this case i need to incorporate major.minor version details in the .nuspec <id /> element.
One possibly problematic result of the current setup. Lets say i add a nuget package using the gui, say a version 220.127.116.11, and then configure my project to use a "nuget install ..." prebuild event so that on other dev/test wks and tfs build machines
it will automatically pull down the package versus using source control to maintain the binaries. In that case if i come along and publish a 18.104.22.168 then the "nuget install ..." commands are going to pull down the latest 22.214.171.124 drop, even
if i leave the 126.96.36.199 package on the publishing drop site, and as a result the hint path settings in the csproj file will no longer be correct as they contain the version in the path. Is that a known issue or is "nuget install ..." smart
about pulling down the specific package version and not the latest published drop?
Thanks for details on nuget 1.6 -prerelease behavior. Sounds like that addresses allowing vNext release work scenarios to happen without breaking folks bound to currently shipping release.