Hi,
I would try incrementally adding these files to see which ones cause the
collision. Seems to be a problem with duplicate identifiers. Otherwise merge
modules should work .. however merge modules are originally indended to ease
the deploying of 3rd party products' installers and allow to isolate the
work of developers or developer teams. Using them at such a low level might
result in too much ado, but i think it's not a mistake.
(I think, but gurus might know it better)
Regards,
Janos
2007/9/25, Crouch, John <[EMAIL PROTECTED]>:
>
> Dear all,
>
> We have produced a large MSI made up of many merge modules (our features),
> most of which have *.exes with their own exe.configs to be configured at
> install time using <util:XMLFile>. However, when we try to bring them
> together we get a collision problem in the Light.exe log file please see
> below for the error message that is repeated for every module.
>
>
>
> We are not sure of:
>
> a) If these tasks are standard or custom actions? We can see in Orca
> that these are custom actions but in Wix not.
>
> b) How do we keep the feature & configuration part together if we take
> out the XMLFile config part and put it in a separate module?
>
> c) Are we off track completely?
>
>
>
> We can see that when experimenting with a single merge module – no
> problem.
>
>
>
> John
>
>
>
>
>
> warning LGHT1055 : The InstallExecuteSequence table contains an action
> 'SchedXmlFile' which cannot be merged from the merge module 'DAL
> Initilaliser Application.msm'. This action is likely colliding with an
> action in the database that is being created. The colliding action may have
> been authored in the database or merged in from another merge module. If
> this is a standard action, it is likely colliding due to a difference in the
> condition for the action in the database and merge module. If this is a
> custom action, it should only be declared in the database or one merge
> module.
>
>
>
> warning LGHT1056 : The CustomAction table contains a row with primary
> key(s) 'SchedXmlFile' which cannot be merged from the merge module 'NOV DAL
> Initilaliser Application.msm'. This is likely due to collision of rows
> with the same primary key(s) (but other different values in other columns)
> between the database and the merge module.
>
>
>
> warning LGHT1056 : The CustomAction table contains a row with primary
> key(s) 'ExecXmlFile' which cannot be merged from the merge module 'DAL
> Initilaliser Application.msm'. This is likely due to collision of rows
> with the same primary key(s) (but other different values in other columns)
> between the database and the merge module.
>
>
>
> warning LGHT1056 : The CustomAction table contains a row with primary
> key(s) 'ExecXmlFileRollback' which cannot be merged from the merge module
> 'DAL Initilaliser Application.msm'. This is likely due to collision of
> rows with the same primary key(s) (but other different values in other
> columns) between the database and the merge module.
>
>
>
> Kind regards,
> *National Oilwell Varco*
>
> *John Crouch*
> Software Engineer/Developer
>
> National Oilwell Norway AS
> Phone: +4751818181
> Direct: +4751217563
> Fax: +4751800547
> [EMAIL PROTECTED] <[EMAIL PROTECTED]>
> www.nov.com
>
>
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2005.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
>
>
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
