How to format [PRODUCTVER] for use with vucheck.exe

[NewsArchive]

Hi,

I have this in my server manifest file:

[SB5UPDATE]
Version=2/2010
Setup=ism_dokumenter.exe

The versioning goes like this:

2/2010
3/2010
1/2011


Wucheck.exe detects correctly the change from the first to the second
version but NOT from the second to the third.

I realise that this is not a standard way of formatting a revison no. (this
is origination from a document management system) but any way that I can
make wucheck.exe accept this ?

Cheers
/Poul

[NewsArchive]

Hi Poul,

I'm curious......

Why are you using this type of version format in your installer?

If it were me I'd keep it simple and use what the installer is designed
to be comfortable with. (AA.BB.CCCC.DDDD)

Regards,

Lee
www.cya2day.com

[NewsArchive]

Poul,

> I have this in my server manifest file:
>
> [SB5UPDATE]
> Version=2/2010
> Setup=ism_dokumenter.exe
>
> The versioning goes like this:
>
> 2/2010
> 3/2010
> 1/2011
>
>
> Wucheck.exe detects correctly the change from the first to the second
> version but NOT from the second to the third.
>
> I realise that this is not a standard way of formatting a revison no.
> (this is origination from a document management system) but any way that I
> can make wucheck.exe accept this ?

What Lee said.

In Windows, "2/2010" is an invalid file version format. It should be
"AA.BB.CCCC.DDDD" where AA is the major version, BB is the minor version,
CCCC is the build version, and DDDD is optional and ignored.

The SetupBuilder version comparison supports version strings of the form
aaaaaa.bbbbbb.cccccc.dddddd. Version strings are compared in the order of
major version, minor version, build number, and revision. Each value of the
major version, minor version, build number, and revision is compared
separately as an integer

Friedrich

--
Friedrich Linder
Lindersoft
www.lindersoft.com
+1.954.252.3910

SetupBuilder is Windows 7 installation -- "point. click. ship"

-- Official Comodo Code Signing and SSL Certificate Partner

[NewsArchive]

Hi Lee & Frederich,

Thanks for the info - I guess it was as expected :-)

As I said: this is not a traditional versioning scheme for a program but
versioning of a collection of documents.

Will this format work:
1.2010
2.2010
3.2010
1.2011
etc.

I note only two integers in major & minor segments: "AA.BB.CCCC.DDDD" ?

Cheers
/Poul

[NewsArchive]

Poul,

> Thanks for the info - I guess it was as expected :-)
>
> As I said: this is not a traditional versioning scheme for a program but
> versioning of a collection of documents.
>
> Will this format work:
> 1.2010
> 2.2010
> 3.2010
> 1.2011
> etc.
>
> I note only two integers in major & minor segments: "AA.BB.CCCC.DDDD" ?

Well, from the technical point-of-view, it would work. SetupBuilder version
comparison supports version strings of the form aaaaaa.bbbbbb.cccccc.dddddd.

But it will not work from the logical point-of-view. Please note that
version 3.2010 is "larger" (or "newer") than 1.2011 ;-)

What about:

2010.1
2010.2
2010.3
2011.1
etc.

Friedrich

--
Friedrich Linder
Lindersoft
www.lindersoft.com
+1.954.252.3910

SetupBuilder is Windows 7 installation -- "point. click. ship"

-- Official Comodo Code Signing and SSL Certificate Partner

[NewsArchive]

Noted.

Thanks.

/Poul