Note: I am not able to repro this with regular pre-release test packages. But it is noticed consistently in our Web API 5.0 alpha packages. Below is the repro for the same.
1. Copy the package Microsoft.AspNet.WebApi.Tracing.5.0.0-alpha-13xxxx.nupkg from the Asp net web stack myget feed @ http://www.myget.org/F/aspnetwebstacknightly/ to local share "C:\Temp".
2. Add "C:\Temp" and "http://www.myget.org/F/aspnetwebstacknightly/" as package sources.
3. Create a new MVC 4 Web API project and install the package Microsoft.AspNet.WebApi.Tracing from package manager console by chosing the source "C:\Temp".
__Expected:__
The pre-release package Microsoft.AspNet.WebApi.Tracing from "C:\Temp" source should get installed properly after resolving its dependencies from the myget feed ( which is also added as a package source).
__Actual:__
The package installation fails while trying to resolve dependencies.
__Installation of the package works fine when we directly try to install it from the myget feed. Looks like NuGet is not resolving pre-release dependencies present in a different source ?__
This is really blocking our nightly BVT verification of packages ( where we copy the relevant package to test machine and resolve the dependencies from our nightly drop share). It would be great if we can priortize it.