No Longer Able To Debug Custom Activities After Studio Update

Help Activities
, ,
1

When developing a custom activity in Visual Studio you could previously attach the debugger to the UiPath Executor and use that to run through your code, hitting breakpoints etc.

It seems after an update of Studio I can no longer do this, I have 3 instances of the executor I could attach to and I believe the one I need to won’t let me since there is already a debugger attached.

Can anyone else confirm this behaviour before I register a bug with UiPath?

I also commented on this old topic related which also includes the ‘classic’ debugging steps but it didnt get any notice.

2

Anyone willing to help?

3

can you share image to clear your error?
regards,

4

As mentioned in my first post, unable to attach the debugger since the process already has a debugger attached.

Are you still able to debug custom activities from Visual Studio?

5

Just to bring this back up, I believe this is still an issue and custom activites cannot be debugged on the current versions of Studio.

6

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.

7

Thanks Luca, this way provides a way to debug again.

8

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.