Book a Demo

Author Topic: Direct .dll debugging  (Read 5475 times)

yves.carrier

  • EA Novice
  • *
  • Posts: 8
  • Karma: +0/-0
  • I love YaBB 1G - SP1!
    • View Profile
Direct .dll debugging
« on: October 24, 2014, 04:37:13 am »
Using the Execution Analyzer, I try to launch a Debug session for a .dll file. But since this procedure is not documented in EA (as far as I know...), I read a rather outdated article titled "Visual Execution Analyzer in Enterprise Architect" (2009) that explains that, when debugging a Class library, you can pass the Class name, the method name and the value of the arguments separated by comas as arguments of the command line. I tried so... the Debug session seems to be properly launched but the arguments seem to be totally ignored. The Debug window just shows the Stack depth being used and that's it, nothing else. I never hit a Breakpoint. To confirm, I just deleted the arguments and got the exact same behaviour. Any help would be appreciated.

yves.carrier

  • EA Novice
  • *
  • Posts: 8
  • Karma: +0/-0
  • I love YaBB 1G - SP1!
    • View Profile
Re: Direct .dll debugging
« Reply #1 on: October 24, 2014, 07:27:45 am »
OK, at the risk to look a little fuzzy, I will reply to myself for the ones of you that may seek for the same thing as I was. Actually, EA provides a very convenient tool to test DLLs. This is the Execution Analyzer Workbench. You just need to configure your Debug - Workbench script (you enter the path of your .dll file in the required script parameter). Then, you can right-click on any Class of your dll and select the "Execution Analyzer - Create Workbench Instance of Class". The remaining of the process is self explanatory.
« Last Edit: October 24, 2014, 07:28:52 am by yves.carrier »