Using Custom NuGet package source with defaults

Topics: General
Mar 13, 2015 at 9:46 PM
In VS2013, I can point to a custom NuGet package source.

Just in case though, if I am missing something, I'd still like for Nuget to be able to go out to the internet to find what it needs.

I can order which package sources are searched first, but I want to make sure that if I do select the checkboxes for the internet based NuGet package source locations, that NuGet doesn't just automatically go out there and look anyway.

In other words, if it finds what it is looking for in the custom package source location, it looks no further.

Is this the way NuGet works with the VS2013 settings?