We have both an internal TeamCity NuGet feed, and an additional Visual Studio Online feed set up via the new Packages functionality in VSO.
We're able to consume packages from TC's feed just fine, but TC fails to find the correct versions of packages stored in the VSO feed at the Package Dependency Satisfaction step in our build. The error is the same for each VSO package - Unable to find version X.X.X of package Y, when the version specified definitely exists in the VSO feed, and can be consumed correctly on local builds.
I've configured credentials via a build feature, and I believe these are working correctly, since before I did so I was getting authentication issues which I'm not seeing any more in the build logs.
If I use package manager console, and issue a get-package -ListAvailable against the VSO source with an appropriate filter, it correctly returns the version in question.
I've also (against my better judgement!) added feed details to NuGet.config and checked in as part of the build, but this doesn't seem to have helped.
Anyone seen anything similar? Is there a step / setting I need to configure to consume from VSO?
An alternative would be to push the VSO packages directly into TC as .nupkgs, but everything I've read seems to indicate that this isn't possible via the .svc that's exposed - can anyone confirm if this is possible, and if so point me to some appropriate docs - my google-fu is not so strong on this one :)