Monday, July 4, 2011 12:25 PM
Subject: Re: [WiX-users] Wix 3.0 Merge Module
PS: MergeRedirectFolder isn't a special name or anything. It's just what the
template calls the Directory that is parented to TARGETDIR and thus can be
retargeted by the merge process. The gory details are sp
PS: MergeRedirectFolder isn't a special name or anything. It's just what the
template calls the Directory that is parented to TARGETDIR and thus can be
retargeted by the merge process. The gory details are spelled out in the
MSI SDK: http://msdn.microsoft.com/en-us/library/aa367787(v=VS.85).aspx
---
Christopher Painter, Author of Deployment Engineering Blog
Have a hot tip, know a secret or read a really good thread that deserves
attention? E-Mail Me
From: Jaxon
To: wix-users@lists.sourceforge.net
Sent: Saturday, July 2, 2011 2:20 PM
Subject: Re: [WiX-users] Wix 3.0 Merge Module
Yes,
ail] <http://user/SendEmail.jtp?type=node&node=6541400&i=1>
> Sent: Saturday, July 2, 2011 10:49 AM
> Subject: Re: [WiX-users] Wix 3.0 Merge Module
>
> Hi,
>
> I hate to dig up an old thread, but I'm having the same problem as the OP,
> but I'm using
Sent: Saturday, July 2, 2011 10:49 AM
Subject: Re: [WiX-users] Wix 3.0 Merge Module
Hi,
I hate to dig up an old thread, but I'm having the same problem as the OP,
but I'm using InstallShield 11 Pro (InstallScript MSI Project).
My Wix 3.5 merge module is already installed to C:\ and for t
Hi,
I hate to dig up an old thread, but I'm having the same problem as the OP,
but I'm using InstallShield 11 Pro (InstallScript MSI Project).
My Wix 3.5 merge module is already installed to C:\ and for the life of me I
can't figure out why.
Any hints, suggestions, etc. would be greatly apprecia
Hi Rob,
I looked at the Directory table of the resulting MSI with SuperOrca
and MergeRedirectFolder's Directory_Parent = "myProd".
The problem was the sample I sent you did not replicate a bug that I
had in the real merge module. I prematurely closed a directory.
But now that we are on the topic
It should work. Did you look at the Directory table in the resulting MSI in
Orca and see that the MergeRedirectFolder did not have "myProd" as it's
parent?
On Sun, Jun 6, 2010 at 7:39 AM, Tzvi Tafet wrote:
> I am trying to write a Wix 3.0 merge module that an .msi can put
> wherever it wants. I
I am trying to write a Wix 3.0 merge module that an .msi can put
wherever it wants. I would like a directory structure like this:
c:\Program Files\myCompany\myProd
What is happening is that all of the files in the merge module are
written to c:\.
Here is the merge module:
Hello all,
I am trying to author a WiX 3.0 merge module (or two if necessary) that
will allow multiple app MSIs to install a Win32 shared SxS assembly and
associated policy (i.e the same deployment strategy that VC++ uses.)
After many attempts I continue to hit two roadblocks:
1) The first app M
10 matches
Mail list logo