How to host a Remote Object in IIS
1. Build a simple remote object
.Net Remoting provides multiple ways to making an object remotable. They can be passed by value or by reference. After an object is passed by value, a copy of it exists in the program domains of both client and the server.
On the other hand, if an object is passed by reference to the client program, it exists only on the server. Clients must access its methods through the reference. To do this, we must derive the remote class from the MarshalByRefObject class in the System namespace.
2. Host the Remote Object in IIS
At first, you need create a new directory where the Remote Object will be placed. Then create a directory named bin beneath the above directory and copy the compiled Remote Object (DLL) to the bin directory.
In the meanwhile, this directory should be configured to be an application folder in IIS.
In the next step, create a new file called web.config. The sample content is listed below.
<?xml version="1.0" encoding="utf-8" ?>
<configuration>
<appSettings>
……
</appSettings>
<system.runtime.remoting>
<application>
<channels>
<channel ref="http" />
</channels>
<service>
<wellknown
mode="SingleCall"
type="AppRemotingLogger.BusinessRules.DefaultHome, AppRemotingLogger.BusinessRules"
objectUri="AppRemotingLogger.IHome.soap" />
</service>
</application>
</system.runtime.remoting>
</configuration>
It’s important to note that if you are hosting your remote object in IIS, you can’t declare an application name using application name attribute in web.config file. In this case, the virtual directory of your application automatically becomes the application name.
Elements of Configuration File:
<wellknown
mode="SingleCall"
type="BusinessRules.DefaultHome, BusinessRules"
objectUri="IHome.soap" />
<wellknown> element contains information about server-activated (well-known) objects the application exposes to clients. The mode attribute states whether the server offers a singleton or singlecall object. Its value can be either “Singleton” or “SingleCall”.
The type attribute is used to state the name of the type being offered, and the assembly or program in which it exists.
The objectUri attribute specifies the URI endpoint where the remote object is to be published.
3. Check the correctness
When you have it done, your object is hosted on your network. Then you can access the remote object at the URL:
HTTP://<servername>/<appname>/<URI.soap>?wsdl
Where <servername> is the name of the computer that hosts the object, <appname> is the name of the application, which is the same as the name of the virtual directory’s application name. And <URI.soap> is the URI that you specify in the object’s web.config file.
If IE browser can response WSDL, it shows you’ve successfully deployed remote object in IIS.