PowerShell debugger error in Visual Studio 2019
Issue #194
resolved
I am having the same issue noted in issue #89, so it appears the issue is not fully resolved, or has re-occurred with updated software
I am running Windows 10 build 1903, Visual Studio Community 2019, and PowerShell Tools for Visual Studio 4.9.4 (trial llicense), all clean/fresh installs. This build/version of Windows is inherently running .NET Framework 4.8. Please note that I’ve also installed the Desktop Development workload with VS 2019, which was the fix mentioned in issue 89, so it seems there is some other missing dependency. I did try running a repair on VS 2019 just for giggles, and it did not help.
Whenever I try to launch debugging for a PowerShell project with a Windows Forms file, even just a default blank one, I immediately get the “Attaching the PowerShell Debug Engine debugger to process…” error message, after which the debugger just hangs indefinitely, and I have to force it to stop.
I am hoping for a solution on this soon, because the 21-day limited trial of this software is flying by quickly, and I haven’t been able to really test it at all. Thank you.
Comments (4)
-
-
reporter
Thanks for the quick response. Let me know if you need any further info from my machine. Just to note, this machine does have some corporate lockdown policies in place, but I also have administrator rights on it. Also, I tried running VS 2019 itself in administrator mode, and got the same debugger error.
-
Thanks. And don’t worry about the trial time. I can always cut you a new license.
-
- changed status to resolved
Resolved in v5.1.1
- Log in to comment
Thanks for the heads up. It looks like this is also an issue with Windows 2016 RDSH servers for some reason. I have users that have had success on Windows 1903 with VS 2019 Community and 4.9.4 but others are not having success. It’s not consistent so there is something going on with the installation in certain scenarios. Trying to nail it down.