Remoting is Whacky!

This week I resumed my 70-310 studies and finished off the chapters on Windows Services and Serviced Components.  These were both very valuable areas of learning for me and, along the way, many of the questions that I'd had in the past - particularly about COM+ services - got cleared up.

I also spent a good amount of time "burrowing" into the next section with is on - <insert sinister sound /> - Remoting.  From 40,000ft I have no real trouble understanding the various Remoting pieces and how they fit together; it's when you hit the ground and understand the finer details that your head simply starts to spin.

I think that my biggest problem with Remoting is that I just don't get it!  All of the apps that I build are like the starter kits (TaskVision, ASP.NET Starter Kits, etc) where Remoting just isn't considered a part of the picture.  If you need a Type, you just reference it in your Project!

Hopefully, by the end of this section I will have been liberated to the virtues of this little-understood piece of .NET framework architecture.

P.S.  While I'm working through the chapter I've also got 1 eye on the Remoting FAQ's that Ingo has created.