Skip to content

build,win: add WinGet Visual Studio 2022 Build Tools Edition config#61652

Merged
nodejs-github-bot merged 1 commit intonodejs:mainfrom
MikeMcC399:visual-studio-2022-winget-add-build-tools
Feb 11, 2026
Merged

build,win: add WinGet Visual Studio 2022 Build Tools Edition config#61652
nodejs-github-bot merged 1 commit intonodejs:mainfrom
MikeMcC399:visual-studio-2022-winget-add-build-tools

Conversation

@MikeMcC399
Copy link
Contributor

@MikeMcC399 MikeMcC399 commented Feb 3, 2026

Current situation

BUILDING > Windows > Option 2: Automated install with WinGet contains instructions to install Node.js build prerequisites using predefined .configurations for Visual Studio 2022 on Windows:

Edition Configuration
Community configuration.dsc.yaml
Professional configuration.vsProfessional.dsc.yaml
Enterprise configuration.vsEnterprise.dsc.yaml

Compared to both the sections Option 1: Manual install and Option 3: Automated install with Boxstarter, a WinGet configuration for the Visual Studio 2022 Build Tools Edition for Option 2 is missing. The documentation is also slightly misleading, since it lists "Visual Studio 2022 Build Tools" as being installed, although this edition is not installed.

Change

  • Add a Build Tools 2022 Edition configuration to the .configurations directory:

    Edition Configuration
    Build Tools configuration.vsBuildTools.dsc.yaml

    The required Desktop develop development with C++ workload has ID: Microsoft.VisualStudio.Workload.VCTools, differing from other editions such as the Community Edition which uses instead ID: Microsoft.VisualStudio.Workload.NativeDesktop.

  • Align workload naming to the Visual Studio Installer UI and documentation, changing "Visual C++" to "Desktop development with C++" workload.

  • Use relative links to ensure the document points to its own branch and not just the main branch

@nodejs-github-bot
Copy link
Collaborator

Review requested:

  • @nodejs/build
  • @nodejs/tsc

@nodejs-github-bot nodejs-github-bot added build Issues and PRs related to build files or the CI. doc Issues and PRs related to the documentations. labels Feb 3, 2026
@MikeMcC399 MikeMcC399 force-pushed the visual-studio-2022-winget-add-build-tools branch from 2156d16 to 77cc845 Compare February 3, 2026 12:26
@MikeMcC399

This comment was marked as outdated.

@MikeMcC399

This comment was marked as outdated.

Copy link
Member

@lpinca lpinca left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

RSLGTM

@MikeMcC399

This comment was marked as resolved.

@MikeMcC399

This comment was marked as resolved.

@aduh95 aduh95 added author ready PRs that have at least one approval, no pending requests for changes, and a CI started. commit-queue Add this label to land a pull request using GitHub Actions. labels Feb 11, 2026
@nodejs-github-bot nodejs-github-bot removed the commit-queue Add this label to land a pull request using GitHub Actions. label Feb 11, 2026
@nodejs-github-bot nodejs-github-bot merged commit fbb9b42 into nodejs:main Feb 11, 2026
23 checks passed
@nodejs-github-bot
Copy link
Collaborator

Landed in fbb9b42

@MikeMcC399 MikeMcC399 deleted the visual-studio-2022-winget-add-build-tools branch February 11, 2026 17:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

author ready PRs that have at least one approval, no pending requests for changes, and a CI started. build Issues and PRs related to build files or the CI. doc Issues and PRs related to the documentations.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants