This section describes how to upgrade from FormDirector 2 to FormDirector 6.  While generally you'll be able to replace FormDirector 2 with FormDirector 6, there are a few important changes you may need to consider.

Assembly Changes

Projects must now target .NET Framework 3.5 or later to build with the FormDirector assembly.

The assembly filename has been renamed from Accusoft.FormDirector2.Net.dll to Accusoft.FormDirector.Net.dll. Project references must be updated to use the new assembly.

Recommended Changes

Image Transfer

There are several different ways to import and export image data into the FormDirector class. In V3, in addition to the existing methods, we have provided new interfaces to achieve that between FormDirector and other applicable Accusoft components. These new methods are recommended for their ease of use to prevent memory leaks.

Export

void TemplateImage.CopyTo(System.Object Destination);

Import

Importing image data to a TemplateImage object is achieved by passing a TemplateImage object as the input of the same export methods called by another Accusoft object. The TemplateImage object has to be instantiated before passed in.

Note that although TemplateImage class supports exporting using CopyTo() only, it does support importing using TransferTo() and CopyTo() initiated by another object.

API Changes

• Deprecated
  FormDirector is fully licensed from now on and is not required to install licenses or call licensing API. Other FormSuite components, such as FormFix, ScanFix Xpress, SmartZone ICR and SmartZone OCR, are still required to install licenses or call licensing API. The following enumeration, class, and methods are now marked as deprecated and will be removed from a future release of FormDirector:
  • EvaluationMode Enumeration
  • Licensing Class
  • EvaluationMode Property (Licensing)
  • SetOEMLicenseKey Method (Licensing)
  • SetSolutionKey Method (Licensing)
  • SetSolutionName Method (Licensing)
• Added
  • The method GetTemplateHashCode() has been added to the API, to determine when the template images in the form definitions or form set have changed. FormFix uses the hash code to determine if the template images have changed, requiring it to recompute Form Set Analysis data. FormFix caches Form Set Analysis data, rather than recomputing it on each run, to save time during forms processing.