M
Marco Voorwinden
Hello all,
We've created quite a complex installer using InstallShield Developer 7 SP4,
and shipped version 2.1.1 to our customers. Now we're in the need of
applying a very minor 'patch' to our installation (resulting in the same
product version with only the build number changed). I tried this first
using the Tools/Generate Patch option, which did create a patch (.msp) file,
but that patch could not be installed (due to the MSDE merge module). Next I
tried it with a minor upgrade, but now it only installs part of the new
files. I've been working on this problem for a week now, and am quite
desperate
If anyone can help me with this, or encounters the same problem(s) please
reply to this post.
Thanks in advance!
Details:
The installation contains 3 features (Client,Server,Common), next to some
Merge Modules. Depending on the type of setup that is chosen
(Client,Server,Standalone) some features are selected for installation
(using the addlocal Event on the Next button of the dialog where the user
can select the type of installation).
Now for the upgrade (or patch) I compiled a new installer, where I changed
only the package code (according to the description in the Help).
Running this installation with the command line options REINSTALL=ALL and
REINSTALLMODE=vomus, does only install some of the new files, and not all.
(These files are all from the Common or the Server feature. nothing from
Client is installed)
Looking at the verbose logging, I found the following:
---snip---
MSI (s) (C4:40): Feature: Common; Installed: Local; Request: Reinstall;
Action: Reinstall
MSI (s) (C4:40): Feature: Client; Installed: Advertise; Request:
Reinstall; Action: Reinstall
---snip---
Strange that Common is installed as Local, and Client as Advertise!!!
This results in the fact that all the Client components are skipped:
---snip---
MSI (s) (C4:40): Component: Designer; Installed: Local; Request: Null;
Action: Null
MSI (s) (C4:40): Component: Images; Installed: Local; Request: Null;
Action: Null
---snip---
Can someone explain to me why it happens that one feature is installed as
Advertise and the other as Local?? As far as I can find in the MSI Project,
nothing is done to make the Client Feature advertise...
Can I change this during the upgrade maybe?
Thanks for any help.
Marco Voorwinden
We've created quite a complex installer using InstallShield Developer 7 SP4,
and shipped version 2.1.1 to our customers. Now we're in the need of
applying a very minor 'patch' to our installation (resulting in the same
product version with only the build number changed). I tried this first
using the Tools/Generate Patch option, which did create a patch (.msp) file,
but that patch could not be installed (due to the MSDE merge module). Next I
tried it with a minor upgrade, but now it only installs part of the new
files. I've been working on this problem for a week now, and am quite
desperate
If anyone can help me with this, or encounters the same problem(s) please
reply to this post.
Thanks in advance!
Details:
The installation contains 3 features (Client,Server,Common), next to some
Merge Modules. Depending on the type of setup that is chosen
(Client,Server,Standalone) some features are selected for installation
(using the addlocal Event on the Next button of the dialog where the user
can select the type of installation).
Now for the upgrade (or patch) I compiled a new installer, where I changed
only the package code (according to the description in the Help).
Running this installation with the command line options REINSTALL=ALL and
REINSTALLMODE=vomus, does only install some of the new files, and not all.
(These files are all from the Common or the Server feature. nothing from
Client is installed)
Looking at the verbose logging, I found the following:
---snip---
MSI (s) (C4:40): Feature: Common; Installed: Local; Request: Reinstall;
Action: Reinstall
MSI (s) (C4:40): Feature: Client; Installed: Advertise; Request:
Reinstall; Action: Reinstall
---snip---
Strange that Common is installed as Local, and Client as Advertise!!!
This results in the fact that all the Client components are skipped:
---snip---
MSI (s) (C4:40): Component: Designer; Installed: Local; Request: Null;
Action: Null
MSI (s) (C4:40): Component: Images; Installed: Local; Request: Null;
Action: Null
---snip---
Can someone explain to me why it happens that one feature is installed as
Advertise and the other as Local?? As far as I can find in the MSI Project,
nothing is done to make the Client Feature advertise...
Can I change this during the upgrade maybe?
Thanks for any help.
Marco Voorwinden