Microsoft KB Archive/906764

= BUG: Merge module files have the same ComponentID in different Visual Studio projects =

Article ID: 906764

Article Last Modified on 3/2/2007

-

APPLIES TO


 * Microsoft Visual Studio 2005 Professional Edition
 * Microsoft Visual Studio 2005 Standard Edition
 * Microsoft Visual Studio 2005 Express Edition
 * Microsoft Visual Studio .NET 2003 Professional Edition
 * Microsoft Visual Studio .NET 2003 Enterprise Architect
 * Microsoft Visual Studio .NET 2003 Enterprise Developer
 * Microsoft Visual Studio .NET 2003 Academic Edition
 * Microsoft Visual Studio .NET 2002 Professional Edition
 * Microsoft Visual Studio .NET 2002 Enterprise Architect
 * Microsoft Visual Studio .NET 2002 Enterprise Developer
 * Microsoft Visual Studio .NET 2002 Academic Edition

-





SYMPTOMS
When you create two Merge Module projects in Microsoft Visual Studio or in Microsoft Visual Studio .NET, the .msm files for the two projects may have the same ComponentID.



CAUSE
This issue occurs because of the steps that are used to create the hash value for the file.



WORKAROUND
To work around this issue, use a database table editor such as the Orca.exe utility to modify the ComponentID of one of the .msm files.

Note The Orca.exe utility is available as part of the Microsoft Platform SDK Components for Windows Installer Developers.

To modify the ComponentID by using the Orca.exe utility, follow these steps:
 * 1) Start Orca.exe, and then open the .msm file that you want to modify.
 * 2) In the left pane, click Component.
 * 3) In the right pane, click the current ComponentID, and then press CTRL+G to paste a new ComponentID GUID.
 * 4) On the File menu, click Save.
 * 5) Quit the Orca.exe utility.



STATUS
Microsoft has confirmed that this is a bug in the Microsoft products that are listed in the &quot;Applies to&quot; section.

