Open adamdriscoll opened 1 month ago
Curses. I got that too. The cannot view or watch variables in the debugger. Assumed I had borked my Visual Studio install.. So I uninstalled Visual Studio and installed the latest rev.. Went to reinstall the pro tools extension and now I have 2 problems.
Yes, I know. I really need to get up to speed with gitub. I went install the pro tools from the ironman web site, and found out that it was being open sourced here. No probs. . BUT there is no downloader for visual studio at https://ironmansoftware.com/powershell-pro-tools/downloads. So I came here? And I, for the life of me, cannot work out how to get hold of the latest rev. Do you want me to create an installer ?
Forgive me .. but my first concern is to get my really rubbish bit of powershell working. I use the excellent forms stuff. Do not want to get distracted with sorting out an install or migrating to VS Code et al.. at this stage.
Please help.
Sorry ... to be more specific .. Can't get forms, but can run the existing .ps1
This when I do a quickwatch. ............... Hover gives me nothing.
Unable to evaluate the expression. Operation not supported. Unknown error: 0x80070057.
Same with me. I may also say that the locals window is empty during debugging but filled when debugging C# code.
Rolled back to VS enterprise 17.8.13 and still debugging issues.
Go back to a previous version of pro tools
P
From: Martin @.> Sent: Saturday, September 7, 2024 1:39 AM To: ironmansoftware/powershell-pro-tools @.> Cc: DE GROOT Peter [Eastern Goldfields College] @.>; Comment @.> Subject: Re: [ironmansoftware/powershell-pro-tools] Issues running scripts in Visual Studio (Issue #82)
Rolled back to VS enterprise 17.8.13 and still debugging issues.
- Reply to this email directly, view it on GitHubhttps://github.com/ironmansoftware/powershell-pro-tools/issues/82#issuecomment-2334527919, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AAZDRAG5EDKVW5MEKVAQ46TZVHSCPAVCNFSM6AAAAABLWWTLBCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGMZUGUZDOOJRHE. You are receiving this because you commented.Message ID: @.**@.>>
I haven't actually had the time to look into this yet but this was reported on the Marketplace site: