PDA

View Full Version : Variable Substitution on Dialog Title



NewsArchive
01-13-2006, 05:38 AM
Hi,

Just discovered that although the variable I'm using in [PRODUCTNAME] gets
resolved on the initial dialog (and seems to throughout the setup process),
it does not appear properly on the cancel message box as shown in the
attached screen shot.

Small thing, but hopefully can be fixed...

SB Dev 5.2.1354
-Brian

NewsArchive
01-13-2006, 05:51 AM
Brian,

This is not a bug (it's a documentation problem). Please do not use runtime
variables in [PRODUCTNAME], [PRODUCTVER], [APPTITLE], [PRODUCTGIUD],
[UPGRADEGUID] or [EXENAME]. Unfortunately, this information is missing in
the documentation. The above items are used before the script engine is
executed.

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

"point. click. ship" - that's SetupBuilder 5

NewsArchive
01-14-2006, 04:07 AM
Thanks for the reply Friedrich,

Let me give you a quick rundown of what I'm up to with this...

The scenario is that some data is being archived for a given year from the
primary SQL database to a newly created SQL database, then essentially
purged.

Then it burns a CD with the newly created database files, an autorun.inf
file and a previously created SB5 install for the product. The idea here
is that the user can drop the CD into any PC, run the install and access the
archived data.

My idea was to customize the install process with the year so that users
could install/uninstall archived years as necessary without affecting their
primary product install. With that in mind, the archived year is planted in
the autorun.inf file and the SB5 install retrieves it and uses throughout
the install for appending to the product name, installation directory, and
so forth.

However, if I'm really not able to add the year, it's a showstopper for me.
I need to be able to create unique installations for accessing archived data
based on a calendar year. If I can't use a variable in [PRODUCTNAME], then
the user won't be able to uninstall just the year they are no longer
interested in accessing, or am I missing something...

And... so far it is working with the exception of the Cancel dialog...

Thanks,
-Brian

NewsArchive
01-14-2006, 04:07 AM
Brian,

The uninstall process is not based on the [PRODUCTNAME]. In Windows, there
is always a GUID behind the uninstaller. Without a unique Product GUID,
it's not possible to have an uninstaller based on the calendar year.

Even if it would be possible to use a variable in [PRODUCTNAME], the GUID
for 2005, 2006, 2007, etc. would be the same and so a, say, year 2007
installation would overwrite the 2006 uninstall information.

Of course, there is no problem to read the year from a file and use this
in the installation folder.

Does this help?

Friedrich

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

"point. click. ship" - that's SetupBuilder 5

NewsArchive
01-14-2006, 04:08 AM
Thanks, I guess I would have been in trouble anyways then... For some reason
I was thinking product name had something to do with it, which is why I've
been avoiding putting version numbers in the product title, (I was thinking
to avoid duplicate entries in Add/Remove Programs, but maybe that was an old
version, or a different installer...).

When is the GUID for a given install picked, and once picked, does it ever
change for a given SB5 project?

Thanks,
-Brian

NewsArchive
01-14-2006, 04:08 AM
Never mind, found the info on the General Information Tab...

Thanks,
-Brian

NewsArchive
01-14-2006, 04:08 AM
Hi Brian,

The GUID should not change for a product or a specific product version.

For example, {B1C06C90-696B-11D9-72AE-01631BD32CD6} is the Product GUID
for SetupBuilder 5 Professional and{4D910660-BBBC-11D8-6784-02015E7D18BE}
the GUID for the Developer Edition. It will not change for all version
5 releases. We'll use different GUIDs for Version 6, Version 7, etc.

But you can change the GUID for a product - in this case it is wise to
provide an automatic uninstall feature (to uninstall the old version)
and then install the new(er) product with a different GUID.

If you are interested, please send me again more detailed information
and I'll give this some thoughts over the weekend. Your description
was very good, but perhaps you have further information.

Friedrich

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

"point. click. ship" - that's SetupBuilder 5

NewsArchive
01-14-2006, 04:08 AM
Hi Friedrich,

After reconsidering for a bit, I don't think this will be a problem for me.

I think I'll drop the year altogether, since my intention is to use the same
installer for any given year, and the installer is already different from
the one used to install the regular version of the product since it must
install a personal version of the server and the archived database itself.

I doubt it will be a big problem that they'll only be able to access one
archived year at a time on any given machine.

Thanks for clearing this up...
-Brian