Essential. Net Reading Notes [Part 2]

Previous Article (http://interma.cnblogs.com/archive/2005/11/24/283814.html)

III.Chapter 2 Components

1.CLRModule inclusionCode, Metadata, and resources.CLRThe module is stillWinntOfPE/coffThe extension version of the executable file. Most of the content is stored inPE/coffFile. Text.

2.4Type of module output:EXE, winexe, library, Module. OnlyModuleCannot be deployed independently (ProgramLevel is the atomic unit of deployment), that isCLRIt cannot be loaded directly.

3.Assembly(Assembly)Is composed of one or more modules.

4.The Assembly metadata contains the Assembly List section (Assembly manifest, That is. AssemblyInstead. Assembly extern), For modules without assembly list(Module),CLROnly indirect loading is allowed.

5.Assembly4Some names (Strong names ):Name, version, culture, publickeytoken.

6.ContainCultureThe feature assembly cannot contain code. They are pure resource assembly (also knownSatelliteAssembly ). That is to say, all the Assembly containing the Code isCulture-neutral.

7.Strong name program assemblyPublic KeyAttached to the Assembly.

8.CLRAlways load the Assembly as needed. (Good feature)

9.Assembly. loadform (): Load directly through the Assembly loader (load by location), completely ignoring any version policy.

Assembly. Load (): Parse through the Assembly parser, and then load through the Assembly loader.

10. The version policy can only be used on a strongly-named assembly.

11. Version Policy3Application policy (App. config)=>Issuer Policy (Integrated Resources)=>Machine policy (Machine. config). Note that the issuer policy is generally used for components to indicate the versions of the components that can be compatible with each other. (Good feature)

12. Policy for searching assembly files:[1] GAC => [2] codebase hint (hrefLocation) => [3] probing(AppbaseDirectory and Its subdirectories)

[To be continued...]