NET. Both have the potential to significantly improve
the reliability of web applications and ease the maintenance burden on the web administrator.
The strong-named assembly has built-in tamper-proof features, as we alluded to earlier.
During the build process for the assembly, the compiler performs a hash on the contents of
the assembly to create a digital signature. The public key information is also stored inside the
assembly, so it can be verified by the runtime when it loads the assembly or when it is installed
in the GAC. Any file tampering will cause an assembly load failure.
GAC installation provides a performance advantage over putting a strong-named assembly in
the bin directory of the ASP.NET web application, because the verification process happens
CHAPTER 12 ?– BUILDING A COMPLEX CONTROL 585
only once when the strong-named assembly is installed. If a strong-named assembly is loaded
from an application??™s bin directory, the verification takes place each time on assembly load
into an application.
Additional Assembly Attributes
As mentioned previously, additional information on the control library, such as the title, description,
company, and so on, can be configured by going to project properties and clicking the
Assembly Information button on the Application tab.
Pages:
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769