C# 4 and .NET 4

summary ❘ 459
Version dependencies are exactly recorded so that with assemblies, the DLL hell of old DLLs no longer
exists. Because of these features, development, deployment, and administration have become a lot easier.
You learned the differences between private and shared assemblies and saw how shared assemblies can
be created. With private assemblies, you don’t have to pay attention to uniqueness and versioning issues
because these assemblies are copied and only used by a single application. Sharing assemblies requires you
to use a key for uniqueness and to define the version. You looked at the GAC, which can be used as an
intelligent store for shared assemblies.
You can have faster application startups by using the native image generator. With this the JIT compiler
does not need to run because the native code is created during installation time.
You looked at overriding versioning issues to use a version of an assembly different from the one that was
used during development; this is done through publisher policies and application configuration files. Finally,
you learned how probing works with private assemblies.
The chapter also discussed loading assemblies dynamically and creating assemblies during runtime. If you
want to get more information on this, you should read about the plugin model of .NET 4 in Chapter 28,
“Managed Extensibility Framework.” To use a plugin model with the advantage of app-domains, see coverage
of the System.Addin namespace in Chapter 50, “Add-Ins.”
www.it-ebooks.info