Answer: Microsoft now has an official NuGet package (see blog post). Old answer, prior to August 2016; provided in case the NuGet package doesn’t work for you: Install dacframework.msi (x86|x64) Install SQLDOM.MSI (x86|x64) Install SQLLS.MSI (x86|x64) Install SQLSysClrTypes.msi (x86|x64) Install SSDTBuildUtilities.msi (from the “Administrator Install Point” as setup in step 3 here) Done! Source: Headless … Read more
All steps to install build tools: Download build tools Download layout files for offline installation: Possible workloads are specified here. Following command contains workloads for msbuild and C++ build tools. Run (exe file will have some version numbers in name): vs_BuildTools.exe –layout c:\BT2017offline –add Microsoft.VisualStudio.Workload.MSBuildTools –add Microsoft.VisualStudio.Workload.VCTools –add Microsoft.VisualStudio.Workload.WebBuildTools –add Microsoft.VisualStudio.Workload.NetCoreBuildTools –lang en-US Copy c:\BT2017offline … Read more
To run on on your CI server without Visual Studio, you only need to copy a few folders from a development machine to the same location on the CI server. There is no need to install the SDK. VS 2015: C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v14.0\Web C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v14.0\WebApplications VS 2013: C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v12.0\Web C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v12.0\WebApplications VS … Read more
The reason given is actually a huge benefit. Builds that go to QA should only ever come from a system that builds only from the repository. This way build packages are reproducible and traceable. Developers manually building code for anything except their own testing is dangerous. Too much risk of stuff not getting checked in, … Read more
It is possible to run mstest.exe without visual studio. Download one of the Agents for Visual Studio ISO’s below and install the Test Agent on the server: Visual Studio 2019 Visual Studio 2017 (127MB disk space, less than that for download) Visual Studio 2015 and older: visit https://www.visualstudio.com/vs/older-downloads/ and follow the instructions This installs everything … Read more
Use the command line utility TF – Team Foundation Version Control Tool (tf). You can get a list of all workspaces by bringing up a Visual Studio Command Prompt then changing to your workspace folder and issuing the following commands: C:\YourWorkspaceFolder>tf workspaces /owner:* You should see your problem workspace in the list as well as … Read more
The Visual Studio Build tools are a different download than the IDE. They appear to be a pretty small subset, and they’re called Build Tools for Visual Studio 2019 (download). You can use the GUI to do the installation, or you can script the installation of msbuild: vs_buildtools.exe –add Microsoft.VisualStudio.Workload.MSBuildTools –quiet Microsoft.VisualStudio.Workload.MSBuildTools is a “wrapper” … Read more
To answer the title of the question (but not the question about the output you’re getting): Copying the following folder from your dev machine to your build server fixes this if it’s just web applications C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v10.0\WebApplications Remove x86 according to how your build breaks. If you have other project types you will probably … Read more