BSOD2600
18th December 2007 06:26 UTC
Why did VIProductVersion format change
The last time I built my installer, I was using v2.30. Since I've updated to v2.33 MakeNSISW dies during the last bit of the installation with:
Processed 1 file, writing output:
Adding plug-ins initializing function... Done!
Error: invalid VIProductVersion format, should be X.X.X.X
Error - aborting creation process
In all my previous versions, I have defined both numbers AND letters (i.e. 0.8.6j) and it's been fine. Now it's obviously not.
Is this a bug, or the way it's suppose to be enforced now?
Afrow UK
18th December 2007 12:38 UTC
This has always been the case as far as I know.
Stu
BSOD2600
23rd December 2007 01:07 UTC
I know for a fact, that it hasn't been enforced that way in the past. For example, here is part of my installer file from 7/26/2006 which worked fine:
!define VERSION 0.8.6h
OutFile cacti-${VERSION}.${INSTALLVER}.exe
VIProductVersion 0.8.6.0
VIAddVersionKey ProductVersion "${VERSION}"
kichik
23rd December 2007 18:37 UTC
Your code uses proper format for VIProductVersion. You're confusing it with VIAddVersionKey which supports whatever text you want.