Settings and activity
5 results found
-
4 votesPayton Byrd shared this idea ·
-
154 votes
An error occurred while saving the comment Payton Byrd supported this idea · -
276 votesPayton Byrd supported this idea ·
-
1,685 votesPayton Byrd supported this idea ·
-
4 votesPayton Byrd shared this idea ·
I love this idea and want to add my 22 cents worth...
1. This would make module development much easier as currently VS Code with the PowerShell extension is the only viable option and VS Code is horrible at debugging C#.
2. You could use the .Net Framework version for Windows PowerShell debugging and the .Net Core version for PowerShell 6+ debugging.
3. We really need a way to debug both PowerShell Script, and the CLR hosted by the Runspace at the same time. Nothing that I know of currently can do this.
4. Integrating PowerShell as a console in LinqPad would be a huge help overall.
5. Being able to .Dump() objects in PowerShell would be hugely useful.