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.
Related articles
Related discussion
-
String was not recognized as a valid DateTime.
by royal ludhiana (19 replies)
-
ASP.NET Patterns every developer should know
by AndyGrant2005 (2 replies)
-
help me to get simple requirement
by Slicksim (1 replies)
-
Compatibility Issue on Firefox to display on Cursor Location
by ansari.wajid (0 replies)
-
Cursor Location in Freetextbox
by ansari.wajid (1 replies)
Related podcasts
-
Looking into the C# Crystal Ball with Charlie Calvert and Bill Wagner
One of the most exciting announcements from PDC was the news about C# 4.0 and Visual Studio 2010. With all the excitement and discussion throughout the event about these new developer tools, we reached out to two experts in the fields. Charlie Calvert and Bill Wagner sat down with Keith and Woody...
Events coming up
-
Dec
6
Developing AJAX Web Applications with Castle Monorail
London, United Kingdom
Monorail is the model-view-controller engine of the Castle Project, bringing many of the best ideas of Ruby on Rails to the .NET world. In this talk, David De Florinier and Gojko Adzic show how Monorail makes it easy to develop .NET based AJAX applications, and how to use the Castle Project to build Web 2.0 applications effectively. Come to this session if you are a .NET web developer. Everyone is welcome!
forget that last post ...
I found it in my code ... non-application test code I threw in on the quick ... cause the StackOverflow.
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.
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" ?
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!!
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.
Thanks for pointing this out. I'll update the tutorial
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)
This thread is for discussions of Introducing .NET Remoting.