Local package source on network drive no longer available

Topics: General
Feb 4, 2014 at 9:23 AM
Edited Feb 4, 2014 at 9:24 AM
Not sure what has happened here but my local package source on our network drive is no longer available through Visual Studio 2013.

I had a package source on a network drive (S:\local_nuget) and it seemed to work fine. Now, VS thinks there is nothing in the package library - "no items found", Update library does not work and when I remove and attempt to re-add the File Manager dialog doesn't see any network drives at all (i.e. S: is not available as an option). If I look in "normal" file manager, the S: drive is available and working fine. It's as if NuGet no longer allows network locations for package sources...

If I copy the library to a local drive, everything works fine.

I don't recall updating nuget, but I guess it may have been updated. I'm runnging 2.7.41101.371.

Anybody else experienced anything similar?

Possibly related to https://nuget.codeplex.com/discussions/528593 ?