Visual Studio BuildTools 2017 is the command-line-only edition of Microsoft's compiler toolchain. Visual Studio BuildTools 2017 supplies MSBuild, the Visual C++ compiler, and Windows SDK components so build servers can compile code without the full IDE.
Visual Studio BuildTools 2017 is the command-line edition of the Microsoft toolchain that ships with Visual Studio 2017. Instead of the full IDE, it installs MSBuild, the Visual C++ compilers and libraries, .NET build targets, and the Windows SDK so source code can be compiled on a machine where nobody needs a graphical editor. The workflow is simple: run the installer, choose the workloads and components you need, then call MSBuild from a command prompt, a script, or a pipeline. Visual Studio BuildTools 2017 keeps build agents lean, reproducible, and free of unnecessary IDE weight.
Component selection is granular: you can add C++ desktop workloads, C++/CLI support, .NET Framework targeting packs, or Node.js build tools depending on what a repository actually builds. Visual Studio BuildTools 2017 can also install older toolset versions beside the current one, which matters where a single build server compiles solutions spanning several compiler generations. Shipped applications may still need the Microsoft Visual C++ 2015 UWP Desktop Runtime Package on end-user machines, so confirm which redistributables your binaries depend on before retiring an older build environment. Teams running Visual Studio BuildTools 2017 alongside a newer IDE usually keep the two toolchains separate for exactly that reason.
The clearest benefit is resource efficiency. A build agent running only the compiler and MSBuild needs far less disk space and memory than one carrying the complete IDE, so virtual machines boot faster and images stay smaller. Automating those agents is simpler as well, because Visual Studio BuildTools 2017 supports quiet, scripted, component-scoped deployments that fit naturally into configuration management. Builds become predictable when every agent installs the same component set instead of whatever happened to be on a developer's laptop, which cuts down the classic works-on-my-machine class of failures. Visual Studio BuildTools 2017 is serviced through the same update channel as the IDE, so security and reliability fixes arrive without you maintaining a toolchain of your own. Keeping the toolchain separate from the editor also lets developers upgrade their IDE on one schedule while continuous integration stays on another.
Key capabilities and highlights.
Build C++, C++/CLI, and managed projects directly from a developer command prompt, a PowerShell session, or a batch script. Compilation fits into automation you already run, so a headless server can produce the same binaries as a workstation without anyone opening a graphical editor or loading a solution file by hand.
The full MSBuild engine ships with Visual Studio BuildTools 2017, so solution and project files behave exactly as they do inside the integrated development environment. Existing targets, custom build steps, and property sheets usually work unchanged, letting a team move a mature repository onto a dedicated build machine without rewriting its build logic.
The Visual Studio BuildTools 2017 installer lets you pick individual workloads and components rather than accepting one fixed bundle. A build server therefore carries only the SDKs, libraries, and targeting packs your code actually needs, which keeps agent images smaller, narrows the attack surface, and makes provisioning faster on virtual machines that are recreated often.
Windows SDK headers, import libraries, and selected diagnostic utilities can be added alongside the compilers. You get what is needed to compile against platform APIs, consume Windows metadata, and investigate a failing build with the same low-level tooling that ships with the full development environment, all from a single installer pass.
Older compiler toolsets can be installed beside the current one, so Visual Studio BuildTools 2017 lets a single agent build legacy maintenance branches and active development from the same pipeline. That removes the usual need to keep several build machines alive purely to service long-lived release lines that cannot move to a newer compiler yet.
Setup accepts command-line parameters and response files, so provisioning a new build agent becomes a repeatable step inside your infrastructure tooling instead of a manual click-through. The same invocation replays on every scaling event, which keeps a fleet of agents identical and makes the whole environment easier to rebuild after a failure.
Beyond C++, the Build Tools can add .NET Framework targeting packs and Node.js build dependencies to the same installation. Repositories that mix native libraries, managed assemblies, and a JavaScript front end compile on one machine, which simplifies pipeline topology and reduces the number of agents you maintain.
Because every part of the toolchain is driven from the command line, it drops into Jenkins, Azure Pipelines, TeamCity, or a plain scheduled script without a custom bridge plugin. Pipeline definitions stay portable, and moving a job between hosted and self-managed runners usually needs only a change to the agent installation step.
Browse historical releases and previous builds.
Common questions about Visual Studio BuildTools 2017.
Visual Studio BuildTools 2017 is used to compile and package software without the full Visual Studio IDE. It provides MSBuild, the Visual C++ compilers and libraries, and other build components driven entirely from the command line, which is why build servers rely on it.
No. The Build Tools are a standalone installation for machines that only need to compile code. Installing the full IDE on the same machine is possible but optional, and most teams deliberately avoid it on servers to keep images small.
Yes. Because it uses the same MSBuild engine and compiler toolset family as the corresponding IDE generation, existing solution and project files generally build without changes. Unusual extensions or editor-only features may need attention, but ordinary C++ and .NET projects transfer cleanly.
Yes, and that is its primary use case. Its command-line tooling and scriptable setup make it straightforward to provision identical build agents that compile code on every commit, run tests, and publish artifacts without interactive input from an engineer.
Yes. The installer allows older toolsets to be added alongside the current one, so projects pinned to an earlier compiler generation can still be built from the same agent. That helps teams supporting long-lived release branches alongside new development.
Windows SDK components are available as selectable items in the installer. Whether they are installed depends on the components you choose, so select the SDK options if your code compiles against platform APIs or consumes Windows metadata.
The full IDE adds editors, designers, interface debuggers, and profiling front ends. Visual Studio BuildTools 2017 focuses on what is needed to compile and package code, which keeps the footprint smaller and leaves out tools a build server never uses.
That depends on which runtime libraries your binaries link against. Confirm the redistributable runtimes your target machines require and deploy them alongside the application, since an end-user computer will not have the build toolchain installed.
Visual Studio BuildTools 2017 is the command-line-only edition of Microsoft's compiler toolchain. Visual Studio BuildTools 2017 supplies MSBuild, the Visual C++ compiler, and Windows SDK components so build servers can compile code without the full IDE.
Microsoft.Azure.ArtifactSigningClientTools is the Windows package that installs the Artifact Signing client plugin, letting SignTool sign code and artifacts through Azure without a local certificate.
Microsoft .NET SDK 9.0 provides compilers, command-line tools, project templates, build infrastructure, and runtimes for creating, testing, publishing, and running compatible .NET applications.
Microsoft .NET SDK 8.0 provides compilers, command-line tools, project templates, build infrastructure, and runtimes for creating, testing, publishing, and running compatible .NET applications.
Microsoft Edge Dev is a preview web browser for testing upcoming Edge capabilities, inspecting websites with built-in developer tools, and evaluating browser changes before they reach stable releases.
Comments