MOMENTAN AUSVERKAUFT
Über dieses Produkt
Product Identifiers
PublisherApress L. P.
ISBN-101590590686
ISBN-139781590590683
eBay Product ID (ePID)2343332
Product Key Features
Number of PagesXxvi, 552 Pages
LanguageEnglish
Publication NameDistributed .net Programming in Vb. Net
Publication Year2002
SubjectSystems Architecture / Distributed Systems & Computing, Software Development & Engineering / General, Programming Languages / Visual Basic, Programming / Microsoft
FeaturesNew Edition
TypeTextbook
AuthorTom Barnaby
Subject AreaComputers
Series.net Developer Ser.
FormatTrade Paperback
Dimensions
Item Weight39.6 Oz
Item Length9.3 in
Item Width7 in
Additional Product Features
Intended AudienceScholarly & Professional
LCCN2005-297782
Number of Volumes1 vol.
IllustratedYes
Edition DescriptionNew Edition
Table Of ContentThe Evolution of Distributed Programming.- This is .NET.- Introduction to .NET Remoting.- Distributed Programming with .NET Remoting.- Additional Remoting Techniques.- Understanding XML Web Services.- Understanding COM Interop.- Leveraging Component Services.- .NET Message Queuing.- Appendix: Data Access with ADO.NET.- Index.
SynopsisWith the release of .NET, Microsoft once again altered the distributed programming landscape. Almost everything changed, from data access, to remote object calls, to the deployment of software components. And of course, .NET introduced a new technology in XML Web services that revolutionized Web development. Distributed .NET Programming in VB .NET describes how to use these .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., 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 of DCOM (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., 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 of DCOM (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.
LC Classification NumberQA76.76.M52
