-->

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).

Command Line Developer Tools Mac Other command line tools (example: mkvinfo) To use all the other command line tools in Windows®, open a Command Prompt window. Just hit the ' Start ' button, click on ' Search programs and files ' (Windows® 7 and Vista) or ' Run ' (Windows® XP and others) and type either ' cmd ' or ' command prompt ' (without. Oct 31, 2019 If you do not already have the oc command line tool, you can download the version corresponding to the OpenShift cluster you are using, from the Command Line Tools option under the help menu. Xcode-select: error: command line tools are already installed, use “Software Update” to install updates. This means you'll need to go to the developer website instead. Installing the CLT. When the.dmg has finished downloaded, double click the file to open it. This will open a little window that looks like this.

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 dotnet CLI 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.exe CLI. If the project is migrated from packages.config to 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.

1. 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.
2. Each download is the nuget.exe file 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.
3. Add the folder where you placed nuget.exe to your PATH environment variable to use the CLI tool from anywhere.

macOS/Linux

Behaviors may vary slightly by OS distribution.

1. Install Mono 4.4.2 or later.

2. Execute the following command at a shell prompt:

3. Create an alias by adding the following script to the appropriate file for your OS (typically ~/.bash_aliases or ~/.bash_profile):

4. Reload the shell. Test the installation by entering nuget with 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

Download Command Line Tools Mac

(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.

The Android SDK is composed of multiple packages that are required for app development.This page lists the most important command line tools that areavailable, organized by the packages in which they're delivered.

You can install and update each package usingAndroid Studio's SDK Manageror the sdkmanagercommand line tool.All of the packages are downloaded into your Android SDK directory, whichyou can locate as follows:

1. In Android Studio, click File > Project Structure.
2. Select SDK Location in the left pane. The path is shown under Android SDK location.

Android SDK Command-Line Tools

Located in: android_sdk/cmdline-tools/version/bin/

Note: For information about the deprecated SDK Tools package, see the SDK Tools release notes.

If you just need these tools because you're not using Android Studio, you candownload the command-line tools package here.

apkanalyzer

Provides insight into the composition of your APK after the build process completes.

avdmanager

Allows you to create and manage Android Virtual Devices (AVDs) from the command line.

lint

A code scanning tool that can help you to identify and correct problems with the structural quality of your code.

retrace

For applications compiled by R8, retrace decodes an obfuscated stack trace that maps back to your original source code.

sdkmanager

Allows you to view, install, update, and uninstall packages for the Android SDK.

Android SDK Build Tools

Command Line Tool Windows

Located in: android_sdk/build-tools/version/
See also: SDK Build Tools release notes

This package is required to build Android apps. Most of the tools in here areinvoked by the build tools and not intended for you. However, the followingcommand line tools might be useful:

aapt2

Parses, indexes, and compiles Android resources into a binary format that is optimized for the Android platform, and packages the compiled resources into a single output.

apksigner

Signs APKs and checks whether APK signatures will be verified successfully on all platform versions that a given APK supports.

zipalign

Optimizes APK files by ensuring that all uncompressed data starts with a particular alignment relative to the start of the file.

Note: You can have multiple versions of the build toolsto build your app for different Android versions.

Android SDK Platform Tools

Os X Command Line Tools

Located in: android_sdk/platform-tools/
See also: SDK Platform Tools release notes

These tools are updated for every new version of the Android platform to support new features(and sometimes more often to fix or improve the tools), and each updateis backward compatible with older platform versions.

In addition to downloading from the SDK Manager, you candownload the SDK Platform Tools here.

adb

Android Debug Bridge (adb) is a versatile tool that lets you manage the state of an emulator instance or Android-powered device. You can also use it to install an APK on a device.

etc1tool

A command line utility that lets you encode PNG images to the ETC1 compression standard and decode ETC1 compressed images back to PNG.

fastboot

Flashes a device with platform and other system images. For flashing instructions, see Factory Images for Nexus and Pixel Devices.

logcat

This is a tool invoked via adb to view app and system logs.

Android Emulator

Java Command Line Tool Mac Download

Located in: android_sdk/emulator/
See also: Android Emulator release notes

This package is required to use the Android Emulator. It includes the following:.

emulator

A QEMU-based device-emulation tool that you can use to debug and test your applications in an actual Android run-time environment.

mksdcard

Helps you create a disk image that you can use with the emulator, to simulate the presence of an external storage card (such as an SD card).

Note: Prior to revision 25.3.0, the emulator tools were included with theSDK Tools package.

Jetifier

Command Line Tools Download For Mac

Jetifier reads a library that usesSupport Library classes, and outputs an equivalent library that uses the newerAndroidX classes.