Hi All, wanted to get your input on an issue I opened.
655 NuGet VSIX should put NuGet.exe on the Machine.
Before we get into implementation details (as the title of the issue does, but I'll change that), let's talk about the high level goal.
- We want to streamline the process for creating and uploading packages.
- We want to close the gap between users/creators.
Dropping NuGet.exe on the machine via VSIX
Basic idea here is to simply have the VSIX deliver NuGet.exe.
Pros: Ubiquity: Everyone who users NuGet needs to run the VSIX. Even content creators will want to install the VSIX so they can test their creations.
Cons: It'll be inside %userprofile%\appdata\local\blah\blah\blah and we can't create a shortcut to it.
NuGet Package Author SDK
The idea here is to have an MSI (available via VS Extension Manager) that "installs" NuGet.exe into the machine's Path
Pros: nuget.exe command works from anywhere.
NuGet.exe available as a NuGet package
Pros: It's already a package. Problem solved.
Cons: It's not added to your path so if you want to run it from a command line, you need to go do that.