Try OpenEdge Now
skip to main content
GUI for .NET Programming
Preface : Example procedures : Compiling and running the sample classes and procedures

Compiling and running the sample classes and procedures

To compile and run the sample classes and procedures:
1. Install the samples into the OpenEdge installation directory as directed.
2. In the OpenEdge installation directory, you can then locate the samples for this manual in the following directory path:
This directory contains one file, assemblies.xml, and two subdirectories, classes and procedures. The assemblies.xml file contains information necessary to access the .NET object types referenced by these sample classes and procedures. The classes subdirectory contains sample ABL class definitions and related files. The procedures subdirectory contains a set of sample procedure source files. Some of these procedure files represent stand-alone examples, and some of them represent drivers for sample classes defined in the classes subdirectory. Driver procedures all have the word, “Driver”, in their filenames. The rest of the filename is generally the name of the sample class that the driver procedure instantiates. For example, MDIFormDriver.p instantiates the class defined by MDIForm.cls.
3. Before compiling and running these files in your OpenEdge development environment:
a. Add the classes and procedures subdirectories to your PROPATH.
b. Move the assemblies.xml file to your working directory. In Progress Developer Studio for OpenEdge, this is the top-level project directory that contains your classes and procedures subdirectories.
After you install these samples, the OpenEdge installation directory also contains additional ABL samples that illustrate elements of the OpenEdge GUI for .NET and that have been built using the Visual Designer in Progress Developer Studio for OpenEdge. In the installation directory, you can locate these Visual Designer samples in the following directory path:
Each sample resides in its own subdirectory with the complete set of files, including any assemblies.xml file, required to compile and run it. This manual provides more information on assemblies.xml files and some of the other file types provided with these samples.