Assembly Versioning

N

Nate Bross

Contributor
Joined
Apr 6, 2005
Messages
601
Location
Chicago, IL
Quite possibly this is common knowledge and I'll look stupid for posting this; however, I recently came across this and thought it was an eloquent way to describe how .NET versioning works from the perspective of the “Project Properties” screen in Visual Studio.

The CLR will always bind to the same major/minor version as what it was compiled against. For example, if the version number is 1.2.3.4, the major/minor version is 1.2. However, the versioning model will support servicing. This allows the developers to build a new version of the assembly and only change the build/revision portion of the assembly. In the previous example, that would be 3.4. The CLR will always load the latest "servicing" version of an assembly, allowing developers to provide updates to assemblies without requiring publisher policy files or binding redirects.
Click to expand...

Full Text Article
 
Back
Top