As long as your entire organization is using Wix to build their
deployments.
Chris
On Mon, Aug 11, 2008 at 1:22 AM, Blair Murri <[EMAIL PROTECTED]> wrote:
> I don't know if anyone has mentioned this already, but the Windows
> Installer team has been trying to deprecate Merge Modules almost ever
I don't know if anyone has mentioned this already, but the Windows Installer
team has been trying to deprecate Merge Modules almost ever since they created
them.
If you don't have to distribute your merge modules to external customers, you
should consider using WixLibs instead of Merge Modules.
No.. That would be normal.
http://sourceforge.net/tracker/index.php?func=detail&aid=2034934&group_id=105970&atid=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
Thank you. I'm just about to read up on modularization. Do you mean
something like this?:
wrote:
> 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 Sn
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 5,
5 matches
Mail list logo