Setup Builder Uninstall

[NewsArchive]

Hi
This is applicable I guess to any installer/uninstaller.
If the installer creates a log of all the files in installs and the uninstaller
uses that to get rid of everything, is there a way of getting the unistaller to
remove files that the program generates on it's own?
Things like temp files or new data sets etc?

Can the install log be modified or can the unistaller be created to remove the directory?

TIA

Chris

[NewsArchive]

Chris,

> This is applicable I guess to any installer/uninstaller.
> If the installer creates a log of all the files in installs and the
> uninstaller uses that to get rid of everything, is there a way of
> getting the unistaller to remove files that the program generates
> on it's own? Things like temp files or new data sets etc?
>
> Can the install log be modified or can the unistaller be created to remove
> the directory?

Yes, absolutely no problem. You can do this from a "custom uninstall".
Remove files, folders (including folder trees), registries, stop services,
zip or unzip, etc. Whatever you want.

Does this help?

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

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

-- Official Comodo Code Signing and SSL Certificate Partner

[NewsArchive]

Thanks Friedrich,

Once I create the custom uninstall, how do I tell my installer to use it?
I don't see that in the manual or in the script for the install.

Maybe for ver 7? - an uninstall section with a check box called complete
re\moval or something that would include a 'Would you like to remove the
directory?' dialog box.

These questions aside, I don't know what I'd do without SB. - Thanks!

Chris

[NewsArchive]

Chris,

> Thanks Friedrich,
>
> Once I create the custom uninstall, how do I tell my installer to use it?
> I don't see that in the manual or in the script for the install.
>
> Maybe for ver 7? - an uninstall section with a check box called complete
> re\moval or something that would include a 'Would you like to remove the
> directory?' dialog box.
>
> These questions aside, I don't know what I'd do without SB. - Thanks!

You only add this custom uninstall to your main script and the compiler will
do the rest.

Please note that you can use *all* script functions (except "Install
File(s)" of course) from within a custom uninstall. Quite a few customers
have to remove several parent folders (not created by the install) during
the uninstall. So a simple 'Would you like to remove the directory?' dialog
box would not help ;-)

For example, they have to remove data folder trees, stop services, call into
DLLs, connect to a server and report that the application is uninstalled,
etc. All this cannot be done with a simple checkbox.

Please see the "Creating a Custom Uninstall" section in the manual or help.
There is a "Delete directories not created with my installation" example.

If you need help, just let me know.

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

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

-- Official Comodo Code Signing and SSL Certificate Partner

[NewsArchive]

Cool! Thanks much.
I wouldn't have guessed that it would be quite that easy. <g>

I have worked out that compiler variables can control nearly everything. So
rather than using features, I am setting CV values and controlliung the file
installs with ifcompvar . . .
Is this the way releases work?

chris

[NewsArchive]

Chris,

> Cool! Thanks much.
> I wouldn't have guessed that it would be quite that easy. <g>

<G> :)

> I have worked out that compiler variables can control nearly everything.
> So rather than using features, I am setting CV values and controlliung
> the file installs with ifcompvar . . .
> Is this the way releases work?

Well, not really. "Releases" are not a replacement for "Features".

Features are specifically designated portions of an application's total
functionality. For example, an application may have features like "Main
Application", "Help Files", "Tutorials", "Sample Files".

Releases control the "output" of the SetupBuilder project. You can define
Releases for your product and specify the settings particular to that
release.

For example, you might want to have a standard and a trial edition with and
without a help file for your application. In this case, you would create 3
releases:

- DownloadTrialWithHelp
- DownloadTrialWithoutHelp
- FullVersion

The same project can compile three (or more!) different installations now.
Different install name, different set of files, etc. That means, the same
project can compile completely different outputs (without having to change
the project). The "ifcompvar" compile directive gives you full control over
the script items for Releases. You can even do a command line compile for
"Releases".

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

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

-- Official Comodo Code Signing and SSL Certificate Partner

[NewsArchive]

That's what I meant that releases are produced using compvars
I now have one setup master creating 6 installs which use 6 different exes all
having different passwords, serial numbers and registry entries!
And each release only changes 1 compvar.

I like that you made the releases use the main values if you leave them blank.

Next, I want to create 2 setup types - Normal/Shared that will install
everything and Network User that will install only shortcuts to the network
install.

Thanks!

Chris