I'm using Visual Studo 2015 and I have Package Manager Console where I can run like
PM> Install-Package Newtonsoft.Json
Visual Studio seems to come with nuget, but what is the location of nuget.exe?
Or Package Manager Console doesn't use nuget.exe?
Visual Studio 2015 uses various NuGet assemblies but it does not itself include NuGet.exe.
NuGet.exe can be downloaded from the NuGet web site:
https://www.nuget.org/downloads
Another great option nowadays is to use winget (if you have Windows 10 v1709 or greater). In the Command Prompt, enter:
winget install Microsoft.NuGet
(below follows some extra information for the curious mind) This will:
Install the official nuget.exe in your PC.
Create a Symbolic Link here: %localappdata%\microsoft\winget\links
Make the nuget.exe globally available for your user to call it from anywhere, since the aforementioned directory should be present in your user's PATH variable.
I am attempting to setup a NuGet package source that requires credentials.
Here are the instructions
I have the latest version of Visual Studio 2015 with everything up to date. I am aware of how to add a package source through the UI in VS2015, but you can't specify credentials when doing it this way.
The command they are asking me to run is:
NuGet Sources Add -Name "telerik.com" -Source "https://nuget.telerik.com/nuget" -UserName "<your login email>" -Password "<your password>"
I am aware that I need a nuget.exe to run this command, but there is a way to do this directly through VS without downloading anything isn't there?
If I download the NuGet.exe, open a command prompt and navigate to it to run that command will I then be able to see it from Visual Studio's NuGet Package Manager UI and access it from Visual Studio's NuGet Package Manager Console? I am confused on how it will integrate with Visual Studio's built in NuGet Package Manager.
I figured out that you need to download nuget.exe to your computer, open up a command prompt and navigate to it. Then run the command to add the package source with credentials:
NuGet Sources Add -Name "telerik.com" -Source "https://nuget.telerik.com/nuget" -UserName "<your login email>" -Password "<your password>"
Restart Visual Studio and the Package Source is added to the list in both the Nuget UI and Nuget Command Line.
If you are using SSO and the Windows credentials fix does not work for you, just sign out of Visual Studio, then sign back in again, and then restart Visual Studio; then, the 401 NuGet package source error will be fixed.
We can update the file Nuget.config file entry as
<add key="Telerik" value="https://nuget.telerik.com/nuget"
UserName ="<<youremail#mail.com>>"
Password ="<<password>>" />
This let me build and run.
I tried the approche Blake Rivell described in his answer. It did not work for me, so I tried to use the -StorePasswordInClearText flag. (See the instruction mentioned in the question)
Then I found out the project I started working on contained a "NuGet.Config" file. The display name of the source in this file was different to the one I added via the command line (to the global "NuGet.Config" file). (Our different projects apparently use different names for it)
So it did not work, because it was not able to associate the source with credentials with the entry in my local "NuGet.Config" file.
I updated to VS2015 this week and along with that updated all NuGet packages in my website solution.
The site builds and run fine locally, however when doing my gated check in to my build server, I get the following when the build fails
As you can see the packages are complaining about the NuGet version, but I'm unsure how to update the NuGet version on the build server. I do have admin privileges to the server, but following the guild described at: http://blog.stangroome.com/2014/02/04/update-nuget-exe-version-used-by-team-build-2013-package-restore/ did not help. For one, my folder was actually C:\Program Files\Microsoft Team Foundation Server 11.0\Tools unlike the C:\Program Files\Microsoft Team Foundation Server 12.0\Tools described in the guide, but additionally I did not have a NuGet.exe within the folder.
I've done a full hard drive search of NuGet.exe, but could not locate it in any directories aside from the directories that are directly related to project source code (.nuget\NuGet.exe).
I have opened visual studio on the server and updated the NuGet version within "Extension and Updates" hoping that would fix the issue, unfortunately it did not.
Any ideas on how to fix the issue/errors presented in the screenshot?
The problem is that you're using the old-style, deprecated-since-NuGet 2.7-style "package restore" that's based on modifying your CSProj files to include references to a NuGet.targets file and a copy of NuGet.exe that gets put into a .nuget folder and ends up source controlled.
Basically, the version of nuget.exe that's on the build server is irrelevant right now -- your CSProj files are pointing to the file in your .nuget folder.
TFS 2013 and beyond has support for automatic package restore without using the NuGet.targets method. You can migrate off of it pretty easily: https://docs.nuget.org/consume/package-restore/migrating-to-automatic-package-restore
After a check in from Visual Studio 2013 I am getting the following 2 build errors:
C:\a\src\project.nuget\nuget.targets (58): The process cannot access the file 'C:\Users\buildguest\AppData\Roaming\NuGet\NuGet.Config' because it is being used by another process.
C:\a\src\project.nuget\nuget.targets (58): The command ""C:\a\src\project.nuget\nuget.exe" install "C:\a\src\project\WebWorkerRole\packages.config" -source "" -o "C:\a\src\project\packages"" exited with code 1.
Do you have enabled NuGet Package Restore in your solution? This adds nuget.exe and nuget.config into your solution and build can use it locally. To enable NuGet Package Restore right click on the Solution node in Solution Explorer and select Enable NuGet Package Restore (see NuGet documentation).
I am trying to create a nuget package using http://docs.nuget.org/docs/creating-packages/creating-and-publishing-a-package#From_a_convention_based_working_directory
as a reference.
My Package Manger Console in Visual Studio is not allowing me to use the 'nuget' command.
I am able to 'Get-help nuguet' and it displays:
The following NuGet cmdlets are included.
Cmdlet Description
------------------ ----------------------------------------------
Get-Package Gets the set of packages available from the package source.
Install-Package Installs a package and its dependencies into the project.
Uninstall-Package Uninstalls a package. If other packages depend on this package,
the command will fail unless the –Force option is specified.
Update-Package Updates a package and its dependencies to a newer version.
Add-BindingRedirect Examines all assemblies within the output path for a project
and adds binding redirects to the application (or web)
configuration file where necessary.
Get-Project Returns a reference to the DTE (Development Tools Environment)
for the specified project. If none is specifed, returns the
default project selected in the Package Manager Console.
Open-PackagePage Open the browser pointing to ProjectUrl, LicenseUrl or
ReportAbuseUrl of the specified package.
Register-TabExpansion Registers a tab expansion for the parameters of a command.
However, whenever I start off commands with nuget is gives :
The term 'nuget' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try ag
ain.
At line:1 char:6
+ nuget <<<<
+ CategoryInfo : ObjectNotFound: (nuget:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException
I have tried the following solutions:
1>closing down all items and restarting
2> uninstalling and reinstalling
3>creating a powershell profile file (this didn't exist before and this actually broke everything)
The problem started to appear after I upgraded my Visual Studio 2012 Ultimate trial version to registered. I had originally had the VS 12 Pro installed. I don't know if that really has anything to do with it but I noticed that others that had similar problems have vs 10 and 12 installed.
My question is "does anyone know what else to try?" My theory is that the path to the nuget command is missing but I cannot find how to configure the paths the package manager console uses and I am not sure where the cmdlet nuget is actually stored.
Updated---tried downloading the command line tool as suggested below. This lead to nothing working again. I tried to uninstall and now I have a item in vs2010 extentions for nuget that doesn't have a install or unistall button enabled. This leads me to believe that it has to do with extensions installed via 2010 and 2012 that has a part in my little drama. If anyone also knows how to nuke an uninstallable extension, please advise also but I will try another question for that.
Nuget.exe is placed at .nuget folder of your project. It can't be executed directly in Package Manager Console, but is executed by Powershell commands because these commands build custom path for themselves.
My steps to solve are:
Download NuGet.exe from https://github.com/NuGet/NuGet.Client/releases (give preference for the latest release);
Place NuGet.exe in C:\Program Files\NuGet\Visual Studio 2012 (or your VS version);
Add C:\Program Files\NuGet\Visual Studio 2012 (or your VS version) in PATH environment variable (see http://www.itechtalk.com/thread3595.html as a How-to) (instructions here).
Close and open Visual Studio.
Update
NuGet can be easily installed in your project using the following command:
Install-Package NuGet.CommandLine
In [Package Manager Console] try the below
Install-Package NuGet.CommandLine
There are much nicer ways to do it.
Install Nuget.Build package in you project that you want to pack. May need to close and re-open solution after install.
Install nuget via chocolatey - much nicer. Install chocolatey: https://chocolatey.org/, then run
cinst Nuget.CommandLine
in your command prompt. This will install nuget and setup environment paths, so nuget is always available.
You can also try setting the system variable path to the location of your nuget exe and restarting VS.
Open your system PATH variable and add the location of your nuget.exe (for me this is: C:\Program Files (x86)\NuGet\Visual Studio 2013)
Restart Visual Studio
I would have posted this as a comment to your answer #done_merson but I didn't have the required reputation to do that.
In Visual Studio:
Tools -> Nuget Package Manager -> Package Manager Console.
In PM:
Install-Package NuGet.CommandLine
Close Visual Studio and open it again.
The nuget commandline tool does not come with the vsix file, it's a separate download
https://github.com/nuget/home
Right-click on your project in solution explorer.
Select Manage NuGet Packages for Solution.
Search NuGet.CommandLine by Microsoft and Install it.
On complete installation, you will find a folder named packages in
your project. Go to solution explorer and look for it.
Inside packages look for a folder named NuGet.CommandLine.3.5.0, here 3.5.0 is just version name your folder name will change accordingly.
Inside NuGet.CommandLine.3.5.0 look for a folder named tools.
Inside tools you will get your nuget.exe
Retrieve nuget.exe from https://www.nuget.org/downloads. Copy it to a local folder and add that folder to the PATH environment variable.
This is will make nuget available globally, from any project.
I got around this by finding the nuget.exe and moving to an easy to type path (c:\nuget\nuget) and then calling the nuget with this path. This seems to solve the problem.
c:\nuget\nuget at the package manager console works as expected.
I tried to find the path that the console was using and changing the environment path but was never able to get it to work in that way.
Follow these steps.
In visual studio go to Tools-> NuGet Package Manager->Package Manager Console
Run below command
Install-Package NuGet.CommandLine
Close visual studio and reOpen again
repeat step 1
run your nuget command
eg. nuget push C:\Users\syaads\Debug\Library.1.0.32.nupkg -Source Artifactory
You can find the nuget.exe in your profile folder:
C:\Users\YourProfileName\.nuget\packages\nuget.commandline\6.0.0\tools
If you want to use it gloablly, please register above path in PATH environment variable.
For detailed guide how to do it, please see Add to the PATH in Windows 10
Download nuget.exe from https://www.nuget.org/downloads.
create a new folder in root of C drive e.g c:\nuget, copy the nuget.ext to nuget folder in c drive and paste.
Go to environmental settings.
Go to System Variable Section => select the variable name as Path and double click on path variable => and click on new button in the last add c:\nuget => then apply => save => save.
Download the nuget.exe from the https://www.nuget.org/downloads.
Copy and paste the downloaded file to the relevant folder where your .nupkg is created.
Try to execute the command.