In your book
C# Web Services (Building Web Services with .NET Remoting and ASP.NET)

(First Indian Reprint: January 2002 ISBN: 81-7366-304-1.)
(Originally Printed in United States. ISBN: 1-861004-39-7)


There is an example where the server and client are created using configuration file. Page-134 to Page 138. (In chapter 6).

Sir after running the server which is waiting to respond to client, when I run the client. It uses the local assembly (MyRemoteObject.dll) to create the object. Which was used to compile the code. Instead of taking from server or referring the config file. Please help me.

I also want the link to download the code for this book. I am unable to locate it on the site.


Thanking you.
Amit Mirchandani.

Code---


////MyRemoteObject.cs/////////////
using System;

namespace amit
{
   public class MyRemoteObject : System.MarshalByRefObject
   {
      public MyRemoteObject()
      {
         System.Console.WriteLine("Constructor Called");
      }

      public string Hello(string name)
      {
         Console.WriteLine("Hello " + name);
         return "Hello Mr " + name;
      }

   }
///////////////////////////////////////////////////////


///////////SimpleServer.config////////////////////////
<configuration>
   <system.runtime.remoting>
      <application name="SimpleServer">
          <service>
                  <wellknown mode="SingleCall" type="amit.MyRemoteObject, MyRemoteObject" objectUri="MyRemoteObject" />
          </service>
          <channels>
            <channel ref="tcp server" port="9000" />
        </channels>
      </application>
   </system.runtime.remoting>
</configuration>
///////////////////////////////////////////////////////////////

//////SimpleServer.cs/////////////////////////
using System;
using System.Runtime.Remoting;

namespace amit
{
   class SimpleServer
   {
      static void Main(string[] ar)
      {
        RemotingConfiguration.Configure("SimpleServer.conf ig");
        Console.WriteLine("Press ne key");
        Console.ReadLine();


      }

   }
//////////////////////////////////////////////////////////


////////SimpleClient.config//////////
<configuration>
    <system.runtime.remoting>
        <application name="SimpleClient">
            <client url="tcp://localhost:9000/SimpleServer">
                                <wellknown type="amit.MyRemoteobject, MyRemoteObject" url="tcp://localhost:9000/SimpleServer/MyRemoteObject" />
             </client>
             <channels>
                <channel ref="tcp client" />
             </channels>
        </application>
    </system.runtime.remoting>
</configuration>
//////////////////////////////////////////////////////////////


///////SimpleClient.cs//////////////////////////
using System;
using System.Runtime.Remoting;

namespace amit
{
   class SimpleClient
   {
      static void Main(string[] ar)
      {
         RemotingConfiguration.Configure("SimpleClient.conf ig");
         MyRemoteObject obj = new MyRemoteObject();
         Console.WriteLine(obj.Hello("amit"));

      }

   }
}
///////////////////////////////////////////////////////////

Dear amitmirchandani,

There are two issues with the configuration files you've provided. The first on is this line in your client configuration file:
The attribute url is used in the client tag if you're working with CAO (Client Activated Objects). For SAO (Server ACtivated Objects), like the one you've used, the client tag contains no attributes. So remove this extra attribute. All else is fine with your server and client config files.

The second issue is the names of your config files. The general structure for naming a config file in .NET is assemblyname.extension.config, i.e. if your assembly's name is MyAssembly.exe, then the config file for your assemble should be named MyAssembly.exe.config. You can see that you've not followed this convention. Try renaming your config files so that they adhere to this standard. After you do this, don't forget to modify the call to the RemotingConfiguration.Configure() method accordingly.

I hope this should solve your problem.

Regards,

ejan