 | | From: | Jared | | Subject: | Multiple Uninstallers | | Date: | Tue, 14 Dec 2004 13:21:10 -0500 |
|
|
 | Is there a method in which if your installer installs 2 seperate programs
during the installation process that you could have an uninstaller for each?
--
Jared
|
|
| | From: | Tim Rude | | Subject: | Re: Multiple Uninstallers | | Date: | Tue, 14 Dec 2004 12:25:51 -0600 |
|
|
| Imbed one installer inside the other and call it using a [Run] entry. Be
sure that each has a different AppID.
--
Tim Rude
timrude@NOSPAM.hotmail.com
(remove NOSPAM. for correct email address)
"Jared" wrote in message
news:cpnatp$ub0$1@news.jrsoftware.org...
> Is there a method in which if your installer installs 2 seperate programs
> during the installation process that you could have an uninstaller for
each?
>
> --
>
> Jared
>
>
|
|
| | From: | Jared | | Subject: | Re: Multiple Uninstallers | | Date: | Tue, 14 Dec 2004 13:50:15 -0500 |
|
|
| Do you mean that the installer would instlal that file somewhere and then
run it? once they hit finish or somehting? The problem is that the second
program NEEDS to be installed by at least one other copy of software. I had
a post referring to this a few days ago. Right now I have them selecting a
path that gets stored in the registry for the second app at a custom screen
and installs the file as a shared file. The problem is the first time you
one of the packages that came with that second program you loose your start
menu shortcuts/desktop icons. I'd like to be able to do like sharedfile or
something with the links ideally. Is there any way of doign this ?
Thanks!
"Tim Rude" wrote in message
news:cpnb7e$udq$1@news.jrsoftware.org...
> Imbed one installer inside the other and call it using a [Run] entry. Be
> sure that each has a different AppID.
>
> --
> Tim Rude
>
> timrude@NOSPAM.hotmail.com
> (remove NOSPAM. for correct email address)
>
> "Jared" wrote in message
> news:cpnatp$ub0$1@news.jrsoftware.org...
>> Is there a method in which if your installer installs 2 seperate programs
>> during the installation process that you could have an uninstaller for
> each?
>>
>> --
>>
>> Jared
>>
>>
>
>
|
|
| | From: | Jonny Kwekkeboom | | Subject: | Re: Multiple Uninstallers | | Date: | Tue, 14 Dec 2004 20:32:43 +0100 |
|
|
| Hi,
create two setups
and you can call setup B from Setup A [Run] Section
If in Setup A a other AppID as in Setup B than it will create also 2
uninstaller....
Look in HelpFile for Setup->AppID directive....
cu
Jonny
|
|
| | From: | Jared | | Subject: | Re: Multiple Uninstallers | | Date: | Tue, 14 Dec 2004 15:55:21 -0500 |
|
|
| isnt it possible that they could just exit setup b once it gets started from
setup a? or once B finishes exit a? or something like that?
Jared
"Jonny Kwekkeboom" wrote in message
news:cpnf5f$vq6$1@news.jrsoftware.org...
> Hi,
>
> create two setups
> and you can call setup B from Setup A [Run] Section
>
> If in Setup A a other AppID as in Setup B than it will create also 2
> uninstaller....
>
> Look in HelpFile for Setup->AppID directive....
>
> cu
> Jonny
>
>
|
|
| | From: | Gavin Lambert | | Subject: | Re: Multiple Uninstallers | | Date: | Wed, 15 Dec 2004 11:02:42 +1300 |
|
|
| Jared wrote:
> isnt it possible that they could just exit setup b once it gets started from
> setup a? or once B finishes exit a? or something like that?
Install B silently. Ask any questions you need to know the answers to
during A's installation, and pass the answers to B on the command line,
or in an INI file or something.
If you set AllowCancelDuringInstall to no (for A), then once it's
actually begun the installation (including the [Run] section) there's no
way for the user to abort the installation of A.
To avoid having uninstallation of any A remove B when there are other
A's still installed, you'd need to add some conditional logic to only
call B's uninstaller if you're the last A that's installed.
Unfortunately, you can't do this with [UninstallRun] and Check functions
(since those are evaluated at install time, not uninstall time), so I
think your only option here is to use IS5's uninstall scripting and hook
into CurUninstallStepChanged(usPostUninstall).
Come to think of it, you could probably write a mini-app that does the
check & invokes the uninstaller itself, and then call *that* from
[UninstallRun]. That'd probably work in IS4. Up to you which one
sounds more difficult, though :)
|
|
