Soapsuds.exe -- Imp. Tool (.Net Framework Tools Series)

Soapsuds.exe -- Imp. Tool (.Net Framework Tools Series)

using System;
using System.Runtime.Remoting;
using System.Runtime.Remoting.Channels;
using System.Runtime.Remoting.Channels.Http;

public class Calc:MarshalByRefObject
{
           public int Add(int i , int j)
            {
                    return i+j;
            }
            public int Del(int i , int j)
            {
                    return i-j;
            }
            public int Mul(int i , int j)
            {
                    return i*j;
            }
            public int Div(int i , int j)
            {
                    return i/j;
            }
}

using System;
using System.Runtime.Remoting;
using System.Runtime.Remoting.Channels;
using System.Runtime.Remoting.Channels.Http;

class ClassMain
{
          /// <summary>
          /// The main entry point for the application.
          /// </summary>
          [STAThread]
          static void Main(string[] args)
          {
            HttpChannel httpChannel = new HttpChannel(8765);
            ChannelServices.RegisterChannel(httpChannel);
            RemotingConfiguration.ApplicationName ="MyRemotingApp";
            RemotingConfiguration.RegisterWellKnownServiceType(typeof(Calc),"MyCalc",WellKnownObjectMode.Singleton);
            Console.WriteLine("Server started ..... ");
            Console.ReadLine();
          }
}

6) Our Http Remoting Server is now ready which will work on port 8765. This is a Singleton server i.e. only object will be  created and this object will server to all the clients.

7) Compile the application and create the executable.

8) Run the executable and you should get a message "Server started". The server executable should be running hence forth throughout the example.

Step 2:

     <A href="http://localhost:8765/MyRemotingApp/MyCalc?WSDL" target=_top>http://localhost:8765/MyRemotingApp/MyCalc?WSDL</A>

Step 3:

1) See that the server is running (Run the executable).

2) Go to the VS.NET command prompt and type soapsuds /? . This will list all the available options.

Input Sources (only one can be specified)
-urlToSchema(-url):[SchemaUrl]
-types:[type1,assemblyname[,serviceEndpoint]][;type2,assemblyname[,serviceEndpoint]][...]
-inputSchemaFile(-is):schemafile Input Schema File
-inputAssemblyFile(-ia):assemblyfileInput Options
-inputDirectory(-id):directory     Location of input dlls.
-serviceEndpoint(-se): Url for Service Endpoint placed in Wsdl file

Output Options
-outputSchemaFile(-os):schemafile
-outputDirectory(-od):directory for generated source files
-outputAssemblyFile(-oa):assemblyfile

Generate Options
-GenerateCode(-gc)  (equivalent to "-od:.")

Other Options
-WrappedProxy(-wp) Create wrapped proxy (default)
-NoWrappedProxy(-nowp)   No wrapped proxy
-proxyNamespace(-pn)  Namespace on generated proxy (Only used for interopNamespaces)
-StrongNameFile(-sn):filename   Use strong name to build assembly

Connection Information Options
-username(-u):username
-password(-p):password
-domain(-d):domain
-httpProxyName(-hpn):name
-httpProxyPort(-hpp):number

Note : After these options there are some examples given about the usuage of the tool. Check them out.

    soapsuds -url:<A href="http://localhost:8765/MyRemotingApp/MyCalc?WSDL" target=_top>http://localhost:8765/MyRemotingApp/MyCalc?WSDL</A> -gc

    soapsuds -url:<A href="http://localhost:8765/MyRemotingApp/MyCalc?WSDL" target=_top>http://localhost:8765/MyRemotingApp/MyCalc?WSDL</A> -oa:MyServer.dll

    soapsuds -url:<A href="http://localhost:8765/MyRemotingApp/MyCalc?WSDL" target=_top>http://localhost:8765/MyRemotingApp/MyCalc?WSDL</A> -os:MyServer.xmlStep 4:

using System;
using System.Runtime.Remoting.Channels;
using System.Runtime.Remoting.Channels.Http;
using RemotingServer;

namespace RemotingClient
{
       /// <summary>
       /// Summary description for Client
       /// </summary>
       class Client
       {
               /// <summary>
               /// The main entry point for the application.
               /// </summary>
               [STAThread]
               static void Main(string[] args)
               {

                 HttpChannel httpChannel = new HttpChannel();
                 ChannelServices.RegisterChannel(httpChannel);
                 RemotingServer.Calc obj = new Calc();
                 obj =(RemotingServer.Calc)Activator.GetObject(typeof(RemotingServer.Calc),                     "<A href="http://localhost:8765/MyRemotingApp/MyCalc" target=_top>http://localhost:8765/MyRemotingApp/MyCalc</A>");
                 Console.WriteLine(((RemotingServer.Calc)obj).Add(1,2));
                 Console.ReadLine();
               }
       }
}

3) In this we are opening an HTTP channel to communicate with our remote object. Our remote object is a SAO i.e. Server activated
object. Finally we are calling the Add function, which should return us 3.

4) First we will add our proxy class i.e. RemotingServer.cs to our application. Add compile the project.

Note: There should not be any reference to any remoting server dll's in our project. The only addition should be Remoting server  class, which will communicate with the remote object.

5) Result 3 should be displayed.

6) Stop the application and remove the proxy class RemotingServer.cs. NOW ADD reference to MyServer.dll and compile the project and execute it.

7) Result 3 should be displayed.

8) This way we can use either the proxy class or the proxy dll to communicate with our remoting object.

Step 5 :

Let us now check out some other important options of soapsuds.

1) Generating xml schema, assembly and code for a particular type in the assembly.

       soapsuds -types:Calc.MyServer,MyServer -gc
       soapsuds -types:RemotingServer.Calc,MyServer -os:MyCalc.xml
       soapsuds -types:RemotingServer.Calc,MyServer -oa:MyCalc.dll

       soapsuds -is:MyServer.xml -gc
       soapsuds -is:MyServer.xml -oa:MyServer1.dll

This article has no explicit license attached to it but may contain usage terms in the article text or the download files themselves. If in doubt please contact the author via the discussion board below.

A list of licenses authors might use can be found here