If you have two separate MSI files then you'll have two entries in Add/Remove Programs. There's no magic merge that makes them become one product.
>> But I did the same type of thing using the .NET setup (which produces MSI files) and it did as I expected. The upgrade recognized that it was the same product as the initial install, and I only ended up with the one entry in Add/Remove Programs. Why exactly don't you want to include the file in subsequent updates? If it's a static file then patches and upgrades won't try to update it anyway if it hasn't changed. Otherwise don't use an MSI package to install it. Pack it in the Binary table of the first install, or as a resource in an exe so that Windows doesn't directly install and control it. You'll have to remove it at uninstall time. >> I don't want the user to have to download the larger MSI file (actually I turn it into an exe) that contains the static file when they do an upgrade, since there's no utility in doing so. I'm not sure what you mean by "Pack it in the Binary table of the first install". I'm not that knowledgeable about MSI's in general, have always used the .NET setup until I started using Wix. Phil Wilson -----Original Message----- From: Wix Mailing List [mailto:w...@danhinsley.com] Sent: Tuesday, May 18, 2010 9:41 AM To: 'General discussion for Windows Installer XML toolset.' Subject: [WiX-users] Upgrade installation The install of my app includes a large file that I don't want to include in the subsequent updates. So I have an install project and an upgrade project. I have the Product->UpgradeCode, and the Component->GUID Guids the same in the install and the upgrade. I use AutoGen for the Product and Package ID's. I run the install, then the update. Everything works OK, except there are now two entries in the Add/Remove program list. When I did this using the .NET install, it only kept the latest in the list. Any hints on how I would go about doing this? Thanks, Dan ---------------------------------------------------------------------------- -- _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users *** Confidentiality Notice: This e-mail, including any associated or attached files, is intended solely for the individual or entity to which it is addressed. This e-mail is confidential and may well also be legally privileged. If you have received it in error, you are on notice of its status. Please notify the sender immediately by reply e-mail and then delete this message from your system. Please do not copy it or use it for any purposes, or disclose its contents to any other person. This email comes from a division of the Invensys Group, owned by Invensys plc, which is a company registered in England and Wales with its registered office at Portland House, Bressenden Place, London, SW1E 5BF (Registered number 166023). For a list of European legal entities within the Invensys Group, please go to http://www.invensys.com/legal/default.asp?top_nav_id=77&nav_id=80&prev_id=77 . You may contact Invensys plc on +44 (0)20 7821 3848 or e-mail inet.hqhelpd...@invensys.com. This e-mail and any attachments thereto may be subject to the terms of any agreements between Invensys (and/or its subsidiaries and affiliates) and the recipient (and/or its subsidiaries and affiliates). ---------------------------------------------------------------------------- -- _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users ------------------------------------------------------------------------------ _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
