.NET Proxy Generated Code

A generated .NET proxy is a set of object-oriented classes that correspond to the set of methods selected during generation. There are three main classes that a developer can access and use. Other classes are generated, but they are not exposed for use by the application. The three exposed classes are:

<method-name> Referred to as the .NET Proxy object
<method-name> Import Referred to as the Import object
<method-name> Export Referred to as the Export object

This chapter discusses the details of the three generated interfaces.

In addition to the generated interface, a .NET Proxy also consists of runtime code and a set of user modifiable exit routines. The user exits influence how the runtime handles security and communications processing.

The creation of an executable .NET Proxy involves both generating the .NET Proxy source code and installing the proxy. You can choose to do these two operations as two independent activities or as a single operation (select Install after generation option on the Proxy Code Generation dialog).

Generating a .NET Proxy results in a \proxy\net directory structure being added to your <model-name>.ief directory. The generated proxy source code is contained in a directory structure under \proxy\net\src. The installed, or built, .NET proxy code is contained in a directory structure \proxy\net\deploy.

The following file map shows the structure of the generated directories:

The generated proxy source code is placed in the \src\<component> directory. After the Build Tool has successfully built the proxy, the \proxy\net directory includes a \deploy\<component> directory. This directory contains a <component>.dll. This dll is the .NET Proxy and the user-written code uses this.

The \deploy\<component> directory includes a \samples directory. Within the \samples directory, there are APP, ASP.NET and an option XML directory.

Select the optional XML API only if you want to generate the XML sample. The ASP.NET, APP, and XML directories contain the generated samples. You can use the sample to test the generated proxy. The generated sample code also demonstrates the possible usage of the proxy. The samples are not considered part of the proxy.

If you select XML API for generation, then the \deploy\<component> directory also includes the XML schema file (.XSD). The XML schema file is considered part of the proxy itself.

More information:

Generating the Proxy

User Exits