Mike, thanks for your response. I intend using the correct component GUIDs for all the files. As far as I know there are no merge modules for msxml prior to version 3?
I guess my examples were not very sensible. The examples I gave were just a few obvious ones - there are many many more. I am trying to make hundreds of packages (a mixture of 3rd party and in-house) co-exist together. I have a means of ensuring all files get the correct/consistent component GUIDs. I have all the registry that all the files create when they self register. I was wondering what the best strategy was to deal with registry that is shared amongst different files where there is no merge module available. Thanks Paul Phone: 01628 534395 (int: 630 8395) Mobile: 07977917774 (int: 611 7774) email: [EMAIL PROTECTED] -----Original Message----- From: Mike Dimmick [mailto:[EMAIL PROTECTED] Sent: 21 September 2006 12:33 To: DOLPHIN Paul (AXA-L); wix-users@lists.sourceforge.net Subject: RE: [WiX-users] Multiple files sharing registry For all the files you mention, you should be using the MSMs. If you generate your own component GUIDs for these files, you risk breaking other applications when they are uninstalled. See Rob Mensching's blog post 'Component Rules 101' for details (http://blogs.msdn.com/robmen/archive/2003/10/18/56497.aspx). For any case where you're redistributing a third-party's components, follow the supplier's guidance for how they should be redistributed. For HTML Help I think it should be the HTML Help Update package. -- Mike Dimmick -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of DOLPHIN Paul (AXA-L) Sent: 21 September 2006 12:21 To: wix-users@lists.sourceforge.net Subject: [WiX-users] Multiple files sharing registry Could someone offer suggestions as to the best way of dealing with self registering files that share registry entries. There are a number of examples of this - 1. Later versions of files with different names (e.g. msxml.dll, msxml3.dll, etc) 2. Files that use other files (e.g. olepro32.dll uses oleaut32.dll) 3. Files that are part of the same subsystem (e.g. hhctrl.ocx and itss.dll) Etc Using tallow/heat/similar tools captures the registry for these types of files and puts it in a component with the file but this means that e.g. uninstalling a package containing msxml3.dll will break packages containing msxml.dll since the common registry will be deleted. The only solution I can think of is to create a separate component containing ALL the related registry entries (e.g. for all versions of msxml*.dll) and make sure that is always included with any of the relevant files. Is there a better way? This email originates from AXA Sun Life Services plc which distributes and administers financial services and products. Registered in England No. 3424940, registered office: 5 Old Broad Street, London, EC2N 1AD. AXA Sun Life Services plc is authorised and regulated by the Financial Services Authority and is entered on the Financial Services Authority register (www.fsa.gov.uk/register) number 185746. This message and any files transmitted with it are confidential and intended solely for the individual or entity to whom they are addressed. If you have received this in error, you should not disseminate or copy this email. Please notify the sender immediately and delete this email from your system. Please also note that any opinions presented in this email are solely those of the author and do not necessarily represent those of the AXA UK Group of companies. Email transmission cannot be guaranteed to be secure, or error free as information could be intercepted, corrupted, lost, destroyed, late in arriving or incomplete as a result of the transmission process. The sender therefore does not accept liability for any errors or omissions in the contents of this message which arise as a result of email transmission. Finally, the recipient should check this email and any attachments for viruses. The AXA UK Group of companies accept no liability for any damage caused by any virus transmitted by this email. ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
