Hello @Jon_Smith,
I can deduce from your previous post that you want to attach the debugger by selecting the Executor Process manually. While it is not wrong and generally that is the correct approach, Studio uses more than one executor concurrently for different purposes.
To get around this I suggest adding:
System.Diagnostics. Debugger.Launch() (see ms documentation)
It should be placed at the entry point of your activity (e.g. at the start of ExecuteAsync(), BeginExecute(), etc.) and place a breakpoint the following line of code. When this line of code is reached, you will be prompted to select a Debugger, select your instance of Visual Studio.
Do not forget to remove the line of code before publishing/ sharing the package with anyone else.
Also try running instead of debugging the process from Studio (“Run” \ “Run file”) when using this method.
This recommendation is for Runtime diagnostics. Hopefully this helps.
ashokkarale
Yoichi
lrtetala
naveen.s
Anil_G
PeCour
Ahmad_Rais
AJ_Ask
Soudios
chunkin.zhang