I can think of some: Advertising. Use of the resolve source action without a condition to prevent it after first time installation. Binary delta patching where the original file is not available, perhaps because it's been overwritten
Since we avoid all of those, we've never had the problem either. -----Original Message----- From: Pally Sandher [mailto:pally.sand...@iesve.com] Sent: 18 May 2011 10:43 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] How to cache msi for Modify/Repair to use I'm curious as to why people encounter issues with this. I've never had to do anything special for Windows Installer to do this automatically for our packages. Unfortunately I have run across situations where upgrade or uninstall of someone else's product prompts Windows Installer to request the MSI so it'd be interesting to know what causes it. Palbinder Sandher Software Deployment Engineer T: +44 (0) 141 945 8500 F: +44 (0) 141 945 8501 http://www.iesve.com **Design, Simulate + Innovate with the <Virtual Environment>** Integrated Environmental Solutions Limited. Registered in Scotland No. SC151456 Registered Office - Helix Building, West Of Scotland Science Park, Glasgow G20 0SP Email Disclaimer -----Original Message----- From: Wang, Miaohsi [mailto:miaohsi.w...@invensys.com] Sent: 17 May 2011 17:51 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] How to cache msi for Modify/Repair to use Hi Mat, Thanks a lot for the very useful information. If you can, please also share with us your merge module code. Thank you, Miaohsi -----Original Message----- From: Skildum, Mathew [mailto:mathew.skil...@aspect.com] Sent: Tuesday, May 17, 2011 8:58 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] How to cache msi for Modify/Repair to use There is no generic way to do this, You will basically have to write your own custom actions that does this task and updates the source list for the MSI package. I personally created a merge module with a set of actions that cache the MSI in a set location and handle any cleanup and registration that is required. Mat Skildum -----Original Message----- From: Wang, Miaohsi [mailto:miaohsi.w...@invensys.com] Sent: Tuesday, May 17, 2011 10:44 AM To: General discussion for Windows Installer XML toolset. Subject: [WiX-users] How to cache msi for Modify/Repair to use Dear All, After installing our product, doing Modify/Repair from the "Add Remove Programs" window requires the original install package to be in the same location where the product is installed from. Does anyone know how to cache msi locally such that Modify/Repair the product via "Add Remove Programs" window will not require this? Your help will be much appreciated. Thanks a lot, Miaohsi *** 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 3rd Floor, 40 Grosvenor Place, London, SW1X 7AW (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 3155 1200 or e-mail recept...@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). ----------------------------------------------------------------------------- - Achieve unprecedented app performance and reliability What every C/C++ and Fortran developer should know. Learn how Intel has extended the reach of its next-generation tools to help boost performance applications - inlcuding clusters. http://p.sf.net/sfu/intel-dev2devmay _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users ----------------------------------------------------------------------------- - Achieve unprecedented app performance and reliability What every C/C++ and Fortran developer should know. Learn how Intel has extended the reach of its next-generation tools to help boost performance applications - inlcuding clusters. http://p.sf.net/sfu/intel-dev2devmay _______________________________________________ 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 3rd Floor, 40 Grosvenor Place, London, SW1X 7AW (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 3155 1200 or e-mail recept...@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). ----------------------------------------------------------------------------- - Achieve unprecedented app performance and reliability What every C/C++ and Fortran developer should know. Learn how Intel has extended the reach of its next-generation tools to help boost performance applications - inlcuding clusters. http://p.sf.net/sfu/intel-dev2devmay _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users ----------------------------------------------------------------------------- - What Every C/C++ and Fortran developer Should Know! Read this article and learn how Intel has extended the reach of its next-generation tools to help Windows* and Linux* C/C++ and Fortran developers boost performance applications - including clusters. http://p.sf.net/sfu/intel-dev2devmay _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users SDL PLC confidential, all rights reserved. If you are not the intended recipient of this mail SDL requests and requires that you delete it without acting upon or copying any of its contents, and we further request that you advise us. SDL PLC is a public limited company registered in England and Wales. Registered number: 02675207. Registered address: Globe House, Clivemont Road, Maidenhead, Berkshire SL6 7DY, UK. ------------------------------------------------------------------------------ What Every C/C++ and Fortran developer Should Know! Read this article and learn how Intel has extended the reach of its next-generation tools to help Windows* and Linux* C/C++ and Fortran developers boost performance applications - including clusters. http://p.sf.net/sfu/intel-dev2devmay _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
