The Philosophy of .NET


The point of this chapter was to lay out the conceptual framework necessary for the remainder of this book. I began by examining a number of limitations and complexities found within the technologies prior to .NET, and followed up with an overview of how .NET and Visual Basic 2005 attempt to streamline the current state of affairs.

.NET basically boils down to a runtime execution engine (mscoree.dll) and base class library (mscorlib.dll and associates). The common language runtime (CLR) is able to host any .NET binary (aka assembly) that abides by the rules of managed code. As you have seen, assemblies contain CIL instructions (in addition to type metadata and the assembly manifest) that are compiled to platform-specific instructions using a just-in-time (JIT) compiler. In addition, you explored the role of the Common Language Specification (CLS) and Common Type System (CTS).

This was followed by an examination of the ildasm.exe utility, as well as coverage of how to configure a machine to host .NET applications using dotnetfx.exe. I wrapped up by briefly addressing the platform-independent nature of the .NET platform and the Mono and Portable.NET CLI distributions.


Application Programming Interface Intermediate Language Component Object Model Common Language Infrastructure Type Metadata 
These keywords were added by machine and not by the authors. This process is experimental and the keywords may be updated as the learning algorithm improves.


Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.

Copyright information

© Andrew Troelsen 2006

Personalised recommendations