Overview: Using .NET

Microsoft .NET is a set of Microsoft software technologies for integrating software applications.

.NET components are generated in the designer and can be deployed to a .NET runtime environment as Web services, or as remotable .NET objects.

A remotable object is one that can be controlled from a different computer than the one where it is deployed. Using this object you can run tasks on computers where the ScreenConnectorProxy Service and the Java Virtual Machine are not installed and develop native client applications that do not require Java.

This .NET  interface	Provides this
.NET Web service	Supports stateless tasks only. An installer is generated to install .NET components in .NET Framework. Communicates with the clients via SOAP.
.NET remotable client object	Supports stateful tasks. Configuration and DLL files are created to aid in developing your client application. Uses .NET Remoting for client-server commmunication.

Typical .NET Solution

As shown in the following diagram, the native client uses remoting to communicate with the .NET object on the Web services computer; the Web services client communicates using SOAP. From the server, using COM, the .NET object communicates with the Attachmate ScreenConnectorProxy service. Through JNI, the ScreenConnectorProxy service calls into Java and then runs tasks using the IConnectorAccess interface.

The workflow

1. Generate .NET components in the designer.

2. Deploy to a .NET run-time environment.

3. Configure your client environment. Depending on whether you are deploying a Web service or a .NET remotable client object, this process will vary.

4. Using Visual Studio, create your project.

Code Samples for .NET Remotable Objects

• Client-activated Remote Object Client Sample: Hosted in IIS

  A simple console application that demonstrates how to execute a task via a client-activated remote object. The remote component is hosted in IIS and includes a corresponding configuration file.

• Server-activated Remote Object Server Sample

  A simple console application that demonstrates how to host a server-activated remote object. This application listens for client requests on TCP port 8989. The sample includes a corresponding configuration file.

• Server-activated Remote Object Client Sample: Hosted in a Custom Application

  This sample is dependent on the successful implementation of a server-activated remote object. The sample consists of a simple console application that demonstrates how to execute a task via a server-activated remote object hosted in a custom application. The sample includes a corresponding configuration file.

	Using Tasks in Your Applications, Overview
	Using Web Services
	Configuring a .NET Environment
	Deploying a .NET Remote Client Object
	Deploying Web Services Using .NET