Hi Michael,
Thanks for all your help in trying to resolve my issue.
In the end I had to give up on trying to understand the cause. I did try
downloading the source but could not build it with the tools that the make
file says that I need. There were just too many compile errors and too
little
Michael,
I do have access to a standard edition of SQL Server and so I used the SQL
Profiler from that to analyse what was happening during the install.
With my WiX generated installer I saw all the login, database creation and
stored procedure addition stuff that I expected. However, when I
Hi Michael,
The property SQLSERVER is being set to '(local)\SQLEXPRESS' from within the
MSI database, although if I edit this using Orca to some other value it gets
reset back to the above value when the setup program is run (as observed
from the log file).
I think that the above value is
I have created a merge module using Wix v3 that successfully installs several
databases in to SQL Express 2005 SP3 when integrated in to a Wix generated
MSI of my own making. However, when I ship this merge module to my customer,
he integrates it into an InstallShield Setup program and it
Thanks.
Rob Mensching-6 wrote:
Because both Merge Modules have the CustomAction but a CustomAction can
only exist in a Product once. So the warning is telling you one of them
is being dropped.
John Stevenson-Hoare wrote:
Does anyone know why I get this warning and the following
Does anyone know why I get this warning and the following warnings when
I include two merge modules in my installation package that each
contains a reference to WixUtilExtension?
warning LGHT1056: The CustomAction table contains a row with primary
key(s) 'SchedXmlFile' which cannot be merged
6 matches
Mail list logo
