I have described the procedures to implement .net remoting
in IIS. By hosting the server and client in IIS we can achieve the following
benefits based on project implementation.
Client web site does not need to bother about remote settings in
config or code at minimum. It just requires adding reference to the proxy
interface. However, if you want, you can use Client.exe.config for more
Client needs to be host once which can be accessed by as many users.
It saves client application deployment time for each user/machine.
Server and client automatically use the IIS security features,
We can implement different features of remoting, such as
SingleCall/Singleton, CAO, and SAO, etc. In my view, SingleCall SAO with Http
channel and binary formatter suits best when hosting server side component in
I hope this article will be helpful for .NET programmers.
Comments and suggestions are appreciated.
Abhishek Kumar Singh