When you click the c++ build tool in vs_installer UI, you could see that it will install related components automatically. Important note: using command line is quite different from the vs_installer UI. 140 means that VS2015 build tool for C++. If you want to build c++ project, you can try the following example: vs_buildtool_xxx.exe -add ^ add .4.5.2.TargetingPack^Ĭ:\BuildTools\MSBuild\Current\Bin\MSBuild.exe myproject.slnĪnd you can add any more workloads or packages by commamd -add with the related Component ID.
You can try the below script: // This is for desktop development and also add the net framwork 3.5 And the order is the same as the build tool. You can refer to this document to obtain the related Component ID of buildtool.īesides, this document also list the command line installed instructions. NET C#įirst, you should note that, all the workloads or packages need to be installed and they will be integrated into Build Tool, what you need is the workload Component ID of them.
Studio Build Tools build environment, for C++ version X. How to automate (from command-line) the installation of a Visual With this method, even if you open a 6-year old project, you should be able to build it. Or msbuildget -package=.NET-35 -installdir=c:\buildtools\net35Ĭ:\buildtools\net35\bin\msbuild.exe myproject.sln If it was possible, I would just, once for all create a build.bat file for every project, that would be something like: msbuildget -package=VC14 -installdir=c:\buildtools\vc14 # automatically download and installĬ:\buildtools\vc14\bin\msbuild.exe myproject.sln How to install the required MS build tools from command-line? (I don't want to use any IDE, I want to script everything) This might be a solution to avoid this problem: Your computer is now a mess with 5 different versions of SDKs installed at the same time that probably collide with each other (did version Z overwrite/uninstall version Y or not?) Then spend X hours browsing on websites like, install a package, then notice it's not the right one ( msbuild still fails), download another package, install it, etc.Īt the end you have downloaded 8 GB of packages, waited for the download, waited for the install, for the reboot, and you're still not sure it works NET Framework version / the right SDK is missing (example situation here among many others) Oops, I don't have the right Visual Studio version /. I download a project from Github or open an old project of mine (say from 4 years ago) Note: I have already read How can I install the VS2017 version of msbuild on a build server without installing the IDE? but this does not answer with a totally GUI-less script-only install.
0 kommentar(er)
