Hi,

I'm new to WiX. I have multiple merge modules, each of which sets up a web
application via WixIisExtension. 
When I merged them together, I received a lot of LGHT1055, LGHT1056 warnings
like:

(143) : warning LGHT1056 : The CustomAction table contains a row with
primary ke
y(s) 'RemoveUser' which cannot be merged from the merge module 'xxx.msm'. 
This i
s likely due to collision of rows with the same primary key(s) (but other
differ
ent values in other columns) between the database and the merge module.

(144) : warning LGHT1055 : The InstallExecuteSequence table contains an
action '
ConfigureUsers' which cannot be merged from the merge module 'xxx.msm'. 
This act
ion is likely colliding with an action in the database that is being
created.  T
he colliding action may have been authored in the database or merged in from
ano
ther 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 me
rge module.

I tend to not put all components using WixIisExtension in a single
MergeModule. I have to keep separate merge modules and merge some of them
when needed.
So my question is:

Can I ignore these warnings or should I do anything to eliminate these
warning?


Kind Regards,

Daming




--
View this message in context: 
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/The-impact-of-merging-multiple-merge-modules-into-one-package-when-each-of-msm-contains-WixIisExtensn-tp7581396.html
Sent from the wix-users mailing list archive at Nabble.com.

------------------------------------------------------------------------------
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_sfd2d_oct
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Reply via email to