You would need to define the table schema using the CustomTable element.
Try using dark.exe on an msi which has thay merge modules and seeing what
CustomTable elements you get in the output.
Hope that helps
On 11 Mar 2014 02:15, Dmitry Nechaev
dmitry.nech...@objectconsulting.com.au wrote:
Hi
Those Merge Modules have NEVER WORKED CORRECTLY. I can't even get
those to work in VS2005. I have an app still on .NET 2.0. If you
complain on the SAP Forums, SAP states that the tool we use
internally to compile them passes validadation, but they never tell
you what that tool is... As
On 10-Mar-14 22:12, Dmitry Nechaev wrote:
There is no way for me to fix ICE03 error for this MSM using InsureTable for
the last dozen of tables commented out in the code above.
WiX doesn't know what those tables are so it can't create them. If the
merge modules are fundamentally broken, you
Message-
From: Carter Young [mailto:ecyo...@grandecom.net]
Sent: Wednesday, 12 March 2014 12:26 AM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] ICE03 or Unresolved reference
Those Merge Modules have NEVER WORKED CORRECTLY. I can't even get those to
work in VS2005. I have
Hi All
I started to work with WIX and got stack with weird behaviour of WIX 3.8 for
Visual Studio 2013.
I'm trying to merge Crystal Reports msm module into the project as below:
A File with Crystal Reports MSM:
InstallExecuteSequence
MsiPublishAssemblies Sequence=1502 /
5 matches
Mail list logo
