Next: Debugging COM objects with gdb, Previous: Creating COM objects with GNAT [Contents][Index]

### 5.4 Using GNAT COM objects as Distributed COM objects

Using COM objects in a distributed fashion is more of a configuration issue then a programming issue. For both the client code and the server code there are no changes that need to be done. Remote machines need to have their registry updated to include the various COM entries and the type library must be registered. A simple application that does this is in `remote.adb`.

It registers the type library and inserts the same registry entries as the COM containers, but does not insert a server type and uses the key/value pair RemoteServerName/ServerName to specify the IP address or name of the remote server. It is possible to override the specified server name by using `CoCreateInstanceEx` instead of `CoCreateInstance` in the client code.

When using DCOM, you must also configure permissions to remote machines to access the COM objects. This is done using the Windows NT utility dcomcnfg.exe.