Vs command line tools

At the command prompt, use the CD command to change to the Visual Studio installation directory. Then, use CD again to change to the subdirectory that contains the configuration-specific command files. For Visual Studio , use the VC subdirectory. Enter the command for your preferred developer environment. Open the Properties dialog for a developer command prompt shortcut to see the command target used. The architecture-specific batch files set the architecture parameter and call vcvarsall.

You can pass the same options to these batch files as you would pass to vcvarsall. To specify parameters for your own command shortcut, add them to the end of the command in double-quotes. To use an earlier compiler toolset, specify the version number. Use something like this command target in your shortcut:. Adjust the path to reflect your Visual Studio installation directory. CL Use the compiler cl.

Link Use the linker link. When you build on the command line, the F1 command isn't available for instant help.

Instead, you can use a search engine to get information about warnings, errors, and messages. You can also download and use the offline help files. To use the search in docs. You can also use the devenv command to use Visual Studio to build projects and solutions. You don't have to install the full IDE on all your build servers and build pipelines.

You avoid the extra overhead of the IDE. MSBuild runs in containerized build environments, and supports a binary logger. CMake CMake cmake. CMake can configure and control native build tools for its supported platforms, such as MSBuild and Make.

For more information about CMake, see the CMake documentation. Starting in Visual Studio version These articles show how to build apps on the command line, and describe how to customize the command-line build environment. Walkthrough: Compile a C program on the command line Describes how to compile a program written in the C programming language.

NET Framework. Projects and build systems. Skip to main content. This browser is no longer supported. Download Microsoft Edge More info. Contents Exit focus mode.

Is this page helpful? Please rate your experience Yes No. Any additional feedback? Note This article is about how to set up an environment to use the individual compilers, linkers, librarian, and other basic tools. Note Several command-line tools or tool options may require Administrator permission.

Caution The vcvarsall. Note Starting in Visual Studio version The following is an example of the additional parameters used with the PowerShell script command 'Start-Process':. The first '--wait' is used by the Visual Studio Installer, and the second '-Wait' is used by 'Start-Process' to wait for completion. The '-PassThru' parameter is used by 'Start-Process' to use the installer's exit code for its return value.

Download the Visual Studio core editor the most minimal Visual Studio configuration. Only include the English language pack:. Download the. NET desktop and. NET web workloads along with all recommended components. Start an interactive installation of all workloads and components that are available in the Visual Studio Enterprise edition:. Install a second instance of Visual Studio Professional using a nickname on a machine with Visual Studio Community edition already installed, with support for Node.

Using --config to install the workloads and components from a previously saved installation configuration file:. Sometimes, things can go wrong. If your Visual Studio installation fails, see Troubleshoot Visual Studio installation and upgrade issues for step-by-step guidance.

Skip to main content. Also, more complicated tasks may not be possible using a GUI. CLI - Although many command line environments are capable of multitasking , they do not offer the same ease and ability to view multiple things at once on one screen.

GUI - GUI users have windows that enable a user to view, control, manipulate, and toggle through multiple programs and folders at the same time. CLI - Command line users only need to utilize a keyboard to navigate the interface, often resulting in faster performance. GUI - While modern GUIs are fast and efficient, they require a mouse , so you must move your hand from the mouse to the keyboard to type. For many users, taking your hand off the keyboard to move the mouse pointer is slower than using a CLI, which requires only the keyboard.

Bottom line: A command line performs many tasks faster and can be faster at doing certain tasks on a computer. Video, mouse, and other drivers need to be loaded, taking up additional system resources. Bottom line: A computer that's only using a command line interface doesn't require as many system resources as GUI.

CLI - A command line interface mostly requires users to already know scripting commands and syntax , making it difficult for new or novice users to create scripts. GUI - Creating scripts using a GUI has become easier with programming software, which allows users to write the scripts without having to know all the commands and syntax. Bottom line: Scripting in a CLI requires more knowledge of all of the commands required in the script.

However, once these commands are known, it's easier and often faster to create scripts and automate common tasks. CLI - When remotely accessing another computer or device over a network, a user can manipulate the device or its files with a command line interface.

However, you must know the commands to do so, and it's not as easy for new or novice users.