NETDefGen Help

Overview Of Copy file Generation

.Net Assemblies are made up of one or more Classes within a Namespace.  A COBOL program

accesses an Assembly using a Namespace and Class defined within a copy file.  Within a

Namespace Class hierarchy are Methods, Properties, Enumerations and Events.

NetDefGen interrogates an Assembly and produces an English translation for Namespaces,

Classes, Methods, Enumerations, Properties and Events.  The resultant copy file is included in a

COBOL program for use by the compiler and programmer.

In addition to the copy file, event handlers are generated for each Class in the Assembly.

.NET events and event data are delivered to the ACUCOBOL runtime and COBOL program from

event handlers.

Event handlers are loaded by the runtime when a COBOL program executes a Display statement,

a Create statement or references an Assembly in a COBOL Screen Section.

By default the runtime locates Event handlers from the same directory where the runtime is

located.  The runtime configuration variable NET-EVENTS-PREFIX can also be used to specify

one or more directory paths to search.

Windows base types: integer, unsigned integer, float, double, byte, character and character string

are all supported.

Objects are not supported.  Any method, property or constructor requiring a parameter of type

object will fail when executed by the COBOL program as will any method or property that returns

an object.

Please see A Guide to Interoperating with ACUCOBOL-GT for more detailed information.

This is the path to the directory where the assembly you wish to produce a copy file from resides.

This will be the computer’s path to the Global Assembly Cache (GAC) by default when the

program first executes.  If the desired .NET assembly resides in another directory you may enter

the path in this edit field or click the Browse button to navigate to the appropriate directory.

Clicking the GAC button will set this field to the GAC path at any time.

If the Global Assembly Cache.(GAC) is the currently selected Assembly Location then this list

box will contain all the Assemblies found there.  If the directory selected is other than the GAC

then all the .dll and .exe files will be listed (both assemblies and non-assemblies).

When an Assembly is selected from the list, all Namespaces and Classes found in that

Assembly will display in the list box labeled Namespace Classes.

By default, when an assembly has been selected from the Assemblies list all of the items found

in the assembly will be selected.  Assemblies may contain many namespaces and classes

which can result in very large copy files containing many references and declaration that are

unused by your application.  To reduce the size of your copy file you can select only those items

that are needed by your application.

The entry field labeled Copyfile To Create contains the full path and file name of the copy file to

generate.  If event handlers are generated, they will be located in the same directory with a file

name prefix of the Namespace and Class and a suffix of .DLL. You may enter the path and

filename in this edit field or click the Browse button to navigate to the appropriate directory.

The Generate Copyfile button will only be enabled when an assembly is selected, at least one

namespace/class is selected and a valid copy file destination has been entered into the Copyfile

To Create field.

Clicking the Generate Copyfile button will generate the copy file and any required event handlers.

Success or failure messages will appear in the status area at the bottom of the screen.

Displays this help file.

Closes the utility application.

               Remember the Last Startup Directory: default

               The utility will remember the last directory selected with assemblies and will restore the

               selection on subsequent executions.  Note that this is not affected by using the GAC

               button.  You may select the GAC at any time and your previously selected directory

               will be retained.

               Set a Fixed Startup Directory:

               Use this selection if you wish the utility to always startup in the same directory.

               Remember the Last Destination Directory and File: default

               Unchecking this option will cause the utility to always assume that the startup

               location is the destination.

               Allows the use of up to two different versions of .NET. Enter the paths of the versioned

               tools and select the radio button for the version you want the utility to use.

               Double-Clicking on the field will clear it causing the utility to use which ever version is

               the current default on the development machine.

               These selections can aid the debugging process.  The first selection will cause the

               utility to include debug information in any event dlls it creates.  The second selection

               will keep the intermediate IL source code the utility generates when creating an event

               dll.  This can be most useful when working with Micro Focus Technical Support to

               resolve a problem.