In article <[EMAIL PROTECTED]>,
JCWrs <[EMAIL PROTECTED]> writes:
> [...] 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.
Let me guess, you have several merge modules which have files that
have the same name in the same location relative to the merge module's
folder?
This is a bug in VS.NET's deployment projects. There really is not
much you can do about it, short of patching up the GUIDs yourself
after VS.NET builds the merge modules. See
<http://www.xmission.com/~legalize/msi/known-bugs-2003.html#MM3>
> 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?
The merge module signature GUID is used to generate unique primary
keys, but it doesn't affect the component GUID.
> 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?
If the problem is the one I describe above, you don't want to ignore
it. (i.e. is ICE08 failing as I describe in the above URL?) If the
problem is not the one I describe, then can you tell us more
information about the problem?
--
"The Direct3D Graphics Pipeline" -- DirectX 9 draft available for download
<http://www.xmission.com/~legalize/book/download/index.html>
Legalize Adulthood! <http://blogs.xmission.com/legalize/>
-------------------------------------------------------------------------
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
[email protected]
https://lists.sourceforge.net/lists/listinfo/wix-users
