When developing an ASP.NET application, you can package the code into a variety of processes according to a class of processing according to the specific needs and designs developed. And organize and manage existing code. This creates a lot of assemblies in the ASP.NET application (that is, the DLL file formed after compiling).
In these contexts, many packages for the underlying code, do not involve the application's transaction logic, then it is possible to repeatedly apply in various applications (reuse of the code). For example, a package for various common database operations form a class specifically for database operations, then this class is available in all applications that require databases. There is also a problem with it, which may make some corresponding changes in a variety of different applications, then with the increase in the number of assemblies, the number of modifications will be released. There are a lot of trouble. Even if some of the assemblies are only used by an application, they may have different versions due to their modifications, resulting in the same version. In the usual development, this is often encountered, and the adjustment of a certain code can always produce expected results, and the error is found, and finally found that some of the code used in the program set used is modified. . A few days ago, I have written a document on the sequence of the assembly, and I said that some of my personal suggestions, I hope to have a certain reference value. First, we need to have a label, version number for identifying different versions of the assembly. In the MSDN's description of the version number, it is recommended to use a version number format consisting of four parts. [Majorversion.minorversion.buildNumber.revision], the specific description of these four parts is as follows: (main version or subsection. Changes made to the main version of the version number indicate incompatible changes. Therefore, in this Under the appointment, version 2.0.0 is considered is not compatible with the 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.2, or the entire removal of a type or method belongs to an incompatible change. Invical version. Internal version number is usually used Distinguish the daily version or a smaller compatible version. Revision number. Revision number change is usually reserved for the incremental compilation required to repair a particular error. Sometimes you hear it is called "emergency error repair No. Since the change is usually amendment number when sending to a particular error is sent to a particular error.) Part is taken from MSDN in the above parentheses. Of course, the format of this version number can be appropriately adjusted according to the different actual needs. The version number of the version I use is: [Primary version number. Supreme version number. Program compilation time. Number of modifications], where the main version number is used to identify a large change, the secondary version number is used to identify smaller changes, Compiling time is used to identify the time of the assembly to be compiled, and the number of modifications is used to identify the assembly several times. The lower half will mainly tell two options for the control of the version.
