1. Use version control of your assembly
Make sure you have a proper version control policy, and you can use the assembly version attribute at compile time to apply the version flag, for example:
[Assembly: Assembly Version ("1.0.12.34")]
The same version number is typically applied to an application during the build process.
2. Take a strong name for the Assembly
Assemblies are the smallest unit of version control and code reuse, including:
Assembly identity Information (name, version, etc.)
Inventory and Meta data information
MSIL code
Type and security information
Resources
An assembly with a strong name can uniquely identify it with its version information, zone information, and digital signature.
can be used. NET Framework provides a utility (Sn.exe) for your assembly to create a strong name, this utility requires you to provide a key file as a parameter, the result file is called the "Strong name" file, you can use the Sn.exe tool from the command line to create a strong name key file, such as:
SN--k mycompany.snk
When you execute the previous command, you will see the output of the content as shown in Figure 1.
"51CTO Exclusive Translation" explores some of the best practices in asp.net application development, which can improve your application performance by following these useful procedures. This article presents eight best practices that you can follow when developing asp.net applications in production patterns.
1. Use version control of your assembly
Make sure you have a proper version control policy, and you can use the assembly version attribute at compile time to apply the version flag, for example:
[Assembly: Assembly Version ("1.0.12.34")]
The same version number is typically applied to an application during the build process.
2. Take a strong name for the Assembly
Assemblies are the smallest unit of version control and code reuse, including:
Assembly identity Information (name, version, etc.)
Inventory and Meta data information
MSIL code
Type and security information
Resources