Mirrors/PowerToys
1
0
Fork 0
mirror of https://github.com/microsoft/PowerToys.git synced 2025-12-15 11:17:53 +01:00
Code Issues Packages Projects Releases Wiki Activity

Update debugging.md

Browse Source
This commit is contained in:
Roman Bug
2020-10-27 15:38:40 +03:00
committed by GitHub
parent 810ee0e290
commit 877bd0954b
1 changed files with 2 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
doc/devdocs/modules/launcher/debugging.md
View File

@@ -11,10 +11,10 @@ This approach is used to test UI, plugins, and core `PowerToys Run` functionalit
2. Press `F5` to start debugging. 2. Press `F5` to start debugging.
## Debugging with runner ## Debugging with runner
This approach can be used to test UI, plugins, core `PowerToys Run` functionality and `PowerToys Run` settings. This approach **cannot** be used to debugg functions that execute on starting `launcher.exe` process. This requires building runner along with all the other modules on first compile, making it slower than `Direct debugging` approach. The subsequent compilations should be fast. This approach can be used to test UI, plugins, core `PowerToys Run` functionality and `PowerToys Run` settings. This approach **cannot** be used to debugging functions that execute on starting `launcher.exe` process. This requires building runner along with all the other modules on first compile, making it slower than `Direct debugging` approach. The subsequent compilations should be fast.
1. Right-click on `runner` and select `Set as startup Project`. 1. Right-click on `runner` and select `Set as startup Project`.
2. Press `F5` to start debugging. 2. Press `F5` to start debugging.
3. Attach debugger to `launcher.exe` process. 3. Attach debugger to `launcher.exe` process.
1. Go to `Debug->Attach to process..` 1. Go to `Debug->Attach to process..`
2. Filter and select `launcher.exe` process. 2. Filter and select `launcher.exe` process.
3. Click on `Attach`. 3. Click on `Attach`.