Skip to content
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

Bundle with nuget #34

Closed
letmaik opened this issue Sep 27, 2018 · 2 comments

Comments

Projects
None yet
3 participants
@letmaik
Copy link
Member

commented Sep 27, 2018

When I download git for Windows, then it has built-in support for 2FA for different providers like GitHub or VSTS.

Wouldn't it make sense to include this credential provider directly in the main nuget distribution? This would save projects from including installation instructions in their README files on how to get started with private Azure NuGet feeds. I consider this a problem, especially since this is only required when using the command line or VS Code. Opening a project in Visual Studio works out of the box as it has built-in integration with private Azure NuGet feeds and doesn't require any extra steps.

@infin8x

This comment has been minimized.

Copy link
Collaborator

commented Oct 2, 2018

Because NuGet doesn't have a "distribution" in any sense other than "download this .exe file" from here, we decided with @anangaur and others from the NuGet team not to do any bundling here.

Separately, we are thinking about ways to build this into VS Code and into dotnet (which does have a distribution).

@infin8x infin8x closed this Oct 2, 2018

@rrelyea

This comment has been minimized.

Copy link

commented Oct 2, 2018

Note, as VS 2017 15.9 (or later) and VS Build SKU 2017 15.9 (or later) both install the credprovider, NuGet.exe 4.9 (or later) will be able to find that copy when run on that machine.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.