Resource Information - bug?

[Steve_K]

The new 'Custom version information' feature was something we all were waiting for, but I seem to be unable to use

%ProductVer%

in the 'FileVersion' and 'Product Version' boxes of the 'Custom Version Information' section. After compiling the setup, the version info reads 0.0.0.0 - is that by design, or a bug?

Can't I use the %ProductVer% varaible to dynamically set the version info? If not, this 'new feature' is kind of useless as it is a pain to remember to manually edit the information for each update I build.

Thanks.

[Mark]

Hi Steve_K

If you are looking for dynamic custom version information use design-time constants. You can use the same desing-time constant for the %ProductVer% value and the custom version information.

Session variables are dynamic and meant for the runtime, while design-time constants are meant for design and build times.

[Steve_K]

Will try that. Thanks!

[Steve_K]

OK, tried that, but how do I get a design-time constant to be equal a session variable? Sorry for being a pain ... the help file does not tell me anything about that.

[Mark]

Hi Steve_K,

The trick is to use the design-time constant for the value of %ProductVer%.

[Steve_K]

Sure - didn't get that.

[Maind]

I have try with Setup Factory 8.0.
I have created a constants #VER# and I have assigned %ProductVer%.
Afrer I have write on resources the constant #VER# on Comments Line, but the result are %ProductVer%.

Any solution?

Thanks

[Ulrich]

You should use the design time constant to set the session variable, not the other way around. Perhaps this is what you are doing?

Ulrich

[Maind]

I can't do the opposite?
I would like assign to constant the value into the session variables.

Thanks
Andrea

[jcuster]

Originally Posted by Mark

Hi Steve_K

If you are looking for dynamic custom version information use design-time constants. You can use the same desing-time constant for the %ProductVer% value and the custom version information.

Session variables are dynamic and meant for the runtime, while design-time constants are meant for design and build times.

Sorry to pipe in here, but how can constants be dynamic, Design-Time or otherwise?

Simple method
1. Define Constant #VER# in Build Configuration
2. Set %ProductVer% to #VER# in Settings/Session Variables
3. Use #VER# in the 'Custom version information'
4. Use %ProductVer% in the action scripts

This will allow you to only have to change the Product version in the Build Configuration/#VER#. The Action scripts can not modify the Product Version/#VER# but can still manipulate the %ProductVer% during runtime.

[Maind]

Originally Posted by jcuster

Sorry to pipe in here, but how can constants be dynamic, Design-Time or otherwise?

In fact I had not understood how it was possible.
Now I have understand.
Thanks.

Andrea