Missing feature

[NewsArchive]

Hi Friedrich,

bevor We switched to SB, we have used Installshield 2008. There was a
feature, that I'm missing in SB: For patch creation, you can just point
to one ore more existend single-exe-setups containig previous versions
and IS creates a patch setup for this versions. Is it possible to this
in SB?

Markus

[NewsArchive]

Hi Markus,

> bevor We switched to SB, we have used Installshield 2008. There was a
> feature, that I'm missing in SB: For patch creation, you can just point to
> one ore more existend single-exe-setups containig previous versions and IS
> creates a patch setup for this versions. Is it possible to this in SB?

No, SetupBuilder compiles native Win32 setup.exe files. So you can't just
point to the setup applications and generate a "patch".

BTW, this will also not be available in the future. For security reasons,
you can't simply "extract" files from within a setup.exe without running it.

HTH,

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

SetupBuilder "point. click. ship"
Create Windows Vista ready installations in minutes

-- Official Comodo Code Signing and SSL Certificate Partner

[NewsArchive]

Friedrich,

> BTW, this will also not be available in the future. For security reasons,
> you can't simply "extract" files from within a setup.exe without running it.

Thank you. This was always one of the things I disliked about that
"other software"<g> I used to use!

--
Lee White

Enroll Today at http://CWaddons.com

[NewsArchive]

Hi Lee,

> Thank you. This was always one of the things I disliked about that
> "other software"<g> I used to use!

<G> :) You made a "wise" switch. Argh - the "W" word. I should make an
appointment with the doctor <g>

Friedrich

[NewsArchive]

Just tell him you used "W" to install "W-dev". On 2nd thought, maybe not,
he'll raise his fees! ;-)

--
Russell B. Eggen
www.radfusion.com
Clarion developers: www.radfusion.com/dev.htm

[NewsArchive]

> Just tell him you used "W" to install "W-dev". On 2nd thought, maybe not,
> he'll raise his fees! ;-)

<ROFL> ;-)

Friedrich

[NewsArchive]

> Just tell him you used "W" to install "W-dev". On 2nd thought, maybe not,
> he'll raise his fees! ;-)

For you Russ, always!!!<g>

--
Lee White

Enroll Today at http://CWaddons.com

[NewsArchive]

I try to do my part to stimulate the economy <g>

--
Russell B. Eggen
www.radfusion.com
Clarion developers: www.radfusion.com/dev.htm

[NewsArchive]

Friedrich,

> Argh - the "W" word.

I made a wise choice to use SetupBuilder and I'm not going back!


See, not such a bad word after all.<g>

--
Lee White

Enroll Today at http://CWaddons.com

[NewsArchive]

>> Argh - the "W" word.
>
> I made a wise choice to use SetupBuilder and I'm not going back!
>
> See, not such a bad word after all.<g>

Absolutely <g> :)

Friedrich

[NewsArchive]

Hi Friedrich,

thanks for your answer. So I have to ask for an idea how to solve our
problem. I will try to explain our update/patch situation:

This is the part of our script installing the files:

Install File "C:\SetupBuilder 6 Projects\AIDA 6 Setup
V001\Redist\Distrib\AidaWin\DLL\SYS\Aida\*.*" to "%SYS32DIR%\*.*"
(Always Install) [Version/Date/Time] [Shared] [SelfReg]

Install File "C:\SetupBuilder 6 Projects\AIDA 6 Setup
V001\Redist\Distrib\AidaWin\DLL\SYS\CrystalA\*.*" to "%SYS32DIR%\*.*"
(Always Install) [Version/Date/Time] [Shared] [SelfReg]

Install File "C:\SetupBuilder 6 Projects\AIDA 6 Setup
V001\Redist\Distrib\AidaWin\BARCODE\*.*" to "%FONTSDIR%\*.*" (Always
Install) [TrueType]

Install File "C:\SetupBuilder 6 Projects\AIDA 6 Setup
V001\Redist\Distrib\AidaWin\Daten\*.*" to
"%_SB_INSTALLDIR%\DatenStd\*.*" (Always Install)

Install File "C:\SetupBuilder 6 Projects\AIDA 6 Setup
V001\Redist\Distrib\AidaWin\InfoStd\*.*" to
"%_SB_INSTALLDIR%\InfoStd\*.*" (Always Install)

Install File "C:\SetupBuilder 6 Projects\AIDA 6 Setup
V001\Redist\Distrib\AidaWin\ListStd\*.*" to
"%_SB_INSTALLDIR%\ListStd\*.*" (Always Install)

Install File "C:\SetupBuilder 6 Projects\AIDA 6 Setup
V001\Redist\Distrib\AidaWin\MaskKde\*.*" to
"%_SB_INSTALLDIR%\MaskKde\*.*" (Always Install)

Install File "C:\SetupBuilder 6 Projects\AIDA 6 Setup
V001\Redist\Distrib\AidaWin\MaskStd\*.*" to
"%_SB_INSTALLDIR%\MaskStd\*.*" (Always Install)

Install File "C:\SetupBuilder 6 Projects\AIDA 6 Setup
V001\Redist\Distrib\AidaWin\Programm\*.*" to
"%_SB_INSTALLDIR%\Programm\*.*" (Always Install)

Install File "C:\SetupBuilder 6 Projects\AIDA 6 Setup
V001\Redist\Distrib\AidaWin\WWWRoot\*.*" to
"%_SB_INSTALLDIR%\WWWRoot\*.*" (Always Install)

Install File "C:\SetupBuilder 6 Projects\AIDA 6 Setup
V001\Redist\Distrib\AidaWin\DLL\SYS\CrystalB\*.*" to
"%_SB_INSTALLDIR%\Programm\*.*" (Always Install)

Install File "C:\SetupBuilder 6 Projects\AIDA 6 Setup
V001\Redist\Distrib\AidaWin\DLL\Crystal\Crystal Reports\*.*" to
"%_SB_INSTALLDIR%\Programm\*.*" (Always Install)

Install File "C:\SetupBuilder 6 Projects\AIDA 6 Setup
V001\Redist\Distrib\AidaWin\DLL\Crystal\Shared\*.*" to
"%_SB_INSTALLDIR%\Programm\*.*" (Always Install)

Install File "C:\SetupBuilder 6 Projects\AIDA 6 Setup
V001\Redist\Distrib\AidaWin\DLL\Crystal\Crystal\*. *" to
"%_SB_INSTALLDIR%\Programm\*.*" (Always Install)

This few line are installing more than 3.000 files.

Our version schema is
[Main Version].[Sub Version].[Revision]

For each sub version [for example 05.16.??] there are 10 or twenty
revisions:

V05.16.00
V05.16.01
..
..
..
V05.16.16
V05.16.18

The exakt number of Revisions is not fixed. It depends on the
development process.

For each sub version (05.16.00, 05.17.00, ...), we want to release a
full setup (without patch capability).

For each revsion (05.16.01, 05.16.02, ...), we want to release a full
setup and a patch version. The patch version should be able to patch all
previous versions with the same sub version. This means V05.16.05 patch
should be able to patch 05.16.00, 05.16.01, ..., 05.16.04.

What is the easiest/best way to ingrate this in our automated build
process? To change the script by hand (adding Previous File Versions on
the "Patch" tab) is not a solution.

Thanks for any suggestion.

Markus

[NewsArchive]

Hi Markus,

> What is the easiest/best way to ingrate this in our automated build
> process? To change the script by hand (adding Previous File Versions
> on the "Patch" tab) is not a solution.
>
> Thanks for any suggestion.

That's an interesting scenario. Unfortunately, I don't have any suggestion,
sorry. The "Previous File Versions" option does not (and as far as I can
tell, will not in the foreseeable future) support "wildcards".

It's not a problem to create a V05.16.05 delta patch to bring V05.16.00,
V05.16.01, ..., V05.16.04 to the latest version. But you can't "automate"
this process by using "patch wildcards". I see what you are trying to do
and in your case, "to change the script by hand" is really not an option.

From the technical point of view and in theory, it should be possible to
enhance the compiler in such a way that wildcards are supported. For
example, for the following "Install File" action:

\AidaWin\MaskStd\*.*

Your would define as "Previous File Versions":

\V05.16.00\AidaWin\MaskStd\*.*
\V05.16.01\AidaWin\MaskStd\*.*
\V05.16.02\AidaWin\MaskStd\*.*
\V05.16.03\AidaWin\MaskStd\*.*
\V05.16.04\AidaWin\MaskStd\*.*

We'll add it to the wish list for future consideration.

Thanks,
Friedrich

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

SetupBuilder "point. click. ship"
Create Windows Vista ready installations in minutes

-- Official Comodo Code Signing and SSL Certificate Partner

[NewsArchive]

Hi Friedrich,

so, in my opinion, there are two possible options:

1.) We could write a tool, that modifies the .sb6 file itsself to update
the "previous version files". For that, we need information about the
sb6 file structure.

2.) We would pay for the compiler enhancement (wildcards, command line
support for "prev. file versions"), so you can do this a little bit
earlier (but after your next sb7 release of course).

What do yout think?

Markus

[NewsArchive]

Hi Markus,

> 2.) We would pay for the compiler enhancement (wildcards, command
> line support for "prev. file versions"), so you can do this a little
> bit earlier (but after your next sb7 release of course).
>
> What do yout think?

With a focus on customer satisfaction and continual improvement, our
SetupBuilder user base continues to increase rapidly. So money is not the
driving force behind improvements here :) We'll brainstorm your feature
request in our next business meeting. I'll keep you posted.

Friedrich

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

SetupBuilder "point. click. ship"
Create Windows Vista ready installations in minutes

-- Official Comodo Code Signing and SSL Certificate Partner

[NewsArchive]

Markus,

FYI: we have added "wildcard patching capability" to SetupBuilder 7 now.

The following is possible:

\AidaWin\MaskStd\*.*

Your can define the following "Previous File Versions" to automatically
generate a delta patch for revision (05.16.00, 05.16.01, 05.16.02, 05.16.03,
05.16.04, ...):

\V05.16.00\AidaWin\MaskStd
\V05.16.01\AidaWin\MaskStd
\V05.16.02\AidaWin\MaskStd
\V05.16.03\AidaWin\MaskStd
\V05.16.04\AidaWin\MaskStd

"Previous File Verions" can even be set from a compiler variable.

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

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

-- Official Comodo Code Signing and SSL Certificate Partner

[NewsArchive]

GREAT, GREAT, GREAT!

Thank you, Friedrich.

Markus Zander

[NewsArchive]

> Markus,
>
> FYI: we have added "wildcard patching capability" to SetupBuilder 7 now.

Friedrich,

Any "ball park" release date you could suggest for next SB7 build? I think
you mentioned previously, Windows 7 Release Candidate delayed the next SB7
build.

David

--
From David Troxell - Product Scope 7 - Encourager Software
Clarion Third Party Profile Exchange Online
http://encouragersoftware.com/profile/clarlinks.html
Profile Exchanges - www.encouragersoftware.com/profile/
http://www.profileexchanges.com/blog/

[NewsArchive]

Hi David,

> Any "ball park" release date you could suggest for next SB7 build? I
> think you mentioned previously, Windows 7 Release Candidate delayed
> the next SB7 build.

Our goal is to release the final beta build within the next seven days.

Friedrich

[NewsArchive]

> Hi David,
>
>> Any "ball park" release date you could suggest for next SB7 build? I
>> think you mentioned previously, Windows 7 Release Candidate delayed
>> the next SB7 build.
>
> Our goal is to release the final beta build within the next seven days.

Friedrich,

Thanks much! This will help many of us to plan accordingly with planned
releases of our own.

David

--
From David Troxell - Product Scope 7 - Encourager Software
Clarion Third Party Profile Exchange Online
http://encouragersoftware.com/profile/clarlinks.html
Profile Exchanges - www.encouragersoftware.com/profile/
http://www.profileexchanges.com/blog/