I tried once to see what folks are doing about version number strategies, and I guess I was too verbose (see
How to you manage versions in your assemblies? What's the best practice, especially under source control? I'd like to convey
major.minor.revision, stage (Alpha, Beta, Milestone, Release Candidate, & Release) iteration within stage (Beta 1, Beta 2, RC 1, RC 2) build number (incremental number within stage's iteration)
I am well aware that AssemblyVersionAttribute & AssemblyFileVersionAttribute use the convention major.minor.buildNumber.revision, which just doesn't seem to communicate much information to me without some associated cross reference from version to what
kind of release it actually is.
Your thoughts & opinions are appreciated.
http://social.msdn.microsoft.com/Forums/en/clr/thread/2c3e2bdb-f1ed-4702-af6f-c203e9642378 for a long version of this question.
View Complete Post