We have two main options:
??? Manually version code by releasing weak-named assemblies with documentation and
hope consumers use the correct version.
??? Take advantage of the built-in versioning in .NET available to strong-named assemblies,
which ensures that the correct version of code is being used and provides a flexible policy for
upgrade scenarios.
Although the process of taking a standard or weak-named assembly and converting it to a
strong-named assembly isn??™t instant, it is pretty simple to do. Right-click the project in Solution
Explorer, and select Properties. Click the Signing tab, and check the ???Sign the assembly???
box. In the ???Choose a strong name key file??? drop-down, select New to create a strong name key
file in the project directory and update the project to ensure the generated assembly is signed.
To set the assembly version, open the project??™s properties, and click the Assembly Information
button on the Application tab to fill in the assembly version, file version, title, and company
information.
The final piece of information needed for making a strong-named assembly is the culture.
The recommended culture setting for a primary assembly is the invariant culture, or a culture
name with a blank string.
Pages:
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767