My PC died so I had to build a new one. On my old PC I could import my .NET assembly into a PBL using the .NET Dll Importer tool, then debug to the line that actually calls the method in the assembly, and press F8 to step into SnapDevelop and start debugging the C# code.
Now, on my new PC, when I press F8 to step into the C# code one of two things happens:
- It just steps onto the next line of code in PowerBuilder and the result from calling the assembly has been successfully returned
- It launches SnapDevelop, but doesn't open the debugger and just comes back to the next line of code in PowerBuilder. I can;t see any error messages in SnapDevelop just a lit of Loaded assemblies in the Debug output, with the last assembly being mine
I'm not sure why it does option one for some methods / classes and option 2 for others.
I have made sure the "Launch SnapDevelop to debug C# assemblies" is checked in System Options.
I have tried this with the following combinations:
Assembly in .NET 6.0 and .NET Framework 4.8.1. PowerBuilder 2019 R3 and 2022 R3 Beta. Compiling the assembly with Visual Studio 2022 and SnapDevelop 2019 and 2022. On a colleague's PC, not working there either. I am running Windows 10, fully updated via Windows Update.
I know this was working on my old PC. Anyone have any ideas as to what I'm doing wrong? Of course my old PC had a ton of extra stuff installed, so maybe I am missign something on my new PC???
Thanks!
My issue with SnapDevelop seems to be: on the first step into SnapDevelop is launched and I can debug, then if I make another call from PowerBuilder into a different dll it hangs, unless I close the SnapDevelop that was previously launched first. Needs more experimentation, but that seems to be an issue.
I also wonder why I needed PowerBuilder 2021 installed and why SnapDevelop 2021 launches from PowerBuilder 2019, and why PowerBuilder 2022 R3 Beta didn't work. It's all a little flaky. May have to try installing PowerBuilder 2022 non-beta next.
regards