#13 Off by one error in class version number

[FjK]

I just compiled a new version of my DLL and updated the
documentation from that new DLL The version in the dll
is labeled as 1.0.0.38. However, the front page of the
VBDox documentation reports version 1.0.39. Now, the
problem is not that VBDox can't read the VBP file
right, because here's the current contents of the vbp:

[snip]
MajorVer=1
MinorVer=0
RevisionVer=39
AutoIncrementVer=1
[/snip]

When auto increment is enabled, VB will increment the
version number AFTER it compiles a new version. (ie.
the revision in the vbp file is the next revision
compiled). Thus, VBDox needs to take that into account
to report the version correctly. When
AutoIncrementVer=1, subtract 1 from the Revision
version to ensure the correct version appears in the
documentation.