Using the Object Gateway for .NET
Creating Proxy Classes
This chapter covers the following topics:
The Object Gateway cannot generate proxy classes for .NET generic classes. It similarly cannot import .NET classes with generic subclasses or subinterfaces.
The following steps summarize the procedure:
Start a .NET Object Gateway server. The server must be running before the Wizard can be used.
The .NET Gateway Wizard Studio Template
Fill out the form. The following items can be defined:
The Wizard displays a list of available classes:
Selecting Classes to Import
Check the classes that you want to use, then click Finish
The InterSystems IRIS session sends an import request.
Upon receiving the request, the Object Gateway worker thread introspects the indicated .NET assemblies and classes.
The thread also loads dependent assemblies either from the local directory or from the Global Assembly Cache (GAC).
If it finds any .NET classes that are new or changed, or that have no proxy classes on the InterSystems IRIS side, the Object Gateway worker thread generates new proxy classes for them.
method imports the given class and all its dependencies by creating and compiling all the necessary proxy classes. The %Import()
method returns (in the ByRef argument imported
) a list of generated InterSystems IRIS proxy classes. For details of how .NET class definitions are mapped to InterSystems IRIS proxy classes, see the Mapping Specification
chapter in this guide.
is a onetime, startup operation. It only needs to be called the first time you wish to generate the InterSystems IRIS proxy classes. It is necessary again only if you recompile your .NET code and wish to regenerate the proxies.
Before you invoke %Import()
, prepare the additionalClassPaths
arguments. That is, for each argument, create a new %ListOfDataTypes
object and call its Insert()
method to fill the list. The optional additionalClassPaths
argument can be used to supply additional path arguments, such as the names of additional assembly DLLs that contain the classes you are importing via the Object Gateway. List elements should correspond to individual additional assembly DLL entries, which require the following format:
" rootdir\...\mydll.dll "
You can try to load an assembly from a directory outside of where DotNetGatewaySS.exe
is running, but you might experience a load error for your assembly when you try to use a class in the assembly. InterSystems recommends that you put all local assemblies in the same directory as DotNetGatewaySS.exe
. You can also specify assemblies in the GAC by using partial names for them, System.Data
, for example.
Import Dependencies and Exclusions
While mapping a .NET class into an InterSystems IRIS proxy class and importing it into InterSystems IRIS, the Object Gateway loops over all class dependencies discovered in the given .NET class, including all classes referenced as properties and in argument lists. In other words, the Object Gateway collects a list of all class dependencies needed for a successful import of the given class, then walks that dependency list and generates all necessary proxy classes.
You can control this process by specifying a list of assembly and class name prefixes to exclude from this process. While this situation would be rare, it does give you some flexibility to control what classes get imported. The Object Gateway automatically excludes a small subset of assemblies such as Microsoft.*
This method returns, in the ByRef argument allClasses
, a list of all public classes available in the assembly DLL specified by the first argument, jarFileOrDirectoryName
is a one-step convenience class method that combines calls to %Connect()
, and %Disconnect()
. It returns a list of generated proxies. It also logs that list, if the silent
argument is set to 0. The name
argument is a semicolon-delimited list of classes or assembly DLLs.