SetupBuilder 6.0 Change Log [November 30, 2006]

[NewsArchive]

Just wanted to let everyone know that SetupBuilder 6.0 will be released
soon.

This is the latest Change Log SetupBuilder 6.0:

Change Log for SetupBuilder 6.0 Build 1700 (November 30, 2006)
----------------------------------------------------------------------------

Features/Improvements/Fixes/Workarounds/Changes/Notes:

FEATURE : Add "#code-sign application" compiler directive to code-sign an
application.

FEATURE : Add "#embed manifest in application" compiler directive to
embed a Vista-aware manifest in an application.

FEATURE : Add "Polish" language file (thanks to Leszek Guzowski).

FEATURE : Add "Greek" language file (thanks to Steven Sitas).

FEATURE : Add "Romanian" language file (thanks to Robert Iliuta).

FEATURE : Add "Bulgarian" language file (thanks to Artin Nigohosian).

FEATURE : Add "Requested Execution Level" option to the General
Information "Generator Settings".

FEATURE : Add support for networks in the Files and Folders Visualizer.

FEATURE : System Restore Point handling is back. The "Set System Restore
Point" script function makes it possible to create, end and
cancel system restore points on Me, XP and Vista.

IMPROVEMENT: Add "Uninstall" option to the "Copy Local File(s)" script
function.

IMPROVEMENT: Add "Do not overwrite existing files" option to the "Copy
Folder Tree" script function.

IMPROVEMENT: Add "Uninstall" option to the "Copy Folder Tree" script
function.

IMPROVEMENT: Add Subscription Key auto verification option to the Edit Data
[Multiple Line] dialog

IMPROVEMENT: Add "Remove value" option to the "Edit Registry" script
function.

IMPROVEMENT: Add "File List Filter" to the Files and Folder Visualizers "My
Computer" file list.

IMPROVEMENT: [SB#611241] Ability to create an Internet shortcut (Create
Shortcut) where the target URL is taken from a variable.

IMPROVEMENT: The General Information "Output Directory [OUPUTDIR]" property
can handle compiler variables now.

IMPROVEMENT: Add the ability to "Refresh Drives" in the "My Computer"
folders list (Files and Folder Visualizer) by selecting the "My
Computer" item and right-clicking the mouse.

IMPROVEMENT: Add "Reboot Computer System and Resume" option to the
Reboot/Resume script function. The new %_SB_RESUME% variable
value is "1" if installer resume is enabled.

IMPROVEMENT: Add "Add/Remove Scheduled Task" script function to schedule
any script, program, or document to run at a time that is most
convenient for you. Scheduled Tasks run in the background, and
it starts each task that you schedule at the time that you
specify when you create the task. This is supported under
Windows Vista, Windows XP, Windows 2000 Professional, or
Windows Me.

FIX : Uninstall compatibility issue with Windows Vista build 6000.

FIX : SetupBuilder IDE compatibility issue with Windows Vista build
6000.

FIX : [SB#611021] Possible (undetected) installer buffer overrun
issue.

FIX : "Delete Tree" script function did not check for undefined
variables.

FIX : [SB#611131] Get System Information (Current Date) returned
'02i/mm' (instead of mm/yy) for format 13 and 'yy/02i'
(instead of yy/mm) for format 15.

FIX : [SB#611171] In certain isolated circumstances, the installer
did not resolve variable names.

FIX : "Target Operation Filter" did not work in the Run Program
dialog.

FIX : In certain isolated circumstances, the Cancel button on the
"Do you want to save the changes" message box was not working
as expected.

FIX : Files and Folders Visualizer: various fixes in the source
folder list.

CHANGE : Default SetupBuilder 6 project file extension is .sb6 now.

CHANGE : Various internal IDE modifications to support Windows Vista
build 6000 (Mixed User Application classification - IDE runs
as a Standard User or Administrator).

CHANGE : Private Include Scripts are located in the common repository
for application-specific data now. A typical path is
C:\Documents and Settings\username\Application Data.

CHANGE : "#include script" compiler directive supports both "Core" and
"Private" include scripts now.

CHANGE : Rename all SB5_* compiler variables to SB_*.

CHANGE : Rename SB5_RES compiler variable to SB_REDIST.

CHANGE : SB_TMP, and SB_UNZIP compiler variables point to the common
repository for application-specific data now.

CHANGE : "Product Version" field in iDeploy Web Update Properties is
not supported any longer.

CHANGE : Add [PRODUCTVER] compiler variable quick update option to the
iDeploy Web Update Properties.

CHANGE : Move "Check Interval (days)", "Encrypt Username/Password" and
"Store Properties in INI File" from the "Enable Web Install"
item to the "Install Web Update Client" item.

CHANGE : Hide the "Digital Signature Key Password" on the screen by
masking it.

CHANGE : User Info Dialog Properties: removed "Auto Verify Serial
Number" checkbox from the Advanced tab. This option is
available in the Serial Number Tab now.

CHANGE : When creating new projects, the SV_IPDATASERVER compiler
variable is not created any longer.

CHANGE : New "Get Started" page.

CHANGE : New "Wait Dialog Properties" dialog.

CHANGE : New "Wizard: Set Control Properties" dialog.

CHANGE : The browse button in the "#include script" compiler directive
supports "Core Include Scripts" and "Private Include Scripts".
Separate include script locations are required because you
don't have write access to the Program Files folder under
Windows Vista any longer.

CHANGE : New method to execute installers from the IDE (Test and Run)
to support Vista.

CHANGE : Remove "Wizard Auto Break" control statement. The compiler
generates the wizard event processing feature automatically
now.

CHANGE : Rename "Reboot/Restart System" script function to
"Reboot/Resume".

CHANGE : Rename "Handle System Restore Point" script function to
"Set System Restore Point.

CHANGE : Rename "Handle Delayed File Install" script function to "Set
Delayed File Install"

CHANGE : Updated online help.

CHANGE : Updated PDF manual.

CHANGE : Updated wupdate.exe (including wupdate.sb6) web update client.
The default wupdate.exe is code-signed by Lindersoft now.

CHANGE : Increment version number to 6.0.

----------------------------------------------------------------------------
----------------------------------------------------------------------------

Regards,

Friedrich Linder
Lindersoft
www.lindersoft.com
+1.954.252.3910

"point. click. ship" - that's SetupBuilder 6
Create Windows Vista ready installations in minutes

[NewsArchive]

Friedrich,
Will the #code-sign application and #embed manifest in application
directives be specifiable?
IOW, if an installer contains multiple .EXE files, can SB sign/manifest each
of them or certain ones?

Jane

[NewsArchive]

Jane,

Yes, no problem. You can code-sign / embed Vista manifest and unlimited
number of .EXE files. You can even code-sign / embed Vista manifest .EXE
files that do not go into the setup.exe.

Friedrich

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

"point. click. ship" - that's SetupBuilder 6
Create Windows Vista ready installations in minutes

[NewsArchive]

Excellent! :)

Jane Fleming

[NewsArchive]

:) BTW, it looks like this (see attached screenshot).

Friedrich

[NewsArchive]

Ouch.
I'm toooo old to keep trying to learn new stuff!!!
<g>

Jane Fleming

[NewsArchive]

<BG>

Friedrich

[NewsArchive]

Friedrich,

Any chance of having some DLL which we can interface with our applications
to generate maintenance keys?
For our next products, I would like to go with a 100% iDeploy system.
I have our own registration server, in which we keep the maintenance
expiration date, serial number, etc.

The work flow which I would like to accomplish is as follows:

1. Base version setup progam installs the base release.
2. Our product accesses our registration server, which returns a series of
codes. One of them is an activation code (I use SecWin), the other would be
a mintenance code. Our program would then create the registry key entry
with the maintenance code which allows wupdate to download updates for as
long as the maintenance key is valid.

Currently I would have to manually generate these keys, which are tied to
the serial number of the product, so it has kept me from implementing
iDeploy (or SB5 for that matter). iDeploy is one of the main reasons for my
upgrading to SB5. Not being able to automate this process has kept me with
SB4 for the time being.

In order to scale, we need to be able to automate this process.

Regards,

Benjamin

[NewsArchive]

Benjamin,

Yes, Charles and I are working on RegKISS integration. As part of this
integration process, we'll add a solution to SB6 to handle maintenance key
generation from your application(s).

We'll make additional information available soon.

Friedrich

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

"point. click. ship" - that's SetupBuilder 6
Create Windows Vista ready installations in minutes