CHAPTER 2 Building, Packaging, Deploying, and Administering Applications and Types

Question 1

.NET Framework Deployment Goals

Answer 1

addresses the DLL hell issue

fixing the problem of having an application’s state scattered all over a user’s hard disk

security

Question 2

MSCorLib.dll

Answer 2

MSCorLib.dll is a special file in that it contains all the core types: Byte, Char, String, Int32, and many more.

Question 3

Building Types into a Module

Answer 3

csc.exe /out:Program.exe /t:exe /r:MSCorLib.dll Program.cs

Question 4

Response Files

Answer 4

A response file is a text file that contains a set of compiler command-line switches.

The C# compiler supports multiple response files.

Question 5

PE32(+) header

Answer 5

PE32(+) header is the standard information that Windows expects

Question 6

CLR header

Answer 6

CLR header is a small block of information that is specific to modules that require the CLR (managed modules).

version number of the CLR that the module was built for
a MethodDef token indicating the module’s entry point method
an optional strong-name digital signature

contains the size and offsets of certain metadata tables contained within
the module

Question 7

metadata

Answer 7

The metadata is a block of binary data that consists of several tables.

definition tables
reference tables
manifest tables

Question 8

Common Definition Metadata Tables

Answer 8

ModuleDef
TypeDef
MethodDef
FieldDef
ParamDef
PropertyDef
EventDef

Question 9

Common Reference Metadata Tables

Answer 9

AssemblyRef
ModuleRef
TypeRef
MemberRef

Question 10

manifest

Answer 10

The manifest is another set of metadata tables that basically contain the names of the files that are part of the assembly.

They also describe the assembly’s version, culture, publisher, publicly exported types, and all of the files that
comprise the assembly.

Question 11

characteristics of assemblies

Answer 11

An assembly defines the reusable types

An assembly is marked with a version number

An assembly can have security information associated with it

Question 12

three reasons to use multifile assemblies

Answer 12

You can partition your types among separate files, allowing for files to be incrementally downloaded as described in the Internet download scenario

You can add resource or data files to your assembly

You can create assemblies consisting of types implemented in different programming languages

Question 13

Manifest Metadata Tables

Answer 13

AssemblyDef
FileDef
ManifestResourceDef
ExportedTypesDef

Question 14

Assembly Version Resource Information

Answer 14

When building an assembly, you should set the version resource fields by using custom attributes that you apply at the assembly level in your source code.

Version Numbers
Culture