| Distributed .Net Programming in C# Contributor(s): Barnaby, Tom (Author) |
|
 |
ISBN: 1590590392 ISBN-13: 9781590590393 Publisher: Apress OUR PRICE: $44.96 Product Type: Paperback - Other Formats Published: May 2002 Annotation: With the release of .NET, Microsoft has once again altered the distributed programming landscape. Almost everything has changed, from data access, to remote object calls, to the deployment of software components. And of course, .NET introduces a new technology in XML Web services that may revolutionize Web development. "Distributed .NET Programming in C#" describes how to use these new .NET technologies to build fast, scalable, and robust distributed applications. Along the way, it answers common questions such as, How do I use the .NET Remoting Framework? What role does COM+ play in the .NET universe? How can I interoperate with COM components? What's the difference between .NET Remoting and Web services? How will these changes affect the architecture and design of a distributed application? Author Tom Barnaby assumes the reader is already familiar with the fundamentals of .NET. However, a .NET overview is provided to concisely explain several of the core .NET technologies that are essential for distributed programming, including building, versioning, and deploying assemblies; garbage collection; serialization; and attribute-based programming. |
| Additional Information |
| BISAC Categories: - Computers | Programming Languages - General - Computers | Programming - Microsoft - Computers | Software Development & Engineering - General |
| Dewey: 005.133 |
| Series: .Net Developer |
| Physical Information: 1.3" H x 7.86" W x 8.8" (2.33 lbs) 528 pages |
| Descriptions, Reviews, Etc. |
| Publisher Description: 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. |