vs_buildtools.exe --layout C:\vs2022_buildtools_offline --lang en-US The bootstrapper will refresh the layout, downloading only new or updated packages. Instead of a single vs2022_buildtools_offline folder, create dated versions:
FROM mcr.microsoft.com/windows/servercore:ltsc2022 COPY ./vs2022_buildtools_offline C:/vs_layout RUN C:/vs_layout/vs_buildtools.exe --quiet --wait --norestart --installPath C:/BuildTools --add Microsoft.VisualStudio.Workload.VCTools Use --add Microsoft.VisualStudio.Component.VC.Tools.x86.x64 instead of full workload for smaller container size. 3. Generating a Bootstrapper for Distribution You can create a self-contained vs_buildtools.exe that references your layout: visual studio build tools 2022 offline installer
Full list: Run vs_buildtools.exe --list in an online environment. 1. Offline Installation on Windows Server Core Windows Server Core has no GUI. You must use the silent installer: vs_buildtools
vs_buildtools.exe --layout C:\vs2022_buildtools_offline --lang en-US This downloads all available Build Tools workloads and components for English (en-US). It will take a long time (10–100+ GB) and considerable bandwidth. To save space and time, specify only the workloads you actually need. Use --add to include workloads or individual components. Generating a Bootstrapper for Distribution You can create
$layoutPath = "E:\vs2022_buildtools_offline" $installer = "$layoutPath\vs_buildtools.exe" $installPath = "C:\BuildTools" & $installer --quiet --wait --norestart --installPath $installPath --add Microsoft.VisualStudio.Workload.ManagedDesktopBuildTools --add Microsoft.VisualStudio.Workload.VCTools --includeRecommended
C:\layout\vs_buildtools.exe --quiet --wait --norestart --installPath C:\BuildTools Add --add parameters as needed. Create a Dockerfile that copies the layout and installs: