On 7/16/07, Bob Arnson [EMAIL PROTECTED] wrote:
Scott Palmer wrote:
Microsoft certainly doesn't like to make things easy do they? I
assume though that if someone in the WMF group clued in to using MSI
that they might also have the foresight to provide a merge module for
the
Scott Palmer wrote:
I've only used merge modules to install shared components like the VC8
runtime. I assume that merge modules would update all products in the
case of machine-wide shared components like that.
Patches target specific products so they can't be used to let Microsoft,
for
Microsoft certainly doesn't like to make things easy do they? I assume
though that if someone in the WMF group clued in to using MSI that they
might also have the foresight to provide a merge module for the
redistributables. Kind of like they should have years ago.
However, assuming that they
Microsoft certainly doesn't like to make things easy do they?
I assume though that if someone in the WMF group clued in to using MSI
that they might also have the foresight to provide a merge module for
the redistributables. Kind of like they should have years ago.
Scott Palmer wrote:
Microsoft certainly doesn't like to make things easy do they? I
assume though that if someone in the WMF group clued in to using MSI
that they might also have the foresight to provide a merge module for
the redistributables. Kind of like they should have years ago.
I've got a checkbox in my installer that for some reason cannot be changed
by the user and I haven't a clue why. Anyone got some ideas?
Here's some code snippets:
The initial state is set to checked... (most users will want to upgrade ..
some will need to keep old versions because later
Scott Palmer wrote:
I've got a checkbox in my installer that for some reason cannot be
changed by the user and I haven't a clue why. Anyone got some ideas?
You need to specify the CheckBoxValue attribute.
InstallExecuteSequence
...
Custom Action=exec_WMF90_redist
7 matches
Mail list logo