diff --git a/doc/devdocs/core/installer.md b/doc/devdocs/core/installer.md index 71efed1529..7d3c375b2c 100644 --- a/doc/devdocs/core/installer.md +++ b/doc/devdocs/core/installer.md @@ -88,7 +88,7 @@ ### Building PowerToys Locally #### One stop script for building installer -1. Open `Developer Powershell for VS 2022` or `Developer PowerShell for VS` for VS 2026. +1. Open `Developer PowerShell for VS`. 2. Run tools\build\build-installer.ps1 > For the first-time setup, please run the installer as an administrator. This ensures that the Wix tool can move wix.target to the desired location and trust the certificate used to sign the MSIX packages. @@ -109,7 +109,7 @@ dotnet tool install --global wix --version 5.0.2 ##### From the command line -1. From the start menu, open a `Developer Command Prompt for VS 2022` or `Developer Command Prompt for VS` +1. From the start menu, open a `Developer Command Prompt for VS` 1. Ensure `nuget.exe` is in your `%path%` 1. In the repo root, run these commands: @@ -140,7 +140,7 @@ If you prefer, you can alternatively build prerequisite projects for the install The resulting installer will be available in the `installer\PowerToysSetupVNext\x64\Release\` folder. -To build the installer from the command line, run `Developer Command Prompt for VS 2022` or `Developer Command Prompt for VS` in admin mode and execute the following commands. The generated installer package will be located at `\installer\PowerToysSetupVNext\{platform}\Release\MachineSetup`. +To build the installer from the command line, run `Developer Command Prompt for VS` in admin mode and execute the following commands. The generated installer package will be located at `\installer\PowerToysSetupVNext\{platform}\Release\MachineSetup`. ``` git clean -xfd -e *exe -- .\installer\ diff --git a/doc/devdocs/development/debugging.md b/doc/devdocs/development/debugging.md index 8b6d4de27e..c3e254e0a2 100644 --- a/doc/devdocs/development/debugging.md +++ b/doc/devdocs/development/debugging.md @@ -15,7 +15,7 @@ Before you can start debugging PowerToys, you need to set up your development en You can build the entire solution from the command line, which is sometimes faster than building within Visual Studio: -1. Open `Developer Command Prompt for VS 2022` or `Developer Command Prompt for VS` +1. Open `Developer Command Prompt for VS` 2. Navigate to the repository root directory 3. Run the following command(don't forget to set the correct platform): ```pwsh @@ -105,7 +105,7 @@ If you encounter build errors about missing image files (e.g., `.png`, `.ico`, o 1. **Clean the solution in Visual Studio**: Build > Clean Solution - Or from the command line (Developer Command Prompt for VS 2022 or Developer Command Prompt for VS): + Or from the command line (`Developer Command Prompt for VS`): ```pwsh msbuild PowerToys.slnx /t:Clean /p:Platform=x64 /p:Configuration=Debug ``` diff --git a/doc/devdocs/development/dev-with-vscode.md b/doc/devdocs/development/dev-with-vscode.md index 8228e3e339..ab8ba57b99 100644 --- a/doc/devdocs/development/dev-with-vscode.md +++ b/doc/devdocs/development/dev-with-vscode.md @@ -15,9 +15,27 @@ VS Code extensions Needed: --- ## Building in VS Code -### Configure Developer Powershell for VS 2022 or Developer Powershell for VS for more convenient dev in vscode. -1. Configure profile in in settings, entry: "terminal.integrated.profiles.windows" -2. Add below config as entry (choose VS 2022 or VS 2026 based on your installation): +### Configure Developer PowerShell for VS for more convenient dev in VS Code +1. Configure profile in settings, entry: `terminal.integrated.profiles.windows` +2. Add below config as entry (choose VS 2026 or VS 2022 based on your installation): + +**For Visual Studio 2026 (recommended):** +```json + "Developer PowerShell for VS": { + // Configure based on your preference + "path": "C:\\Program Files\\WindowsApps\\Microsoft.PowerShell_7.5.2.0_arm64__8wekyb3d8bbwe\\pwsh.exe", + "args": [ + "-NoExit", + "-Command", + "& {", + "$orig = Get-Location;", + // Adjust path based on your edition (Community/Professional/Enterprise) + "& 'C:\\Program Files\\Microsoft Visual Studio\\18\\Enterprise\\Common7\\Tools\\Launch-VsDevShell.ps1';", + "Set-Location $orig", + "}" + ] + }, +``` **For Visual Studio 2022:** ```json @@ -37,24 +55,6 @@ VS Code extensions Needed: }, ``` -**For Visual Studio 2026:** -```json - "Developer PowerShell for VS": { - // Configure based on your preference - "path": "C:\\Program Files\\WindowsApps\\Microsoft.PowerShell_7.5.2.0_arm64__8wekyb3d8bbwe\\pwsh.exe", - "args": [ - "-NoExit", - "-Command", - "& {", - "$orig = Get-Location;", - // Adjust path based on your edition (Community/Professional/Enterprise) - "& 'C:\\Program Files\\Microsoft Visual Studio\\18\\Enterprise\\Common7\\Tools\\Launch-VsDevShell.ps1';", - "Set-Location $orig", - "}" - ] - }, -``` - 3. [Optional] Set your Developer PowerShell profile as the default, so that you can get a deep integration with vscode coding agent. 4. Now you can build with plain `msbuild` or configure tasks.json in below section. diff --git a/doc/devdocs/modules/fancyzones.md b/doc/devdocs/modules/fancyzones.md index 0f3c812131..b1bdf4b3d0 100644 --- a/doc/devdocs/modules/fancyzones.md +++ b/doc/devdocs/modules/fancyzones.md @@ -152,7 +152,7 @@ FancyZones is divided into several projects: ## Development Environment Setup ### Prerequisites -- Visual Studio 2022 or 2026: Required for building and debugging +- Visual Studio 2026 (or 2022 17.4+): Required for building and debugging - Windows 10 SDK: Ensure the latest version is installed - PowerToys Repository: Clone from GitHub @@ -183,7 +183,7 @@ FancyZones is divided into several projects: ## Debugging ### Setup for Debugging -1. In Visual Studio 2022 or 2026, set FancyZonesEditor as the startup project +1. In Visual Studio, set FancyZonesEditor as the startup project 2. Set breakpoints in the code where needed 3. Click Run to start debugging