Michael,
I would not expect, AssemblyInformationalVersion to auto increment, as that
is the Product version! I would expect it to be a constant during rebuilds.
I would however, expect both AssemblyVersion and AssemblyFileVersion to auto
increment.
I'll check VS.NET 2005 to see if it has the same behavior, I'm not seeing
anything specific that AssemblyFileVersion should auto increment. (Only the
AssemblyVersion is documented to auto increment.)
Hope this helps
Jay
"Michael Maes" <mi*****@merlot.com> wrote in message
news:%2****************@TK2MSFTNGP11.phx.gbl...
The only pitty is that an "auto-increment" (.*) on the
AssemblyInformationalVersion-Attribute won't work. :-(
<Assembly: AssemblyVersion("2.0.0.0")>
<Assembly: AssemblyInformationalVersion("2.0")>
<Assembly: AssemblyFileVersion("2.0.0.*")>
This literally set the FileVersion to 2.0.0.* and produces a warning in the
IDE (vbc : warning BC40010: Possible problem detected while building
assembly 'Stegosoft.Diagnostics': The version '2.0.0.*' specified for the
'file version' is not in the normal 'major.minor.build.revision' format)
Michael
"Jay B. Harlow [MVP - Outlook]" <Ja************@msn.com> wrote in message
news:%2****************@TK2MSFTNGP11.phx.gbl...
Michael,
There are three "versions" you can include in your AssemblyInfo.vb file:
<Assembly: AssemblyVersion("1.0.*")> ' Assembly version
<Assembly: AssemblyInformationalVersion("1.0")> ' Product version
<Assembly: AssemblyFileVersion("1.0.*")> ' File version
If you exclude the AssemblyInformationalVersion & AssemblyFileVersion they
will default to AssemblyVersion.
For details see:
http://msdn.microsoft.com/library/de...assenamesp.asp
Hope this helps
Jay