Deploying a .NET Remote Client Object
When you generate a .NET remotable object with Task Builder, .NET creates a DLL and some helper files. By default, generated remote objects are configured for hosting within IIS. If you are hosting your remotable objects outside of IIS, or if you're using two web servers to keep one Java-free, see the .NET Deployment Examples topic.
The paths below are for .NET Visual Studio 2002. If you are using .NET Visual Studio 2003, the name of the target directory will be NETTarget2003.
|To deploy a .NET remote client object to run a task on a client computer
- Copy task_name.dll and Remotetask_nameClient.config from
to your development or client computer.
||The remoting folder contains the task_name.dll file and the sample configuration files for hosting .NET remotable objects. Also, it contains Interop.IMSCONNECTORPROXYSERVICELib.dll, a helper DLL that facilitates communication between the .NET object and the IMSConnectorProxy service.
- Edit the following line in Remotetask_nameClient.config to point to the IIS server where the remote object is hosted and where the IMSConnectorProxy service was installed:
- In Visual Studio .NET, add a .NET reference to task_name.dll and write your client application against the task_name API.
The client application should call RemotingConfiguration.Configure ( ) with the modified Remotetask_nameClient.config file as an argument. This will tell the remoting framework that the task_name API is running remotely on the IIS server.
- Distribute task_name.dll and Remotetask_nameClient.config with the client application.