コミュニティ

• 

  Slowdima

  • 2013年08月01日 12:37

  Hello,
  
  Scripts from document definition ( rules, custom actions, export profiles, auto-correction scripts etc. ) can be debugged easily if they are written in COM-languages ( JScript or VBScript ). Just put a standard script breakpoint in script body ( "stop" for VBScript or "debugger" for JScript ) and during script execution your debugger will suggest you to debug the script ( just check that Tools -> Options -> Document Processing -> Disable External Script Debugging is turned OFF ).
  
  As for event handlers or custom stages, then some of them can be debugged in this way and some others can be not. For user-interactive scripts ( like "on user command" event handler) you may use FCtools.ShowMessage for debugging. Noninteractive scripts ( like "document processing script" for example ) usually have access to IProcessingCallback interface, which allows you to write custom messages into task log. You can see the log on processing server monitor by double-clicking on the task record.
  
  Finally, ANY script can be debugged if it is written in .NET and implemented as a call of external component, for example class library. It is assumed that code of the component is created in Visual Studio. And the code should contain a System.Diagnostics.Debugger.Break() function call as a breakpoint. In script body you just create an instance of your custom class and call a method of this class with some input parameters. So, the whole script body will be just a couple of lines. And the script body does not contain breakpoints. Then you should use "Attach to process" functionality in Vusual Studio to attach to FlexiCapture process before script execution. And when script will be executed, Visual Studion will be able to debug your component.

  いいえ 0 はい
• 

  Slowdima

  • 2013年08月02日 10:55

  Unfortunately, I had experience with Visual Studio only. So, as a free and relatively lightweight debugger I can recommend you a Visual Studio Express. Maybe other guys will suggest something better.

  いいえ 0 はい
• 

  Permanently deleted user

  • 2015年11月26日 22:25

  I know it's been a while this answer as been posted but can you please elaborate on how I can set up my code for debugging. I have a custom export workflow/stage that calls my external function. So how would I go about setting up debugging. I tried putting the System.Diagnostics.Debugger.Break() in my code but this just propmted me for a debugger and when I select VS 2012 everything freezes.

  いいえ 2 はい

サインインしてコメントを残してください。