By default, a new Visual Studio project is version 1.0.0.0, and doesn't change unless you manually change it.  I'd like to increment Build (the last segment) whenever the DLL is regenerated (that is, when the code changes or I choose Rebuild) in a way that can be viewed from Explorer > File > Properties.  If possible/practical, I'm also looking to put some Subversion metadata into a comment (rev, author, check-in date, build-date).

The key is it has to happen automatically when any developer builds a new Release version of a solution.  (Possibly also for Debug versions, but not necessarily.)

I did some searching on StackOverflow and MSDN and found a couple of different techniques.  The standard Microsoft way is via [assembly: AssemblyVersion("1.0.*")], but that's not so attractive because (a) it is generated from date and time of build, not an incrementing version, and (b) AssemblyVersion can't be seen from File:Properties.  I also found a couple of tools which can fiddle with AssemblyInfo.cs, typically invoked by the BeforeBuild script, but those have the disadvantage of changing the number every time, whether the DLL is regenerated or not.  Some also require the developer to have certain parsing tools installed on a specific path so they can be used by all developers.  (We don't have or foresee having a central build environment.)

To ASI: How are build versions assigned for iMIS?  Is it manually updated?  If not, how is it automated?

To solution providers and clients:  Do you have a way to autoincrement the build number?  How have you chosen to manage it?]

--

Bruce Wilson
Director, Technical Services
RSM McGladrey, Inc.