Deploying a .NET Remote Client Object

These instructions assume that:

To deploy a .NET remote client object to run a task on a client computer
  1. Copy <project_name>.dll and Remote<project_name>Client.config from Attachmate/EAI/recordings/<project_name>/webservice/NETTarget/assembly
    to your development or client computer.
    Note For hosting .NET objects, along with the <project_name>.dll file and the sample configuration files for .NET remoting, the assembly folder also contains Interop.SCREENCONNECTORPROXYSERVICELib.dll.
    This is a helper DLL that facilitates communication between the .NET object and the ScreenConnectorProxy service.

    The sample configuration file, Remote<project_name>Server.config, is provided to help you write custom programs in order to host remote interfaces outside of IIS. By default, generated remote objects are configured for hosting within IIS.

  2. Edit Remote<project_name>Client.config to point to the IIS server where the remote object is hosted and where the ScreenConnectorProxy service was installed. For example:

    <client url="http://localhost/Test">
    <activated type="Test.RemoteTest, Test"/>
    <wellknown type="Test.RemoteTestFactory, Test" 
    <channel ref="http">
    <formatter ref="binary"/>

  3. In Visual Studio .NET, add a .NET reference to <project_name>.dll and write your client application against the <project_name> API.

    The client application should call RemotingConfiguration.Configure ( ) with the modified Remote<project_name>Client.config file as an argument. This will tell the remoting framework that the <project_name> API is running remotely on the IIS server.

  4. Distribute <project_name>.dll and Remote<project_name>Client.config with the client application.
Related Topics
Bullet Using .NET, Overview
Bullet Configuring a .NET Environment
Bullet Deploying Web Services Using .NET
Bullet .NET Deployment Examples