||Strong Naming of .NET Assemblies
||Biskopstø Strøm, Torur
||Dragoni, Nicola (Embedded Systems Engineering, Department of Informatics and Mathematical Modeling, Technical University of Denmark, DTU, DK-2800 Kgs. Lyngby, Denmark)
||Technical University of Denmark, DTU, DK-2800 Kgs. Lyngby, Denmark
||This report describes a project which was done for Edlund A/S, a company
developing software for insurance companies. The company requested an implementation, which could be used for their every day development, and test
of strong naming in their main application framework Forsikring.NET. They
wanted to know if strong naming would have any performance benets, in particular memory usage regarding scalability. They were also interested in any
security benefits that strong naming would provide.
The report covers the steps necessary to strong name PenSam, a customer solution which is a customized version of Forsikring.NET, and also the workings
of SNU, a script meant for strong named assembly handling for daily development. The problems encountered during the implementation process are covered
as well as how to address them. This implementation is then used as a reference
to implement strong naming in another customer solution and then both strong
named applications are performance tested against their respective stable versions. The report also discusses non-performance aspects of strong naming such
as how the company should handle the private part of cryptographic keys and
what security we can expect from strong naming.
The report is outlined as follows:
The Prerequisites chapter describes the necessary technological prerequisites,
e.g. what is a hash code and what is its relation to strong names. Note that
even though several technologies are descibed here, the knowledge discoveries
are listed in chronological order, i.e. the technology necessary to address an
unexpected problem is described together with the problem solution. It should
also be noted that some programming experience is expected of the reader.
Implementation contains the steps necessary to implement strong naming,
a description of SNU, as well as all encountered problems and how to address
them. How cryptographic keys should be handled is also covered in this chapter.
Performance Analysis is the test chapter. The customer solutions StablePenSam, StrongPenSam, StablePFA and StrongPFA are performance tested. The
test includes different loading time and memory usage.
The Security Limitations chapter discusses non-performance aspects of strong
naming and the security of strong naming.
Finally Conclusion sums up results and discoveries.
||Technical University of Denmark (DTU) : Kgs. Lyngby, Denmark
Creation date: 2009-11-24
Update date: 2010-08-25