Of Cristian Libardo [
[EMAIL PROTECTED]
Sent: Tuesday, August 05, 2008 7:31 AM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] ps:SnapIn
Hi. I've been diving into the amazing world of wix and I just came to the
point where I could use some help (newbie alert).
We have a setup with two
. They are much easier to
work with.
From: [EMAIL PROTECTED] [EMAIL PROTECTED] On Behalf Of Cristian Libardo [EMAIL
PROTECTED]
Sent: Tuesday, August 05, 2008 7:31 AM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] ps:SnapIn
Hi. I've been diving
Hi. I've been diving into the amazing world of wix and I just came to the
point where I could use some help (newbie alert).
We have a setup with two solutions. One that builds merge modules. The other
that picks the previously generated msm:s and creates msi:s.
My problem occurs when I use the
You're probably facing the same issue I did.. There's currently a bug that
binder variables need the fully modularized id in merge modules. I don't
know if there's a way to pass this in to SnapIn extension, but you can try
modularizing the file key yourself as a workaround.
Chris
On Tue, Aug
Thank you. I'm just about to read up on modularization. Do you mean
something like this?:
File Id=MyModule.MyFolder.MyAssembly.dll
On Tue, Aug 5, 2008 at 4:45 PM, Christopher Karper
[EMAIL PROTECTED] wrote:
You're probably facing the same issue I did.. There's currently a bug that
binder
No.. That would be normal.
http://sourceforge.net/tracker/index.php?func=detailaid=2034934group_id=105970atid=642714
You need to add the Module GUID to the file ID.
Wix does a lot of nice things for us, including handling the ID redirection
that occurs with modularization. When you refer to
6 matches
Mail list logo
