Titlebook: C# and the .NET Platform; Andrew Troelsen Book Jun 20032nd edition Apress 2003 .NET..NET framework.C#.Windows.XML.interfaces.language.obje

運(yùn)氣

isotope

Emmenagogue

Object Serialization and the .NET Remoting Layerave nothing to do whatsoever with XML Web services (or Web applications). In short, using.NET you are able to build peer-to-peer distributed applications that have nothing to do with HTTP or XML (if you so choose). As you will see over the course of this chapter, the.NET Remoting architecture is a managed replacement for classic DCOM.

小卷發(fā)

Exceptions and Object Lifetimeu will also come to understand the distinction between . and . exceptions. This discussion will also provide a lead-in to the topic of building custom exception types, as well as how to leverage the built-in exception handling functionality of Visual Studio .NET.

昏暗

消耗

s include:.Coverage of building custom components and controI REMEMBER A TIME years ago when I proposed a book to Apress regarding a forthcoming software SDK named Next Generation Windows Services (NGWS). As you may already know, NGWS eventually became what we now know as the . NET platform. My rese

受辱

https://doi.org/10.1007/978-1-349-02632-6oftware development, eventually become overshadowed by something better or at very least something new. Regardless of the frustration you can feel when upgrading your internal knowledge base, it is unavoidable. Microsoft’s .NET platform represents the latest wave of (positive) changes coming from those kind folks in Redmond.

手段

https://doi.org/10.1007/978-1-349-02632-6uch as MFC and ATL 4.0). Furthermore, if you download or purchase additional .NET-aware languages (such as COBOL .NET, Eiffel .NET and so forth), the chances are quite good that they will ‘snap-in’ to the existing VS .NET IDE out of the box.

DOSE

冒失