Summary
This chapter drilled down into the details of how the CLR resolves the location of externally referenced assemblies. You began by examining the content within an assembly: headers, metadata, manifests, and CIL. Then you constructed single-file and multifile assemblies and a handful of client applications (written in a language-agonistic manner).
As you have seen, assemblies may be private or shared. Private assemblies are copied to the Client’s subdirectory, whereas shared assemblies are deployed to the Global Assembly Cache (GAC), provided they have been assigned a strong name. Finally, has you have seen, private and shared assemblies can be configured using a client-side XML configuration file or, alternatively, via a publisher policy assembly.
Access this chapter
Tax calculation will be finalised at checkout
Purchases are for personal use only
Preview
Unable to display preview. Download preview PDF.
Rights and permissions
Copyright information
© 2005 Andrew Troelsen
About this chapter
Cite this chapter
(2005). Introducing .NET Assemblies. In: Pro C# 2005 and the .NET 2.0 Platform. Apress. https://doi.org/10.1007/978-1-4302-0060-4_11
Download citation
DOI: https://doi.org/10.1007/978-1-4302-0060-4_11
Publisher Name: Apress
Print ISBN: 978-1-59059-419-3
Online ISBN: 978-1-4302-0060-4
eBook Packages: Professional and Applied ComputingProfessional and Applied Computing (R0)Apress Access Books