Breakpoints and Exceptions not showing up in Visual Studio 2017. Debugging Powershell Core Binary Module

[Former user]

I believe the tools should enable debugging a powershell module much as you might a .NET excecutable.

If I launch powershell and load the module from a debug script launched in the debug action an exception or breakpoint is not shown in Visual Studio and an exception simply blows up in red text in the shell.

What is the state of support for .Net standard with PoSH tools and PoSH pro?

Do you feel this is something that should be working?

Thanks

Craig

[Adam Driscoll]

Hi Craig,

.NET Standard should be working as long as you have .NET framework 4.7.2 installed on your machine. This is likely the case since PoshTools requires it. PoshTools does not yet support PowerShell Core but a .NET Standard library should work in PoshTools.

The .NET debugger isn't automatically attached to a PowerShell script you run through PoshTools. The alternative method is to setup your .NET project to launch PowerShell.exe and execute the script. This doesn't provide PowerShell debugging but will provide .NET debugging.

It's possible to get the .NET debugger to work with the PowerShell debugger but I haven't had a huge request for this so it was never implemented.