Chapter 14-Lesson 1

• An Assembly consists of the following parts: Assembly metadata, Type metadata, IL Code, Resources.
• Assembly metadata is also called the manifest and contains information such as Strong Name, Version, Culture, etc.
• Type metadata contains information about all the classes, structs, interfaces and their members.
• Resources contain objects like images, strings, etc.
• An Assembly may consist of multiple files.
• The Assembly class is used to represent a .NET assembly in the code.
• The Load( ) static method if this class loads the specified Assembly in the current AppDomain.
• Each assembly contains one or more modules that represent containers for type information.

Chapter 8-Lesson 1

• Operating System manages processes, while .NET Runtime manages Application Domains.
• If we consider an Assembly as class, then its instances could be called Application Domains.
• If an Application uses more than one assembly, it is possible to create a seperate process for each of them. The problem would be the performance hit ad resource usage caused between context shifts from one process to another. Therefore it is better to use one Assembly that acts as a host for other Assemblies. Then we may share resources (data) among Assemblies within an Application Domain. (e.g. ASP.NET Application object is an Application Domain)
• Points-to-Ponder: (See page 439)
• AppDomain class allows for creating Application Domains within .NET
• AppDomain.CreateDomain( ) static method is used to create a new Application Domain with a friendly name, and RunAssembly( ) instance-level method is used to load an Assembly within a domain.