The following tables list selected tasks that you might need to complete when working with the OpenEdge GUI for .NET and where you can find more information about them.
The Visual Designer is the tool provided by OpenEdge Architect for building a GUI for .NET application. It opens whenever you create or edit an ABL Form, ABL Dialog, ABL MDI Form, ABL User Control, or ABL Inherited Control object in OpenEdge Architect. Each of these objects is an ABL class that inherits and extends a .NET form or control class. Depending on the object type, Visual Designer allows you to build the class by dragging and dropping components, setting properties, and using wizards, which generates code for the class, and you can switch to code view to add code manually using the OpenEdge Editor. For an introduction to the Visual Designer see, Introducing the OpenEdge Architect Visual Designer. For a series of video tutorials on working with the GUI for .NET in OpenEdge Architect, see OpenEdge Architect Videos: Using Visual Designer and GUI for .NET in OpenEdge Architect.
Understanding the code generated for an inherited .NET form
Visual Designer automatically generates code when you create a new ABL Form (ABL-derived .NET form). The following information describes some of this generated code.
OpenEdge Architect Online Help:
Using the assemblies.xml file in development and deployment
Any ABL application that implements a GUI for .NET, or that only references a .NET object type, must have access to an assemblies.xml file that identifies the .NET assemblies defining all .NET objects referenced by the session. OpenEdge Architect automatically creates an assemblies.xml file, which you can update, for any project that references a .NET object.
Building localized forms
Deployment involves setting localization options and installing files associated witht the .NET objects you reference.
OpenEdge provides the .NET Progress.Data.BindingSource (ProBindingSource) class to bind ABL data to .NET user-interface controls that support data binding using the System.Windows.Forms.BindingSource class. Typically, a .NET control supports data binding using a BindingSource class if it has a property of type System.Object (typically named DataSource) to assign the data source object instance, including a ProBindingSource, or it has a property of type ControlBindingsCollection (typically named DataBindings) that you can use to bind data elements from the ProBindingSource to specified properties on the control.Â For an overview of data binding in the GUI for .NET, see Binding ABL Data to .NET Controls in GUI for .NET Programming.
ABL supports events as members of a class, including .NET events, which you can process using a form of the WAIT-FOR statement.
Much of the support for the GUI for .NET is in how ABL supports access to .NET types.