Just Upgraded

[NewsArchive]

Just got new Setupbuilder Dev - Thanks Friedrich for all your work. A dumb
question since I have not had a chance to explore, but will 5 update a
previous 4 project.

[NewsArchive]

Hi Don

I believe that at present it can't because of the different way in which SB5
works compared to SB4.

Cheers
Simon Burrows
Visit the new Data Ferret Website
http://www.dataferret.net

[NewsArchive]

Ouch...

--

Ben E. Brady
The information contained in the message above, as expressed by the author,
is copyright 2005 by Ben E. Brady, All rights strictly reserved worldwide.
The information contained in the message above may not be posted on any
other web site, whether a fee is charged for content or provided for free,
without the express written permission of the author.

[NewsArchive]

Don,

Of course, you can still use your old SB4 installations (there is nothing
wrong with that). Because SB5 gives you so much more power and flexibility,
it's wise to "rethink" some distribution projects.

If you create new projects, I would consider SB5.

SB5 cannot open SB4 files. SB5 has a different philosophy regarding the
project management (and feature set). SB5 is completely "script driven".
SB4.x projects are limited because they are based on a sequential database
driven processing model. Something like the following:

1) Display GUI (Welcome -> Readme -> License -> etc.)
2) Install Files
3) Write Registry/INI Entries
4) Perform Actions
5) Run Programs

In contrast to SB4, the new SB5 is completely script driven. Would you like
to display the License Agreement before your Welcome dialog? No problem.
Or read some values out of the Registry and based on this information
display different sets of wizard dialogs. With SB5 you can do it. SB5
supports IF..THEN..ELSE and LOOP control structures to provide looping and
conditional execution of installation components.

You can now use the *same* script to compile *different* versions of your
installer (e.g. full or upgrade image). The SB5 preprocessor can
conditionally include lines of code within an installer program. The
directives that include code conditionally are defined in such a way that
you can construct a chain of inclusion directives to include exactly the
functions you want.

Friedrich

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

[NewsArchive]

Thanks Friedrich

The best approach. Current SB4 installs continue and gives time to work
with all the new possibilities of SB5.