-
Notifications
You must be signed in to change notification settings - Fork 10.3k
Any chance that KVM Setup (or something else) edits Nuget Package Sources? #92
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
I don't think anything does this deliberately. @Praburaj did you ever see this behavior. |
@glennc It is something I have seen before. |
Fwiw, I looked at a screenshot I took 2 days ago of the package manager and nuget.org was there and the mystery aspnetvnext source was not. -----Original Message----- I don't think anything does this deliberately. @Praburaj did you ever see this behavior. Reply to this email directly or view it on GitHub: |
Must be a bug in KVM somewhere. I'll take a look. |
This is a known tooling issue. http://nuget.codeplex.com/workitem/4397 Work around is to add a feed with url |
…t is has been reported to the dotnet corefx team here: dotnet/corefx#8809 The issue won't be resolved in 1.0.0, so @stephentoub recommended that we reuse the HttpClient.
I had some wierd dependency issues that turned out to be because nuget.org was unchecked in my NuGet Package Source settings. I don't recall turning that off and I know that until very recently, I've been getting current packages (for non vnext projects) from NuGet.
At the same time I noticed something else odd. I had added a source for the nightly builds myself. But in addition to nuget.org being unchecked, i noticed that there is now an AspNetVNext source which duplicates the one I created. Here's a screenshot (after I re-checked nuget.org.)

Is there some scenario (kvm install, grabbing repositories from github, etc) that adds that package source and might also have unchecked nuget.org? If so, it's just been in the last few days that this happened on my machine as I've been fiddling with EF7. :)
The text was updated successfully, but these errors were encountered: