Debug during CPS/OES export

[wto2fe]

I want to debug a StartupParams.otd file during CPS/OES export.

Debugging with XaeShell:

If I try to do this with XaeShell, I´m able to  select "attach to Process", then debugging is running and the code stops in the breakpoint.

But if I add a variable to the watch list, then comes the message "internal error  in the C# compiler".

I have this behavior on my old and on my new Laptop.

Debugging with VisualStudio 2013:

If I try to do the debugging with VisualStudio 2013, then I get this fault message, when I klick on the "attach to process... " button:

I have this behavior only with my new laptop. With my old laptop, debugging with VisualStudio 2013 woks correct.

[wto2fe]

Has anyone ever successfully debugged the export with XaeShell?

[SteffenR-]

I have the same behaviour like you with TcXaeShell.

You can try to reinstall VS2013 or install VS2015 (first Isolated Shell, then Integrated Shell):

https://visualstudio.microsoft.com/vs/older-downloads/isolated-shell/

[wto2fe]

@ SteffenR

Can you discuss this problem (TcXaeShell) with Beckhoff?

[SteffenR-]

After discussing with Beckhoff: debugging C# code will never be possible with TcXaeShell.

To debug C# code you need a licensed Visual Studio (or an old Visual Studio Shell like VS2015, see above).