Click here to Skip to main content
Click here to Skip to main content

.NET Remoting: Passing through the obstacles path from version 1.0 to 1.1

, 31 Mar 2004
Rate this:
Please Sign up or sign in to vote.
Houston, we have a problem. One small step for mankind, one Giant irritation for developers.

Introduction

The following article's aim is to help those of you who want to use .NET Remoting on Framework 1.1*. This article will not teach you Remoting, mainly because I am not an expert on that field. Furthermore, my CodeProject colleagues published some useful and nice to read articles on that issue (see links below). The attached projects were kept simple as possible to allow you to overcome the changes presented by Framework 1.1*. It handles the maladies of security exception, serialization and delegates issues.

Background

Recently, I have faced the challenge of exposing objects via .NET Remoting. Like the most of you, I have started with the MSDN, and of course CodeProject, but all the examples were suited for Framework 1.0 only. Attempts to run 1.0 project on a 1.1 Framework ends with lots of exceptions.

  • Type System.DelegateSerializationHolder and the types derived from it (such as System.DelegateSerializationHolder) are not permitted to be deserialized at this security level.
  • Because of security restrictions, the type System.Runtime.Remoting.ObjRef cannot be accessed.
  • This remoting proxy has no channel sink which means either the server has no registered server channels that are listening, or this application has no suitable client channel to talk to the server.

The web is full of developers' complaints on the very same problems but I have not found a simple, corrective and comprehensive example. So there you have it!.

Code snippets

Activate through Config files

Server side configuration

 <system.runtime.remoting>
    <application name="ServerAssembly" >
     <service>
          <!-- type: is the full type name 
(type the class that inherit from MBR,assembly) of the 
object-->
          <!-- objectUri - alias -->
          <!-- Server tells remoting Here's a type 
Here's how and when to instantiate the type
Here's the name (end point) a client will use to contact the type
            -->            
  
        <wellknown mode="Singleton" 
            type="SharedAssembly.SharedObj, SharedAssembly" 

objectUri="ParachuteExample" />
           </service>
         <channels>
            <channel ref="tcp" port="6123">    
                <serverProviders>            
                    <formatter ref="binary" typeFilterLevel="Full" />
                </serverProviders>                
            </channel>    
         </channels>     
    </application>
  </system.runtime.remoting>

Server side code

RemotingConfiguration.Configure ("ServerAssembly.exe.config");

Client side configuration

   <system.runtime.remoting>
      <application>
         <client>
            <wellknown 
               type="SharedAssembly.SharedObj, SharedAssembly"
               url="tcp://localhost:6123/ParachuteExample"
            />
         </client>
       <channels>
    <channel ref="tcp" port="0">        
     <clientProviders>            
      <formatter ref="binary" />
     </clientProviders>
     <serverProviders>            
      <formatter ref="binary" typeFilterLevel="Full" />
     </serverProviders>            
    </channel>
   </channels>

      </application>

Client side code

RemotingConfiguration.Configure ("ClientAssembly.exe.config");
SharedObj remObject = new SharedObj();

Activate through code

Server side

    BinaryClientFormatterSinkProvider clientProvider = null;
    BinaryServerFormatterSinkProvider serverProvider = 
       new BinaryServerFormatterSinkProvider();
    serverProvider.TypeFilterLevel = 

    System.Runtime.Serialization.Formatters.TypeFilterLevel.Full;
                
    IDictionary props = new Hashtable();
    props["port"] = 6123;
    props["typeFilterLevel"] = TypeFilterLevel.Full;
    TcpChannel chan = new TcpChannel(
    props,clientProvider,serverProvider);

    ChannelServices.RegisterChannel(chan);

    RemotingConfiguration.RegisterWellKnownServiceType(typeof(SharedObj),
                    "ParachuteExample",
                    WellKnownObjectMode.Singleton);

Client Side

    BinaryClientFormatterSinkProvider clientProvider = 
       new BinaryClientFormatterSinkProvider();
    BinaryServerFormatterSinkProvider serverProvider = 
       new BinaryServerFormatterSinkProvider();
    serverProvider.TypeFilterLevel = 

    System.Runtime.Serialization.Formatters.TypeFilterLevel.Full;
                
    IDictionary props = new Hashtable();
    props["port"] = 0;
    string s = System.Guid.NewGuid().ToString();
    props["name"] = s;
    props["typeFilterLevel"] = TypeFilterLevel.Full;
    TcpChannel chan = new TcpChannel(
    props,clientProvider,serverProvider);

    ChannelServices.RegisterChannel(chan);


    Type typeofRI = typeof(IParachute);
    IParachute remObject = (IParachute)Activator.GetObject(    typeofRI,
                    "tcp://localhost:6123/ParachuteExample");

Using the code

Since some of you like configuration files while others like to connect and create the well known object via code, I have included two projects accordingly. Both projects, codeActivationExample.zip and configFileExample.zip, include the same assemblies as follows:

  • ClientAssembly
  • ServerAssembly
  • SharedAssembly

License

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

Share

About the Author

No Biography provided

Comments and Discussions

 
GeneralMy vote of 2 Pinmemberngoj29-Dec-09 14:22 
QuestionBug Remoting by TCP channel in Vista PinmemberZapfchen7-Jul-09 3:57 
AnswerRe: Bug Remoting by TCP channel in Vista PinmemberZapfchen9-Jul-09 2:36 
GeneralServer Raise Event Pinmembertbman16-Jan-09 14:54 
GeneralHi Thanks! HttpChannel is working now! Pinmemberjayzonpanget21-Oct-08 19:02 
GeneralSame problem in HttpChannel Pinmemberjayzonpanget21-Oct-08 18:56 
GeneralExcellent article, got exactly what I wanted Pinmemberebranson196912-May-08 8:43 
GeneralThanks a lot! Pinmembersidkud24-Dec-07 12:53 
GeneralWMI versus .Net Remoting Pinmemberpuromtec19-Aug-07 6:36 
GeneralRe: WMI versus .Net Remoting PinmemberCohen Shwartz Oren13-Aug-07 0:25 
GeneralRe: WMI versus .Net Remoting [modified] Pinmemberpuromtec114-Aug-07 4:42 
GeneralNicely Done PinmemberChristopher G. Lasater23-May-07 8:30 
GeneralRe: Nicely Done PinmemberCohen Shwartz Oren23-May-07 9:30 
GeneralExample fails using HttpChannel Pinmemberrcarsten14-Nov-06 22:13 
GeneralRe: Example fails using HttpChannel Pinmemberjayzonpanget21-Oct-08 19:03 
QuestionRetrieving events in VBA PinmemberJEBond24-Oct-06 5:46 
GeneralThanks a lot PinmemberNehal Kanani20-Jan-06 0:05 
GeneralRe: Thanks a lot PinmemberCohen Shwartz Oren12-May-07 6:14 
GeneralEvents PinsussHector Caban2-Apr-05 0:27 
I am using your sample code on my projects but the difference is that I am hosting it on IIS server.
 

I dont get any error message, but if 2 or more clients are connected then only the last connected client recieves the event.
 

GeneralRe: Events PinmemberCohen Shwartz Oren12-May-07 6:13 
GeneralRe: Events PinmemberChris Zubriski16-Sep-08 8:03 
Generalnew cool stuff PinmemberAlex Sivokho3-Feb-05 23:23 
GeneralRe: new cool stuff PinmemberCohen Shwartz Oren17-Mar-05 2:20 
GeneralRe: new cool stuff Pinmemberajn999917-Mar-05 18:40 
GeneralSome Remoting Exceptions and how to deal with them PinmemberCohen Shwartz Oren18-Oct-04 0:08 

General General    News News    Suggestion Suggestion    Question Question    Bug Bug    Answer Answer    Joke Joke    Rant Rant    Admin Admin   

Use Ctrl+Left/Right to switch messages, Ctrl+Up/Down to switch threads, Ctrl+Shift+Left/Right to switch pages.

| Advertise | Privacy | Mobile
Web02 | 2.8.141015.1 | Last Updated 1 Apr 2004
Article Copyright 2004 by Cohen Shwartz Oren
Everything else Copyright © CodeProject, 1999-2014
Terms of Service
Layout: fixed | fluid