FormDirector Class

A class used to initialize various resources and expose general interfaces not directly associated with form definition, such as for licensing and debugging.

Object Model

Syntax

Visual Basic
C#
C++/CLI

'Declaration
 
<ToolboxBitmapAttribute(Accusoft.FormDirectorSdk.FormDirector, "FormDirector.ico")>
<DesignerCategoryAttribute("Component")>
Public Class FormDirector 
   Inherits System.ComponentModel.Component

'Usage
 
Dim instance As FormDirector

[ToolboxBitmap(Accusoft.FormDirectorSdk.FormDirector, "FormDirector.ico")]
[DesignerCategory("Component")]
public class FormDirector : System.ComponentModel.Component

[ToolboxBitmap(Accusoft.FormDirectorSdk.FormDirector, "FormDirector.ico")]
[DesignerCategory("Component")]
public ref class FormDirector : public System.ComponentModel.Component

Remarks

The primary purpose of the FormDirector class is to activate licensing for the FormDirector component, in addition to setting debug attributes.

Note: A FormDirector instance should be created before other classes within the Accusoft.FormDirector namespace are used.

The following classes require a FormDirector object to be passed as an [In] parameter of their Constructors:

Generally, you will only need to create one new FormDirector instance per process, which can be passed to all of the other objects that require it. The only reason to create multiple FormDirector instances in a single process is if there is a need to use multiple debug logs or licenses.

For example, if an application used 2 (two) FormSetFile objects, and there was a need to have each FormSetFile object create and write to its own log file, a FormDirector object would need to be created for each FormSetFile object.

Inheritance Hierarchy

System.Object
   System.MarshalByRefObject
      System.ComponentModel.Component
         Accusoft.FormDirectorSdk.FormDirector

Reference

FormDirector Members
Accusoft.FormDirectorSdk Namespace