Get Free Shipping on orders over $79
Distributed .Net Programming in C# : .Net Developer - Tom Barnaby

Distributed .Net Programming in C#

By: Tom Barnaby, Andrew Troelsen (Foreword by)

Paperback | 30 June 2010

At a Glance

Paperback


$69.99

or 4 interest-free payments of $17.50 with

 or 

Ships in 5 to 7 business days

COM ON A WIRE, also known as DCOM, was a great boon to the distributed pro- grammer. Under the model ofDCOM, a client was able to interact with COM objects located literally anywhere, without requiring a change of code base. Using the indi- rection provided by AppiDs, stubs, proxies, and channels, our distributed endeavors involved little more than the use of declarative tools such as dcomcnfg.exe and the Component Services snap-in. However, all was not well in the world ofDCOM (or COM for that matter). Although the clicking of check boxes made COM-based remoting appear quite simple on the surface, we suffered through numerous registry conflicts, a lifetime of passing interface pointers by reference, and the dreaded prospect of crossing firewalls. Just as ADO.NET has nothing to do with classic ADO, the .NET Remoting story has nothing to do with classic DCOM. The most obvious case in point is the fact that .NET assemblies are not registered with the system registry. Given this, we have no AppiD. Without an AppiD, we have no RemoteServerName value, which means no reference to oleaut32.dll and thus no more COM-based stub and proxies. In short, everything we knew about interacting with types across the wire has changed dramatically.

More in Microsoft Programming

C# 12 in a Nutshell : The Definitive Reference - Joseph Albahari

RRP $133.00

$64.75

51%
OFF
VBScript in a Nutshell 2e : In a Nutshell - Paul Lomax

RRP $95.00

$47.75

50%
OFF
Programming F# 3.0 : OREILLY AND ASSOCIATE - Chris Smith

RRP $85.75

$43.75

49%
OFF
Programming C# 12 : Build Cloud, Web, and Desktop Applications - Ian Griffiths