Library tutorials & articles

Introducing .NET Remoting

Introduction

.NET Remoting provides a powerful and high performance way of working with remote objects. Architecturally, .NET Remote objects are a perfect fit for accessing resources across the network without the overhead posed by SOAP based WebServices. .NET Remoting is easier to use than Java's RMI, but definately more difficult than creating a WebService.

In this article, we will create a remote object that will return an Object read in from the database. I've also included an alternate object that omits the database functionality in order to allow those that don't have a database available to still play with .NET remoting. Make sure you are using Visual Studio.NET Beta 2 when attempting this project.

Comments

  1. 06 Dec 2005 at 13:00

    forget that last post ...

    I found it in my code ... non-application test code I threw in on the quick ... cause the StackOverflow.
  2. 05 Dec 2005 at 22:17

    Hey, did you ever find out what your problem was?

    I got the same error on a completely different project.

    Same M.O. ...

    ... unhandled exception of type 'System.StackOverflowException' occurred in mscorlib.dll
    during the first call to the object that was returned from the "Activator.GetObject()" call.
  3. 16 Aug 2005 at 06:45

    I encountered the following error message when running the ResumeClient.exe:


    " An unhandled exception of type 'System.StackOverflowException' occurred in mscorlib.dll "


    at the following line of code:


    Resume resume = loader.GetResumeByUserID(1); ;


    but I was able to observe the "New Reference Added!" string on the console of the ResumeSuperServer.  


    Could I safely assume that I already have "loader" as an object of "ResumeLoader", but I failed to obtain "resume" as an object of "Resume" ?

  4. 25 May 2004 at 08:20

    I was looking for a Remoting Sample for beginners for weeks and this was the first that made absolute sense to me. If you are a person with an average IQ like myself, and want to understand the basics of remoting implimentation, this is the tutorial for you!!


    Thanks David for making learning Remoting easy and fun!!




  5. 30 Jan 2004 at 12:11

    I've been looking for a way to implement a cross application boundary component in C# .NET for most of this week. This looks like it will suit my needs perfectly. Thanks.

  6. 27 Feb 2002 at 13:47

    Thanks for pointing this out. I'll update the tutorial

  7. 17 Jan 2002 at 19:48
    I noticed some typo's when playing around with this. (Note I did not use the SQL example since I wanted a very simple example)

    change
       ResumeLoader loader = (ResumeLoader)Activator.GetObject(
           typeof(ResumeServer), "tcp://localhost:9932/ResumeLoader");

       if(rs==null)

    to
       ResumeLoader loader = (ResumeLoader)Activator.GetObject(
           typeof(ResumeLoader), "tcp://localhost:9932/ResumeLoader");

       if(loader==null)


    Note the typeof() change and the change of the test item.

    Hope that is right (I would hate to have typos in my post fixing typos)
  8. 01 Jan 1999 at 00:00

    This thread is for discussions of Introducing .NET Remoting.

Leave a comment

Sign in or Join us (it's free).

David Talbot David Talbot is an experienced Software Architect with a diverse background including creating network applicances, working with television set top boxes, building Billing/CRM systems, Web Portals ...

Related podcasts

  • A Practical Look at Silverlight 2 Part 1

    Now that Silverlight 2 is at the Olympics and making a big splash, we wanted to explore this fascinating technology more. Microsoft Silverlight 2 is a cross-browser, cross-platform, and cross-device plug-in for delivering the next generation of .NET based media experiences and rich interactive ap...

Events coming up

  • Dec 9

    GL.net Group Meeting - December 2009

    Gloucester, United Kingdom

    The beginning of this year holiday season will belong to mocks. Ronnie and Stephen will take us for a tour around exciting world of unit testing.

We'd love to hear what you think! Submit ideas or give us feedback