Learn more about BitTitan and our tools. Migration Guides Step-by-step guides, FAQs, and troubleshooting for your migration projects.
-->Looking to install a package? See Ways to install NuGet packages.
To work with NuGet, as a package consumer or creator, you can use command-line interface (CLI) tools as well as NuGet features in Visual Studio. This article briefly outlines the capabilities of the different tools, how to install them, and their comparative feature availability. To get started using NuGet to consume packages, see Install and use a package (dotnet CLI) and Install and use a package (Visual Studio). To get started creating NuGet packages, see Create and publish a NET Standard package (dotnet CLI) and Create and publish a NET Standard package (Visual Studio).
- Device Management Agent Installation; How can I install the Device Management Agent (DMA) on domain-joined computers without admin rights? Install the Device Management Agent on Terminal Servers; Is it possible to silently install the Device Management Agent? Server and Port Configuration for Device Management Agent.
- You can download the Xcode command-line tools in either of two ways: To install the necessary Xcode tools using Xcode on the Mac: Start Xcode on the Mac.
| Tool | Description | Download |
|---|---|---|
| dotnet.exe | CLI tool for .NET Core and .NET Standard libraries, and for any SDK-style project such as one that targets .NET Framework. Included with the .NET Core SDK and provides core NuGet features on all platforms. (Starting in Visual Studio 2017, the dotnet CLI is automatically installed with any .NET Core related workloads.) | .NET Core SDK |
| nuget.exe | CLI tool for .NET Framework libraries and for any non-SDK-style project such as one that targets .NET Standard libraries. Provides all NuGet capabilities on Windows, provides most features on Mac and Linux when running under Mono. | nuget.exe |
| Visual Studio | On Windows, the NuGet Package Manager is included with Visual Studio 2012 and later. Visual Studio provides the Package Manager UI and the Package Manager Console, through which you can run most NuGet operations. | Visual Studio |
| Visual Studio for Mac | On Mac, certain NuGet capabilities are built-in directly. Package Manager Console is not presently available. For other capabilities, use the dotnet.exe or nuget.exe CLI tools. | Visual Studio for Mac |
| Visual Studio Code | On Windows, Mac, or Linux, NuGet capabilities are available through marketplace extensions, or use the dotnet.exe or nuget.exe CLI tools. | Visual Studio Code |
The MSBuild CLI also provides the ability to restore and create packages, which is primarily useful on build servers. MSBuild is not a general-purpose tool for working with NuGet.
Package Manager Console commands work only within Visual Studio on Windows and do not work within other PowerShell environments.
Visual Studio
Install on Visual Studio 2017 and newer
Starting in Visual Studio 2017, the installer includes the NuGet Package Manager with any workload that employs .NET. To install separately, or to verify that the Package Manager is installed, run the Visual Studio installer and check the option under Individual Components > Code tools > NuGet package manager.
Install on Visual Studio 2015 and older
NuGet Extensions for Visual Studio 2013 and 2015 can be downloaded from https://dist.nuget.org/index.html.
For Visual Studio 2010 and earlier, install the 'NuGet Package Manager for Visual Studio' extension. Note, if you can't see the extension in the first page of search results, try changing the Sort By dropdown to 'Most Downloads', or an alphabetical sort.
CLI tools
You can use either the dotnet CLI or the nuget.exe CLI to support NuGet features in the IDE. The dotnet CLI is installed with some Visual Studio workloads, such as .NET Core. The nuget.exe CLI must be installed separately as described earlier.
The two NuGet CLI tools are dotnet.exe and nuget.exe. See feature availability for a comparison.
- To target .NET Core or .NET Standard, use the dotnet CLI. The
dotnetCLI is required for the SDK-style project format, which uses the SDK attribute. - To target .NET Framework (non-SDK-style project only), use the
nuget.exeCLI. If the project is migrated frompackages.configto PackageReference, use the dotnet CLI.
dotnet.exe CLI
The .NET Core 2.0 CLI, dotnet.exe, works on all platforms (Windows, Mac, and Linux) and provides core NuGet features such as installing, restoring, and publishing packages. dotnet provides direct integration with .NET Core project files (such as .csproj), which is helpful in most scenarios. dotnet is also built directly for each platform and does not require you to install Mono.
Installation:
- On developer computers, install the .NET Core SDK. Starting in Visual Studio 2017, the dotnet CLI is automatically installed with any .NET Core related workloads.
- For build servers, follow the instructions on Using .NET Core SDK and tools in Continuous Integration.
To learn how to use basic commands with the dotnet CLI, see Install and use packages using the dotnet CLI.
nuget.exe CLI
The nuget.exe CLI, nuget.exe, is the command-line utility for Windows that provides all NuGet capabilities; it can also be run on Mac OSX and Linux using Mono with some limitations.
To learn how to use basic commands with the nuget.exe CLI, see Install and use packages using the nuget.exe CLI.
Installation:
Windows
Note
NuGet.exe 5.0 and later require .NET Framework 4.7.2 or later to execute.
- Visit nuget.org/downloads and select NuGet 3.3 or higher (2.8.6 is not compatible with Mono). The latest version is always recommended, and 4.1.0+ is required to publish packages to nuget.org.
- Each download is the
nuget.exefile directly. Instruct your browser to save the file to a folder of your choice. The file is not an installer; you won't see anything if you run it directly from the browser. - Add the folder where you placed
nuget.exeto your PATH environment variable to use the CLI tool from anywhere.
macOS/Linux
Behaviors may vary slightly by OS distribution.
Install Mono 4.4.2 or later.
Execute the following command at a shell prompt:
Create an alias by adding the following script to the appropriate file for your OS (typically
~/.bash_aliasesor~/.bash_profile):Reload the shell. Test the installation by entering
nugetwith no parameters. NuGet CLI help should display.
Tip
Use nuget update -self on Windows to update an existing nuget.exe to the latest version.
Note
The latest recommended NuGet CLI is always available at https://dist.nuget.org/win-x86-commandline/latest/nuget.exe. For compatibility purposes with older continuous integration systems, a previous URL, https://nuget.org/nuget.exe currently provides the deprecated 2.8.6 CLI tool.
Feature availability
| Feature | dotnet CLI | nuget CLI (Windows) | nuget CLI (Mono) | Visual Studio (Windows) | Visual Studio for Mac |
|---|---|---|---|---|---|
| Search packages | ✔ | ✔ | ✔ | ✔ | |
| Install/uninstall packages | ✔ | ✔(1) | ✔ | ✔ | ✔ |
| Update packages | ✔ | ✔ | ✔ | ✔ | |
| Restore packages | ✔ | ✔ | ✔(2) | ✔ | ✔ |
| Manage package feeds (sources) | ✔ | ✔ | ✔ | ✔ | |
| Manage packages on a feed | ✔ | ✔ | ✔ | ||
| Set API keys for feeds | ✔ | ✔ | |||
| Create packages(3) | ✔ | ✔ | ✔(4) | ✔ | |
| Publish packages | ✔ | ✔ | ✔ | ✔ | |
| Replicate packages | ✔ | ✔ | |||
| Manage global-package and cache folders | ✔ | ✔ | ✔ | ||
| Manage NuGet configuration | ✔ | ✔ |
(1) Does not affect project files; use dotnet.exe instead.
(2) Works only with packages.config file and not with solution (.sln) files.
(3) Various advanced package features are available through the CLI only as they aren't represented in the Visual Studio UI tools.
(4) Works with .nuspec files but not with project files.
Upcoming Features
If you'd like to preview upcoming NuGet features, install a Visual Studio Preview, which works side-by-side with stable releases of Visual Studio. To report problems or share ideas for previews, open an issue on the NuGet GitHub repository.
Related topics
Developers working on Windows can also explore the NuGet Package Explorer, an open-source, stand-alone tool to visually explore, create, and edit NuGet packages. It's very helpful, for example, to make experimental changes to a package structure without rebuilding the package.
Boot Camp requires a Mac with an Intel processor.
When you install Microsoft Windows on your Mac, Boot Camp Assistant automatically opens the Boot Camp installer, which installs the latest Windows support software (drivers). If that doesn't happen, or you experience any of the following issues while using Windows on your Mac, follow the steps in this article.
- Your Apple mouse, trackpad, or keyboard isn't working in Windows.
Force Touch isn't designed to work in Windows. - You don't hear audio from the built-in speakers of your Mac in Windows.
- The built-in microphone or camera of your Mac isn't recognized in Windows.
- One or more screen resolutions are unavailable for your display in Windows.
- You can't adjust the brightness of your built-in display in Windows.
- You have issues with Bluetooth or Wi-Fi in Windows.
- You get an alert that Apple Software Update has stopped working.
- You get a message that your PC has a driver or service that isn't ready for this version of Windows.
- Your Mac starts up to a black or blue screen after you install Windows.
If your Mac has an AMD video card and is having graphics issues in Windows, you might need to update your AMD graphics drivers instead.
Install the latest macOS updates
Before proceeding, install the latest macOS updates, which can include updates to Boot Camp.
Format a USB flash drive
To install the latest Windows support software, you need a 16GB or larger USB flash drive formatted as MS-DOS (FAT).
- Start your Mac from macOS.
- Plug the USB flash drive into your Mac.
- Open Disk Utility, which is in the Utilities folder of your Applications folder.
- Choose View > Show All Devices from the menu bar.
- From the sidebar in Disk Utility, select your USB flash drive. (Select the drive name, not the volume name beneath it.)
- Click the Erase button or tab.
- Choose MS-DOS (FAT) as the format and Master Boot Record as the scheme.
- Click Erase to format the drive. When done, quit Disk Utility.
Download the Windows support software
After preparing your USB flash drive, complete these steps:
- Make sure that your Mac is connected to the Internet.
- Open Boot Camp Assistant, which is in the Utilities folder of your Applications folder.
- From the menu bar at the top of your screen, choose Action > Download Windows Support Software, then choose your USB flash drive as the save destination. When the download completes, quit Boot Camp Assistant.
Learn what to do if you can't download or save the Windows support software.
Install the Windows support software
After downloading the Windows support software to your flash drive, follow these steps to install the software. (If you're attempting to resolve issues with a Bluetooth mouse or keyboard, it might be easier to use a USB mouse or keyboard until these steps are complete.)
- Make sure that the USB flash drive is plugged into your Mac.
- Start up your Mac in Windows.
- From File Explorer, open the USB flash drive, then open Setup or setup.exe, which is in the WindowsSupport folder or BootCamp folder. When you're asked to allow Boot Camp to make changes to your device, click Yes.
- Click Repair to begin installation. If you get an alert that the software hasn't passed Windows Logo testing, click Continue Anyway.
- After installation completes, click Finish, then click Yes when you're asked to restart your Mac.
Learn more
If you can't download or save the Windows support software:
Bittitan Tool Install For Mac Mojave
- If the assistant says that the Windows support software could not be saved to the selected drive, or that the USB flash drive can't be used, make sure that your USB flash drive has a storage capacity of at least 16GB and is formatted correctly.
- If the assistant doesn't see your USB flash drive, click Go Back and make sure that the drive is connected directly to the USB port on your Mac—not to a display, hub, or keyboard. Disconnect and reconnect the drive, then click Continue.
- If the assistant says that it can't download the software because of a network problem, make sure that your Mac is connected to the Internet.
- Make sure that your Mac meets the system requirements to install Windows using Boot Camp.
Bittitan Ticker
If a Mac feature still doesn't work after updating the Windows support software, search for your symptom on the Apple support website or Microsoft support website. Some features of your Mac aren't designed to work in Windows.