I used to build my wix installer with SharpDevelop and I never noticed this
problem since it didn't throw an error.  I'm migrating it to Visual Studio
so it can be built alongside everything else, nightly, and I'm seeing a
problem.  The merge modules I use which are generated by VS setup projects
(I have no say in this) are read in by wix and their base components are all
showing the same GUID.  Obviously, this is not what I want and VS throws an
error because of it.  2 questions:

1)How can I change what GUID is assigned to their base components?  The
merge module signatures are different, I thought those were supposed to be
the GUIDs?

2)Why did SharpDevelop ignore this problem and is there a way to do that
with Visual Studio?  What are the potential problems with doing so?
-- 
View this message in context: 
http://www.nabble.com/Duplicate-GUIDs-caused-by-managed-merge-modules-tp14674436p14674436.html
Sent from the wix-users mailing list archive at Nabble.com.


-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Reply via email to