The following problem does not exist in VS2013 (Premium),I can only reproduce it in VS2015 (Enterprise)
I\'ve added a custom NuGet package source. If that source if
This is an old question so I'm surprised the workaround from the bug report wasn't added here. To save reader a click:
Once you're back in your office follow steps 1 and 2 again but this time make sure everything is checked.