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

If package source list is empty, cannot add package source via UI (NuGet 3.4.x) #2617

Closed
vortexau opened this Issue Apr 20, 2016 · 12 comments

Comments

Projects
None yet
5 participants
@vortexau

vortexau commented Apr 20, 2016

When trying to add Package Sources, access the config via Options -> Package Sources. Enter a 'Name' and 'Source' (valid details to try and install Moq), but then when I select 'Add' the item is added as 'Package source' with a URL of 'http://packagesource' and the fields updated to be those same values.

Apologies, I'm not sure of the version (unsure how to find that) - however I'm running VS 2015 Enterprise 14.0.25123.

moq_pre_add

moq_not_added

@rrelyea rrelyea changed the title from Can't add new Package Sources to If package source list is empty, cannot add package source via UI (NuGet 3.4.x) Apr 20, 2016

@rrelyea

This comment has been minimized.

Show comment
Hide comment
@rrelyea

rrelyea Apr 20, 2016

Contributor

Workaround: manually add a source in the nuget.config located: %appdata%\Roaming\NuGet\NuGet.Config

Contributor

rrelyea commented Apr 20, 2016

Workaround: manually add a source in the nuget.config located: %appdata%\Roaming\NuGet\NuGet.Config

@yishaigalatzer

This comment has been minimized.

Show comment
Hide comment
@yishaigalatzer

yishaigalatzer Apr 21, 2016

Thanks for the report. This issue is fixed in 3.5 Beta, keeping it without a milestone because we might port it and release it earlier, still debating

yishaigalatzer commented Apr 21, 2016

Thanks for the report. This issue is fixed in 3.5 Beta, keeping it without a milestone because we might port it and release it earlier, still debating

@rrelyea rrelyea added the Type:Bug label Apr 25, 2016

@rrelyea rrelyea added this to the 3.4.4 milestone Apr 25, 2016

@rrelyea rrelyea modified the milestones: 3.4.4, 3.4.5 Apr 25, 2016

@rrelyea rrelyea added the Priority:1 label May 16, 2016

@rrelyea

This comment has been minimized.

Show comment
Hide comment
@rrelyea

rrelyea Jun 3, 2016

Contributor

@zhili1208 - can you please port this change to 3.4.5 today?

Contributor

rrelyea commented Jun 3, 2016

@zhili1208 - can you please port this change to 3.4.5 today?

@zhili1208

This comment has been minimized.

Show comment
Hide comment
@zhili1208

zhili1208 Jun 3, 2016

Collaborator

NuGet/NuGet.Client@a937261 ported this change to 3.4.5

Collaborator

zhili1208 commented Jun 3, 2016

NuGet/NuGet.Client@a937261 ported this change to 3.4.5

@zhili1208 zhili1208 closed this Jun 3, 2016

@zhili1208 zhili1208 modified the milestones: 3.5 Beta2, 3.4.5 Jun 22, 2016

@duaneking

This comment has been minimized.

Show comment
Hide comment
@duaneking

duaneking Nov 7, 2016

Just got hit by this in the newest version, fix this please!

duaneking commented Nov 7, 2016

Just got hit by this in the newest version, fix this please!

@rrelyea

This comment has been minimized.

Show comment
Hide comment
@rrelyea

rrelyea Nov 7, 2016

Contributor

"newest version"?
think we fixed this problem in 3.5.0 for vs2015, which is posted at http://nuget.org/downloads

Contributor

rrelyea commented Nov 7, 2016

"newest version"?
think we fixed this problem in 3.5.0 for vs2015, which is posted at http://nuget.org/downloads

@duaneking

This comment has been minimized.

Show comment
Hide comment
@duaneking

duaneking Nov 7, 2016

I'm using Visual Studio 2015 Enterprise Edition, using the newest version of the app plugin based on the output from the extension and update manager, and this issue still exists as of the version 3.4.4.1321 that the manager says is installed.

duaneking commented Nov 7, 2016

I'm using Visual Studio 2015 Enterprise Edition, using the newest version of the app plugin based on the output from the extension and update manager, and this issue still exists as of the version 3.4.4.1321 that the manager says is installed.

@rrelyea

This comment has been minimized.

Show comment
Hide comment
@rrelyea

rrelyea Nov 7, 2016

Contributor

Yes, 3.5.0 is not an auto-update. Please update to 3.5.0 via the URL I gave you above. It should fix your issue.

Contributor

rrelyea commented Nov 7, 2016

Yes, 3.5.0 is not an auto-update. Please update to 3.5.0 via the URL I gave you above. It should fix your issue.

@duaneking

This comment has been minimized.

Show comment
Hide comment
@duaneking

duaneking Nov 7, 2016

Given that some corporate IT environments do not allow anything short of an auto update, may I ask when this will be made one?

duaneking commented Nov 7, 2016

Given that some corporate IT environments do not allow anything short of an auto update, may I ask when this will be made one?

@rrelyea

This comment has been minimized.

Show comment
Hide comment
@rrelyea

rrelyea Nov 7, 2016

Contributor

We are being conservative and making sure we give this some time in the market place before turning on auto-update...just to make sure we get some extra validation time.
This is primarily because updates to NuGet without corresponding test runs on VS 2015 as part of major updates have extra risk.
We'd love your feedback on the policy.

We do believe this is a very good update and would love to hear your feedback.

Contributor

rrelyea commented Nov 7, 2016

We are being conservative and making sure we give this some time in the market place before turning on auto-update...just to make sure we get some extra validation time.
This is primarily because updates to NuGet without corresponding test runs on VS 2015 as part of major updates have extra risk.
We'd love your feedback on the policy.

We do believe this is a very good update and would love to hear your feedback.

@duaneking

This comment has been minimized.

Show comment
Hide comment
@duaneking

duaneking Nov 7, 2016

My friendly advice: Just add more unit testing and TDD based code coverage for the UI, possibly use BDD for NuGet since its so critical to so many developers and companies.

duaneking commented Nov 7, 2016

My friendly advice: Just add more unit testing and TDD based code coverage for the UI, possibly use BDD for NuGet since its so critical to so many developers and companies.

@yishaigalatzer

This comment has been minimized.

Show comment
Hide comment
@yishaigalatzer

yishaigalatzer Nov 7, 2016

You would think we know that already :).

This is not a nuget team call, but an all up visual studio platform decision. Nothing else is allowed to auto update at this point.

You can opt in to auto updates by using our beta channel (see the blog).

yishaigalatzer commented Nov 7, 2016

You would think we know that already :).

This is not a nuget team call, but an all up visual studio platform decision. Nothing else is allowed to auto update at this point.

You can opt in to auto updates by using our beta channel (see the blog).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment