How to debug a generic method

RE: How to debug a generic method

Dennis Lindinger — Tue, 20 Dec 2016 15:07:43 GMT

Is your generic method compiling correctly in the method editor? Instead of System.Diagnostics.Debugger.IsAttached in the generic method, try System.Diagnostics.Debugger.Launch(). I've never had a problem breaking in a generic method. Dennis

RE: How to debug a generic method

Eli Donahue — Wed, 07 Dec 2016 11:40:00 GMT

Hi Carsten, Try the following steps after restarting IIS. 1. Open "Microsoft Visual Studio .NET 2012" debugger. 2. Choose Tools --> Attach to Processes…. 3. Choose w3wp.exe and click 'Attach'. 4. Choose Debug --> Exceptions to force the method into the debugger when an exception occurs and choose the check boxes "Thrown". 5. Optionally, you can include the line System.Diagnostics.Debugger.Break() to force a breakpoint at a specific line in your method. Eli Aras Labs Software Engineer

RE: How to debug a generic method

carstenw — Wed, 07 Dec 2016 04:13:35 GMT

Hi Zahar, thanks for your reply. That key is already present in my InnovatorServerConfig.xml, and I am able to debug my other methods just fine. The issue arises when I use the Innovator method applyMethod("someMethod", "someParameters"); I would like to step into the someMethod() implementation, this is what is not working for me. Are you yourself able to step into a method called this way?

RE: How to debug a generic method

Zahar Chernov — Tue, 06 Dec 2016 10:54:24 GMT

To enable debugger, you need to:

add following key to InnovatorServerConfig.xml <operating_parameter key="DebugServerMethod" value="true" />
restart the IIS

Be careful with this flag on Production environment, cause it can slow you production if you forgot to remove debugger from the code.