1,202 questions
I think this issue is related to 1582433 .
Installation of VS2019 Build Tools into container installs VS2022 version rather than VS2019.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(86.4, 41%, 18%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ESP%3C/text%3E%3C/svg%3E)
Stefan Padurariu
1
Reputation point
I am trying to setup a TeamCity agent that runs in docker.
I want to install Visual Studio 2019 Build Tools on this TeamCity agent. I am following the instructions described on this page: https://learn.microsoft.com/en-us/visualstudio/install/build-tools-container?view=vs-2019#create-and-build-the-dockerfile
When I build the docker image, I notice that it installed 2022 version rather than the 2019 version. I have tried to install Visual Studio 2017 Build Tools as well, but it installs the 2022 version.
Here is the Dockerfile that I am running: 176784-dockerfile.txt . I have updated it to use powershell commands rather than cmd commands.
Steps to reproduce:
- Get Docker
- Configure Docker to use Windows Containers
- Download the Dockerfile.txt and remove the txt extension
- Build the image:
docker build -t can/teamcity-agent:2021.2.3-windowsservercore-2004 . - Run the container
- Inspect the container and see the C:\Program Files (x86)\Microsoft Visual Studio\
- Notice folder named 2022
Developer technologies Visual Studio Setup
{count} votes
-
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(140.8, 78%, 23%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ETS%3C/text%3E%3C/svg%3E)
Tianyu Sun-MSFT 34,436 Reputation points Microsoft External Staff2022-02-23T07:40:47.607+00:00 Hi @Stefan Padurariu , welcome to Microsoft Q&A forum.
Could you help to check if the installed version of Visual Studio Build Tools is really VS 2022 or only the folder name is 2022 but it’s VS 2019 Build Tools?
For example, you can use PowerShell/CMD commands to confirm it, by navigating to "C:\Program Files (x86)\Microsoft Visual Studio\2022\BuildTools\Common7\Tools" and run
vsdevcmd.batdirectly. Then check the prompt likeVisual Studio 2019/2022 Developer Command Prompt v16.0/17.0… -
Stefan Padurariu 1 Reputation point
2022-02-23T10:01:16.817+00:00 The result of running "C:\Program Files (x86)\Microsoft Visual Studio\2022\BuildTools\Common7\Tools\vsdevcmd.bat" is:
-
Stefan Padurariu 1 Reputation point
2022-02-23T10:01:41.527+00:00 Btw, I found a temporary workaround. I have switched to chocolatey to install VS Build Tools 2019, rather than downloading and using the
vs_buildtoolsexecutable.# Default arguments ARG teamcityAgentImage='jetbrains/teamcity-agent:2021.2.3-windowsservercore-2004' # dotnet, git, java, ps FROM ${teamcityAgentImage} USER ContainerAdministrator # Use cmd.exe SHELL ["cmd", "/S", "/C"] ### Install Chocolatey RUN powershell -NoProfile -ExecutionPolicy Bypass \ -Command "$env:ChocolateyUseWindowsCompression='false'; \ iex ((New-Object System.Net.WebClient).DownloadString('https://chocolatey.org/install.ps1'))" ### Configure Windows RUN powershell add-windowsfeature web-asp-net45 ### Install VS2019 build tools (replace 2019 with 2017 for 2017 version) RUN choco install visualstudio2019buildtools -y \ && choco install visualstudio2019-workload-azurebuildtools -y \ && choco install visualstudio2019-workload-databuildtools -y \ && choco install visualstudio2019-workload-manageddesktopbuildtools -y \ && choco install visualstudio2019-workload-netcorebuildtools -y \ && choco install visualstudio2019-workload-nodebuildtools -y \ && choco install visualstudio2019-workload-webbuildtools -y \ && choco install visualstudio2019-workload-xamarinbuildtools -y -
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(262.40000000000003, 76%, 35%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EAB%3C/text%3E%3C/svg%3E)
Anthony Burns 1 Reputation point2022-12-12T20:12:16.543+00:00 Subsequent to a support ticket I opened, I believe the https://aka.ms/vs/16/release/vs_buildtools.exe link to download VS Build Tools 2019 is now corrected. I haven't yet had time to confirm this in a docker container, but I don't see a reason why this would not resolve the issue.
Sign in to comment