Lisa Wright wrote:
> I did find a workaround that seems to be working. I'm merging multiple msm's
> but have found that if the one I'm trying to work with is first in the list
> it gets merged properly and are sequenced in the 700's as they should.
>
Unfortunately, mergemod.dll has its own b
sion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Custom Actions from Merge Modules
Lisa Wright wrote:
> I'm having a similar problem with merge modules I am picking up from another
> team. I can't modify those msm's and I'm being forced to add custom ac
Lisa Wright wrote:
> I'm having a similar problem with merge modules I am picking up from another
> team. I can't modify those msm's and I'm being forced to add custom actions
> to set the system folder properties they use so the files get installed to
> the correct place. Mine need to be sequ
neral discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Custom Actions from Merge Modules
It's more complicated than that. The problem your hitting in WiX v3 is
actually a feature added in WiX v2 that allows a developer to separate their
authoring into separate "Fragmen
to be easy.
-Original Message-
From: Tina Basinger [mailto:[EMAIL PROTECTED]
Sent: Thursday, September 25, 2008 12:48
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Custom Actions from Merge Modules
It seems to me that Wix is being u
It seems to me that Wix is being unsupportive of something that Windows
Installer allows. The InstallExecuteSequence table of an MSI contains
references to both the custom actions defined in the MSI directly as well as
in the merge modules. You can go in and modify this table directly (using
Orca
Tina Basinger wrote:
> Maybe this is not supported any more. Should I be able to have the main
> installation code schedule a custom action that is defined within a merge
> module? Any thoughts?
>
Merge modules are designed to be self-contained, which is why they have
the modularization GUID
In all likelihood, your problem is that your CA is being modularized when
compiled, but maybe not to the standard you're expecting. If you look at
your .msm in Orca, you'll see the actual name it's been given. I believe
you can suppress the modularization if that's your wish. Or you can at
leas
Maybe this is not supported any more. Should I be able to have the main
installation code schedule a custom action that is defined within a merge
module? Any thoughts?
Thanks!
-Tina
On Fri, Sep 19, 2008 at 1:15 PM, Tina Basinger <[EMAIL PROTECTED]>wrote:
> Is there a trick to calling a custom
9 matches
Mail list logo
