1. Create a package say DependencyPack version 1.0 and put it in NuGet official source.
2. Now create version 2.0 of DependencyPack and put it in local UNC share.
3. Now create a package testpack version 1.0 which depends on DependencyPack version 1.0 in the same UNC share.
4. Add the UNC share as a package source and try to install testpack
__Expected:__
During installation of test pack, version 1.0 of "DependencyPack" will be picked.
__Actual:__
Version 2.0 of dependencyPack is being installed instead of 1.0.
NuGet should auto-update only minor package versions during install. It should not update the major package versions.
__This happens only when the latter version is present in the UNC share and the older version is present in official source .__ If both 1.0 and 2.0 are present in official source or when both are present in the UNC share, the dependency is resolved to 1.0 properly.
Not a mainline scenario for a typical package consumer. But this scenario might be hit by an organization/package authors who produces package [ say version 10 of package is out and they are trying to test install/upgrade scenarios for version 2.0 before pushing it to the feed]
