Versioning is a very special feature of .NET framework. - In Versioning we can create the assemblies with same name. - The assemblies uses version to differentiate with each other. - A version contains 4 integers separated by dot (.). - Like e.g. 10.23.9.8. - In above e.g. the different integer’s values have different means. - Like we can analyze it 10.23.9.8 [major version. Minor version. Revised version. new version]. So here is 10 is major version of an assembly.
For strongly named assemblies(A strong name consists of the assembly's identity—its simple text name, version number, and culture information (if provided)—plus a public key and a digital signature.), the version of a referenced assembly is stored in the referring assembly, and by default only this exact version will be loaded at run-time. If the exact version is not available, the referring assembly will fail to load. It is possible to override this behaviour in the config file for the referring assembly - references to a single version or a range of versions of the referenced assembly can be redirected to a specific version.
For example, versions 1.0.0.0 to 2.0.0.0 can be redirected to version 3.0.125.3. However note that there is no way to specify a range of versions to be redirected to.
GAC - allows the publisher of the assembly to redirect all applications to a new version of an assembly in one operation
Versioning concept is only applicable to global assembly cache (GAC) as private assembly lie in their individual folders.
Versioning is the process of assigning unique numbers for creation and management of multiple releases of a product.For example a same product is released in multiple versions each of which have the same general functionality but the higher versions may be upgraded or improved.
In software versioning, subsequent releases of a specific product receive numerical identifiers consisting of two or three numbers.The first number is increased when there are significant improvements or changes in functionality.
Versioning can't be applied to private assembly. For multiple versions to coexist it needs to be deployed in GAC.
This group is an initiative from "Vidya Vrat Agarwal" a .NET Passionate. This group is created with a vision to encourage and help people learn Microsoft .NET technology. This group also provides a platform to share ideas, thoughts and experiences an individual may have while learning and implementing .NET technologies.
2 comments:
Versioning is a very special feature of .NET framework.
- In Versioning we can create the assemblies with same name.
- The assemblies uses version to differentiate with each other.
- A version contains 4 integers separated by dot (.).
- Like e.g. 10.23.9.8.
- In above e.g. the different integer’s values have different means.
- Like we can analyze it 10.23.9.8 [major version. Minor version. Revised version. new version]. So here is 10 is major version of an assembly.
For strongly named assemblies(A strong name consists of the assembly's identity—its simple text name, version number, and culture information (if provided)—plus a public key and a digital signature.), the version of a referenced assembly is stored in the referring assembly, and by default only this exact version will be loaded at run-time. If the exact version is not available, the referring assembly will fail to load. It is possible to override this behaviour in the config file for the referring assembly - references to a single version or a range of versions of the referenced assembly can be redirected to a specific version.
For example, versions 1.0.0.0 to 2.0.0.0 can be redirected to version 3.0.125.3. However note that there is no way to specify a range of versions to be redirected to.
GAC - allows the publisher of the assembly to redirect all applications to a new version of an assembly in one operation
Versioning concept is only applicable to global assembly cache (GAC) as private assembly lie in their individual folders.
Versioning is the process of assigning unique numbers for creation and management of multiple releases of a product.For example a same product is released in multiple versions each of which have the same general functionality but the higher versions may be upgraded or improved.
In software versioning, subsequent releases of a specific product receive numerical identifiers consisting of two or three numbers.The first number is increased when there are significant improvements or changes in functionality.
Versioning can't be applied to private assembly. For multiple versions to coexist it needs to be deployed in GAC.
Post a Comment