Deploying a .NET Remote Client Object
These instructions assume that:
- .NET Visual Studio is installed on the computer where Attachmate Designer Studio is installed.
- In the designer, you have created a project and have generated a .NET Web service. When you deploy the Web service, the remote interface is automatically configured.
- The following components are installed on the server where the remotable .NET objects are hosted:
- .NET Framework
- Screen Connector Proxy service
|To deploy a .NET remote client object to run a task on a client computer
to your development or client computer.
||For hosting .NET objects, along with the
<project_name>.dll file and the sample configuration files for .NET remoting, the
assembly folder also contains
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.
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:
<activated type="Test.RemoteTest, Test"/>
- In Visual Studio .NET, add a .NET reference to
<project_name>.dll and write your client application against the
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.
Remote<project_name>Client.config with the client application.