2. Agenda [email protected]
2
Assembly Build numbering
Best practices
Assembly Strong names
Best practices
Recommendations
3. Assembly Names [email protected]
3
Assembly names in .NET framework consist of 4 parts
The short name.
On Windows this is the name of the Portable Executable file without
the extension.
The culture.
This is an RFC 1766 identifier of the locale for the assembly. In
general, library and process assemblies should be culture neutral;
the culture should only be used for satellite assembliesas part of
localization deployment effort.
The version.
This is a dotted number made up of 4 values major, minor, build,
& revision.
A public key token.
This is a 64-bithash of the public key which corresponds to the
private key used to sign[1] the assembly. A signed assembly is said
to have a strong name.
Major version: The component owner usually assigns this number.
It should be the internal version of the product. It rarely changes
during the development cycle of a product release.
5. Minor version: The component owner usually assigns this
number. It is normally used when an incremental release of the
product is planned instead of a full feature upgrade. It rarely
changes during the development cycle of a product release.
6. Build number: The build team usually assigns this number
based on the build that the file was generated with. It changes
with every build of the code.
7. Revision: The build team usually assigns this number. It can
have several meanings: bug number, build number of an older file
being replaced, or service pack number. It rarely changes. This
number is used mostly when servicing the file for an external
release.
