microsoft / microsoft/powerplatform-vscode
PowerShell will not debug with Power Platform Tools activated
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 277
- Forks
- 60
- Avg merge
- 1d 1h
- Merged PRs (30d)
- 14
Description
Type: Bug
I recently installed Power Platform Tools extension. Now when I try to debug a PowerShell script, I see "Activating extensions" in the status bar, then it goes away. I have tried restarting VSCode, I've tried disabling PPTools and I can debug fine, but as soon as I re-enable PPTools, I can no longer debug PowerShell. When I click F1 and select Show Running Extensions, I see all extensions running fine except PPTools which shows "1 uncaught errors - Menu item references the same command as default and alt-command"
Extension version: 2.0.31
VS Code version: Code 1.86.2 (903b1e9d8990623e3d7da1df3d33db3e42d80eda, 2024-02-13T19:40:56.878Z)
OS version: Windows_NT x64 10.0.22631
Modes:
System Info
| Item | Value |
|---|---|
| CPUs | 13th Gen Intel(R) Core(TM) i7-1370P (20 x 2189) |
| GPU Status | 2d_canvas: enabled canvas_oop_rasterization: enabled_on direct_rendering_display_compositor: disabled_off_ok gpu_compositing: enabled multiple_raster_threads: enabled_on opengl: enabled_on rasterization: enabled raw_draw: disabled_off_ok skia_graphite: disabled_off video_decode: enabled video_encode: enabled vulkan: disabled_off webgl: enabled webgl2: enabled webgpu: enabled |
| Load (avg) | undefined |
| Memory (System) | 31.66GB (14.11GB free) |
| Process Argv | --crash-reporter-id aa8207f0-482f-4deb-b60b-d4c60850f30a |
| Screen Reader | no |
| VM | 0% |
A/B Experiments
vsliv368cf:30146710
vspor879:30202332
vspor708:30202333
vspor363:30204092
vscod805:30301674
binariesv615:30325510
vsaa593cf:30376535
py29gd2263:30899288
c4g48928:30535728
azure-dev_surveyone:30548225
2i9eh265:30646982
962ge761:30959799
pythongtdpath:30769146
welcomedialog:30910333
pythonidxpt:30866567
pythonnoceb:30805159
asynctok:30898717
pythontestfixt:30902429
pythonregdiag2:30936856
pyreplss1:30897532
pythonmypyd1:30879173
pythoncet0:30885854
h48ei257:30968133
pythontbext0:30879054
accentitlementst:30887150
dsvsc016:30899300
dsvsc017:30899301
dsvsc018:30899302
edj9j583:30969295
fegfb526:30961430
7j2b6412:30969109
e3gdj431:30958358
ccp1r6:30958156
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the failure in VS Code with Power Platform Tools 2.0.31 enabled and a PowerShell script, then inspect Show Running Extensions for the uncaught menu-command error. Done means PowerShell debugging works while the extension is enabled and the PPTools extension no longer reports that error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- powershell, vscode
- Domain
- developer-experience, tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100