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

About the Author

No Biography provided

Comments and Discussions

 
GeneralSome Remoting Exceptions and how to deal with them PinmemberCohen Shwartz Oren18-Oct-04 0:08 
GeneralPermission problem - DelegateSerializationHolder PinmemberCohen Shwartz Oren18-Oct-04 0:09 
GeneralBecause of security restrictions, the type System. Runtime.Remoting.ObjRef cannot be accessed PinmemberCohen Shwartz Oren18-Oct-04 0:10 
GeneralThe constructor to desterilize an object of type MYException was not found.&#8221; PinmemberCohen Shwartz Oren18-Oct-04 0:11 
GeneralOverloading problem PinmemberCohen Shwartz Oren18-Oct-04 0:12 
GeneralAn unhandled exception of type 'System.Runtime.Remoting.RemotingException' Occurred in mscorlib.dll PinmemberCohen Shwartz Oren18-Oct-04 0:13 
GeneralSerialize object to the clients fails PinmemberCohen Shwartz Oren18-Oct-04 0:14 
GeneralEx: &#8220;Server encountered an internal error. For more information, turn on custom Errors in the server&#8217;s .config file.&#8221; PinmemberCohen Shwartz Oren18-Oct-04 0:15 
Descriptions: This Is a classic annoying error.
It happens on Frameword 1.0 as well as in 1.1
 
Fix –
You can turn the CustomErrors to “Off” but it only work on the same machine. Not if the client and server are in different machines
Check to see if we have full errors.
if( RemotingConfiguration.CustomErrorsEnabled( false ) == true )
Make sure the Exception object is a standard .Net Remoting standard Exception:
Step one
using System.Runtime.Serialization;
 
Step two
define the following constructor
protected MYException (SerializationInfo info, StreamingContext context):base(info,context){}
 
Step Three
The user define exception class must, implement the ISerializable interface or mark it with the [Serializable] attribute.
http://dotnetjunkies.com/WebLog/chris.taylor/archive/2004/01/10/5441.aspx
 
Step Four
Enter the following in the configuration file
>

...



General: &quot;The underlying connection was closed: Unable to connect to the remote PinmemberCohen Shwartz Oren18-Oct-04 0:15 
Generalgetting reconnected to the same old client PinmemberCohen Shwartz Oren18-Oct-04 0:16 
General[Msg Deleted] Pinmemberandre.pietsch25-Aug-05 2:49 
GeneralThanks PinmemberAndreas Nolte12-Oct-04 4:20 
GeneralProgrammatically configure serverProviders and clientprovider Pinmemberchalama2-Sep-04 6:22 
General&quot;Serialization will not deserialize delegates to non-public methods.&quot; PinmemberNeil de Weerdt26-Jul-04 1:50 
GeneralRe: &quot;Serialization will not deserialize delegates to non-public methods.&quot; PinmemberCohen Shwartz Oren26-Jul-04 2:18 
GeneralServer encountered an internal error. For more information, turn on customErrors in the server’s .config file.” PinmemberCohen Shwartz Oren19-Jul-04 5:13 
GeneralRe: Server encountered an internal error. For more information, turn on customErrors in the server’s .config file.” PinmemberCohen Shwartz Oren19-Jul-04 5:21 
GeneralRe: Server encountered an internal error. For more information, turn on customErrors in the server&#8217;s .config file.&#8221; PinsussAnthonyVO10-Feb-05 16:16 
GeneralRe: Server encountered an internal error. For more information, turn on customErrors in the server&#8217;s .config file.&#8221; PinmemberCohen Shwartz Oren12-Feb-05 20:20 
GeneralRe: Server encountered an internal error. For more information, turn on customErrors in the server&#8217;s .config file.&#8221; PinmemberAnthonyVO14-Feb-05 2:21 
GeneralRe: Server encountered an internal error. For more information, turn on customErrors in the server&#8217;s .config file.&#8221; PinmemberCohen Shwartz Oren14-Feb-05 2:31 
General.NET Remoting on Linux Pinmemberjrpally1-Jul-04 7:45 
GeneralThank You :) Pinmemberbzchai14-Jun-04 3:45 
GeneralThank You :) PinsussAnonymous14-Jun-04 3:45 
GeneralServer encountered an internal error. For more information, turn on customErrors in the server's config file PinmemberRamesh1104667-May-04 9:39 

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
Web04 | 2.8.140709.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