コミュニティ

• 

  Katja Ovcharova

  • 2015年12月01日 08:47

  Dear psquare,
  
  For export scripts your external DLL should be attached to FC in the .Net references tab of the Document Definition properties. Please check that this is set up properly for your project.
  
  Further, you did not specify what VS version is used to debug your DLL. For example, if it is VS 2010, then you should use "Tools->Attach to process" after your export script reaches the breakpoint and then choose the FlexiEx.exe in the list of running processes.
  
  In earlier VS versions you will need to specify a path to the .pdb file (if your dll does not required a registration - for registered libs this is not necessary):
  - If symbol files are located at the same place as the dll itself, then set:
  HKEY_CURRENT_USER\Software\ABBYY\FlexiCapture\10.0\Controller\ScriptSupport\ [LoadSymbolsFromOriginalPath] = true
  - If it is necessary to specify full path to symbol files:
  HKEY_CURRENT_USER\Software\ABBYY\FlexiCapture\10.0\Controller\ScriptSupport\ [PDBSearchLocations] =
  Please keep in mind that the symbol file must have the same name as the dll-assembly.
  
  Some information on external dll bebugging is also available in our knowledgebase, here and here.
  
  Please let me know if these hints helped you to get the debug working.

  いいえ 0 はい
• 

  Permanently deleted user

  • 2015年12月01日 21:15

  Perfect thanks you that was the step i was missing the attach to process i was unable to find which one but now that you told me it was FlexiEx.exe it works like a charm.
  
  Thank you very much

  いいえ 0 はい

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