Add dev environment setup with WinGet Configuration#40117
Open
Add dev environment setup with WinGet Configuration#40117
Conversation
benhillis
force-pushed
the
user/benhill/setup-dev-env
branch
from
9d13a2f to
e7e465d
Compare
benhillis
requested review from
Brian-Perkins,
craigloewen-msft,
damanm24 and
jstarks
Contributor
There was a problem hiding this comment.
Pull request overview
Adds a PowerShell prerequisite-checker to help contributors validate a Windows WSL dev environment before building, and extends the test runner to support an /attachdebugger convenience option (with corresponding documentation updates).
Changes:
- Add
tools/setup-dev-env.ps1to validate core build prerequisites (CMake, VS, SDK, symlink capability) and optionally WinDbg/Python. - Update
tools/test/run-tests.ps1to implement/attachdebuggerby launching WinDbgX against the TAEF host process. - Document the new script and test option in developer docs and instructions.
Reviewed changes
Copilot reviewed 5 out of 5 changed files in this pull request and generated 5 comments.
Show a summary per file
| File | Description |
|---|---|
| tools/setup-dev-env.ps1 | New prerequisite checker script with install guidance for missing components |
| tools/test/run-tests.ps1 | Adds /attachdebugger handling and launches WinDbgX against the test host PID |
| doc/docs/dev-loop.md | References the new setup script and documents /attachdebugger vs /waitfordebugger |
| test/README.md | Documents test.bat/run-tests.ps1 option /attachdebugger behavior |
| .github/copilot-instructions.md | Updates repo guidance to include /attachdebugger |
benhillis
force-pushed
the
user/benhill/setup-dev-env
branch
from
e7e465d to
ba60a0f
Compare
benhillis
force-pushed
the
user/benhill/setup-dev-env
branch
from
ba60a0f to
f335c0b
Compare
benhillis
force-pushed
the
user/benhill/setup-dev-env
branch
from
f335c0b to
a08d8e9
Compare
benhillis
force-pushed
the
user/benhill/setup-dev-env
branch
from
d49e820 to
c89c9e5
Compare
benhillis
force-pushed
the
user/benhill/setup-dev-env
branch
from
16079e2 to
9b4fd54
Compare
benhillis
force-pushed
the
user/benhill/setup-dev-env
branch
from
9b4fd54 to
9e42b72
Compare
|
Hey @benhillis this could probably be handled with a WinGet Configuration file. |
Member
Author
Good suggestion. Let me look into it. |
benhillis
changed the title
benhillis
force-pushed
the
user/benhill/setup-dev-env
branch
from
f8c4b7a to
b593245
Compare
benhillis
changed the title
dkbennett
reviewed
Apr 7, 2026
Member
Author
|
Switched to WinGet Configuration files in the latest revision. Thanks for the suggestion @denelon! |
yao-msft
previously approved these changes
Apr 10, 2026
| tools\setup-dev-env.ps1 | ||
| ``` | ||
|
|
||
| This uses [WinGet Configuration](https://learn.microsoft.com/windows/package-manager/configuration/) to install Developer Mode, CMake, Visual Studio 2022, and the required workloads from [`.vsconfig`](https://github.com/microsoft/WSL/blob/master/.vsconfig). If VS 2022 is already installed, the script detects your edition (Community, Professional, or Enterprise) and uses the matching configuration. If no VS 2022 is found, it defaults to Community. |
There was a problem hiding this comment.
nit: winget configure may not be enabled by default out of the box. "winget configure --enable" enables it. We could either document it here or call the command in the dev setup script.
Add a one-command developer environment setup that uses WinGet Configuration (DSC) to install all build prerequisites: Developer Mode, CMake, Visual Studio 2022, and the required VS workloads/components. New files: - tools/setup-dev-env.ps1: Detects any existing VS 2022 edition (Community/Professional/Enterprise) and runs the matching WinGet configuration. Defaults to Community when no VS 2022 is found. - .vsconfig: Declares the required VS components (MSVC, ATL, Clang, Windows SDK 26100, UWP tools, .NET desktop/WinUI workloads) so VS Installer can import them directly. - .config/configuration.winget: WinGet DSC config for VS Community. - .config/configuration.vsProfessional.winget: Same for Professional. - .config/configuration.vsEnterprise.winget: Same for Enterprise. Updated doc/docs/dev-loop.md to document the automated setup and reference the new .vsconfig and winget configuration files, while keeping manual install instructions in a collapsed details block.
benhillis
force-pushed
the
user/benhill/setup-dev-env
branch
from
b3f4ca4 to
9e2f805
Compare
Comment on lines
+57
to
+66
| $configPath = Join-Path $configDir $configFile | ||
|
|
||
| # ── Run WinGet Configuration ──────────────────────────────────────── | ||
| Write-Host "" | ||
| Write-Host "Running WinGet Configuration ($configFile)..." -ForegroundColor Cyan | ||
| Write-Host " This will install: Developer Mode, CMake, VS 2022 + required components" | ||
| Write-Host "" | ||
|
|
||
| winget configure --enable | ||
| if ($LASTEXITCODE -ne 0) |
There was a problem hiding this comment.
Before running winget configure, consider validating prerequisites explicitly (e.g., winget is available and $configPath exists). With $ErrorActionPreference = "Stop", a missing winget binary or missing config file will terminate the script with a generic error rather than the more actionable messages below.
Address review feedback: document that 'winget configure --enable' is required before running winget configure manually, since the feature may not be enabled by default. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
yao-msft
approved these changes
Apr 13, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds a one-command developer environment setup using WinGet Configuration with per-edition VS support, following the pattern used by microsoft/winget-cli and microsoft/terminal.
Quick start
Or run a WinGet configuration directly:
How it works
WinGet Configuration files (3 self-contained configs, one per VS edition): Each declaratively installs Developer Mode, CMake, Visual Studio 2022, and all required workloads/components from
.vsconfigusing DSC resources. Idempotent and safe to re-run.Smart detection script (
tools/setup-dev-env.ps1): Usesvswhereto detect any existing VS 2022 installation and picks the matching configuration file. If no VS 2022 is found, defaults to Community edition. The script is a thin wrapper — all the real work is done bywinget configure.What gets installed
Microsoft.Windows.Settings/WindowsSettingsDSC resourceMicrosoft.WinGet.DSC/WinGetPackageDSC resourceMicrosoft.WinGet.DSC/WinGetPackage+Microsoft.VisualStudio.DSC/VSComponentswith.vsconfigFiles
.config/configuration.winget— WinGet config (Community edition, default).config/configuration.vsProfessional.winget— WinGet config (Professional).config/configuration.vsEnterprise.winget— WinGet config (Enterprise).vsconfig— Required VS workloads/componentstools/setup-dev-env.ps1— Smart edition detection +winget configuredoc/docs/dev-loop.md— Updated prerequisites documentationDeveloper flow