New Entry in Add/Remove Program when upgrade
|
|
Chunyan
|
Hi wix-users,
I developed one setup msi. And I want it to be upgradable. The requirement is: 1. Version 1 install to PathA. (New Install) 2. Version 2 install to PathB. (New Install) 3. Version 3 install to PathA. (Upgrade) The setup meets the requairment. However, when I perform the above actions, there are 3 items in Add/Remove Program list. Version 1 and Version 3 are in the same path. Actually there are 2 installs, since version 3 just upgrades version 2. I consider the reason is that I set <UpgradeVersion OnlyDetect="yes" Property="PREVIOUSFOUND" ... Here Onlydetect = "yes". I know if I set OnlyDetect="No", then upgrade will replace the older version. And there is no old version item in Add/Remove Program list. But if I set OnlyDetect="No", when I perform second step (install Version 2 to PathB(New Install)), the system will check last install (Version 1 in PathA), and remove the files in PathA. I don't what to break install 1. Is there one way to resolve my problem? Regards Chunyan ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ WiX-users mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/wix-users |
||||||||||||||||
Blair-2
|
You could try removing OnlyDetect="no" and adding a condition to the
RemoveExistingProducts action. However, then version 3 in your scenario will remove both versions 1 and 2 (instead of just 1). Your requirement to leave multiple versions without forcing each to use a different path is the problem. It doesn't leave you with many options. -----Original Message----- From: Jiang, Chunyan (GE Healthcare) [mailto:[hidden email]] Sent: Friday, November 06, 2009 1:59 AM To: General discussion for Windows Installer XML toolset. Subject: [WiX-users] New Entry in Add/Remove Program when upgrade Hi wix-users, I developed one setup msi. And I want it to be upgradable. The requirement is: 1. Version 1 install to PathA. (New Install) 2. Version 2 install to PathB. (New Install) 3. Version 3 install to PathA. (Upgrade) The setup meets the requairment. However, when I perform the above actions, there are 3 items in Add/Remove Program list. Version 1 and Version 3 are in the same path. Actually there are 2 installs, since version 3 just upgrades version 2. I consider the reason is that I set <UpgradeVersion OnlyDetect="yes" Property="PREVIOUSFOUND" ... Here Onlydetect = "yes". I know if I set OnlyDetect="No", then upgrade will replace the older version. And there is no old version item in Add/Remove Program list. But if I set OnlyDetect="No", when I perform second step (install Version 2 to PathB(New Install)), the system will check last install (Version 1 in PathA), and remove the files in PathA. I don't what to break install 1. Is there one way to resolve my problem? Regards Chunyan ---------------------------------------------------------------------------- -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ WiX-users mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/wix-users ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ WiX-users mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/wix-users |
||||||||||||||||
|
Chunyan
|
Hi Blair,
Thank you for your explain. I still have some questions here. My requirement is to have multiple versions and also be able to upgrade some. In my last email, the Version 3 should be able to upgrade Version1. It means version 1 should be removed. And Version 2 is kept untouched. But now I set OnlyDetect="yes". When I install Version 3 to the path of Version 1, all these 3 versions stay in the system. And in the future, I want to show the installed software in the Listbox, and ask user to select which one to upgrade, there will be 3 items there, same as Add/Remove Program. It is confused. Version 2 has been upgraded (remove). It should not be shown there. Is it possible to realize my requirement? Best regards, Chunyan -----Ursprüngliche Nachricht----- Von: Blair [mailto:[hidden email]] Gesendet: Freitag, 6. November 2009 15:59 An: 'General discussion for Windows Installer XML toolset.' Betreff: Re: [WiX-users] New Entry in Add/Remove Program when upgrade You could try removing OnlyDetect="no" and adding a condition to the RemoveExistingProducts action. However, then version 3 in your scenario will remove both versions 1 and 2 (instead of just 1). Your requirement to leave multiple versions without forcing each to use a different path is the problem. It doesn't leave you with many options. -----Original Message----- From: Jiang, Chunyan (GE Healthcare) [mailto:[hidden email]] Sent: Friday, November 06, 2009 1:59 AM To: General discussion for Windows Installer XML toolset. Subject: [WiX-users] New Entry in Add/Remove Program when upgrade Hi wix-users, I developed one setup msi. And I want it to be upgradable. The requirement is: 1. Version 1 install to PathA. (New Install) 2. Version 2 install to PathB. (New Install) 3. Version 3 install to PathA. (Upgrade) The setup meets the requairment. However, when I perform the above actions, there are 3 items in Add/Remove Program list. Version 1 and Version 3 are in the same path. Actually there are 2 installs, since version 3 just upgrades version 2. I consider the reason is that I set <UpgradeVersion OnlyDetect="yes" Property="PREVIOUSFOUND" ... Here Onlydetect = "yes". I know if I set OnlyDetect="No", then upgrade will replace the older version. And there is no old version item in Add/Remove Program list. But if I set OnlyDetect="No", when I perform second step (install Version 2 to PathB(New Install)), the system will check last install (Version 1 in PathA), and remove the files in PathA. I don't what to break install 1. Is there one way to resolve my problem? Regards Chunyan ---------------------------------------------------------------------------- -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ WiX-users mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/wix-users ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ WiX-users mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/wix-users ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ WiX-users mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/wix-users |
||||||||||||||||
|
Chunyan
|
Hi Blair,
I would like to ask you if I want to realize my scenario, is it possible to write a custom action to realize removing Version 1? Here I set the main msi still as OnlyDetect="yes". But when select one install from the dialog (Version 1) to upgrade, do the removing verion 1 in the custom action. This custom action only does remove the selected version, don't do the Detect, therefore don't touch version 2. Is it possible? And how to realize it? Regards, Chunyan -----Ursprüngliche Nachricht----- Von: Jiang, Chunyan (GE Healthcare) Gesendet: Mittwoch, 11. November 2009 10:38 An: General discussion for Windows Installer XML toolset. Betreff: Re: [WiX-users] New Entry in Add/Remove Program when upgrade Hi Blair, Thank you for your explain. I still have some questions here. My requirement is to have multiple versions and also be able to upgrade some. In my last email, the Version 3 should be able to upgrade Version1. It means version 1 should be removed. And Version 2 is kept untouched. But now I set OnlyDetect="yes". When I install Version 3 to the path of Version 1, all these 3 versions stay in the system. And in the future, I want to show the installed software in the Listbox, and ask user to select which one to upgrade, there will be 3 items there, same as Add/Remove Program. It is confused. Version 2 has been upgraded (remove). It should not be shown there. Is it possible to realize my requirement? Best regards, Chunyan -----Ursprüngliche Nachricht----- Von: Blair [mailto:[hidden email]] Gesendet: Freitag, 6. November 2009 15:59 An: 'General discussion for Windows Installer XML toolset.' Betreff: Re: [WiX-users] New Entry in Add/Remove Program when upgrade You could try removing OnlyDetect="no" and adding a condition to the RemoveExistingProducts action. However, then version 3 in your scenario will remove both versions 1 and 2 (instead of just 1). Your requirement to leave multiple versions without forcing each to use a different path is the problem. It doesn't leave you with many options. -----Original Message----- From: Jiang, Chunyan (GE Healthcare) [mailto:[hidden email]] Sent: Friday, November 06, 2009 1:59 AM To: General discussion for Windows Installer XML toolset. Subject: [WiX-users] New Entry in Add/Remove Program when upgrade Hi wix-users, I developed one setup msi. And I want it to be upgradable. The requirement is: 1. Version 1 install to PathA. (New Install) 2. Version 2 install to PathB. (New Install) 3. Version 3 install to PathA. (Upgrade) The setup meets the requairment. However, when I perform the above actions, there are 3 items in Add/Remove Program list. Version 1 and Version 3 are in the same path. Actually there are 2 installs, since version 3 just upgrades version 2. I consider the reason is that I set <UpgradeVersion OnlyDetect="yes" Property="PREVIOUSFOUND" ... Here Onlydetect = "yes". I know if I set OnlyDetect="No", then upgrade will replace the older version. And there is no old version item in Add/Remove Program list. But if I set OnlyDetect="No", when I perform second step (install Version 2 to PathB(New Install)), the system will check last install (Version 1 in PathA), and remove the files in PathA. I don't what to break install 1. Is there one way to resolve my problem? Regards Chunyan ---------------------------------------------------------------------------- -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ WiX-users mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/wix-users ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ WiX-users mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/wix-users ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ WiX-users mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/wix-users ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ WiX-users mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/wix-users |
||||||||||||||||
|
Chunyan
|
Hi,
I would like to clarify my requirement again. I read thought the WiX Tutorial 4. And I hope I could develop one setup.msi, which could combine "Minior upgrades" and "New Install". In my scenario, if updage Version 3 to Version 1 in PathA, it should do the "Minor upgrades". It doesn't not change the ProductID. And it only changes the product version and some files, not totally remove all the last install. But if Version 3 installs to a new path, it can act as a new install. Is it possilbe to do this in one setup.msi? If it is not, I want to develop two msi, one is for new install, one is for update. And use an external executable to decide which msi is called. However, there are 90% content same in the NewInstall.msi and Update.msi. Is it possible to create a common part that these two msi can call it? Best regards, Chunyan -----Ursprüngliche Nachricht----- Von: Jiang, Chunyan (GE Healthcare) Gesendet: Mittwoch, 11. November 2009 11:24 An: General discussion for Windows Installer XML toolset. Betreff: Re: [WiX-users] New Entry in Add/Remove Program when upgrade Hi Blair, I would like to ask you if I want to realize my scenario, is it possible to write a custom action to realize removing Version 1? Here I set the main msi still as OnlyDetect="yes". But when select one install from the dialog (Version 1) to upgrade, do the removing verion 1 in the custom action. This custom action only does remove the selected version, don't do the Detect, therefore don't touch version 2. Is it possible? And how to realize it? Regards, Chunyan -----Ursprüngliche Nachricht----- Von: Jiang, Chunyan (GE Healthcare) Gesendet: Mittwoch, 11. November 2009 10:38 An: General discussion for Windows Installer XML toolset. Betreff: Re: [WiX-users] New Entry in Add/Remove Program when upgrade Hi Blair, Thank you for your explain. I still have some questions here. My requirement is to have multiple versions and also be able to upgrade some. In my last email, the Version 3 should be able to upgrade Version1. It means version 1 should be removed. And Version 2 is kept untouched. But now I set OnlyDetect="yes". When I install Version 3 to the path of Version 1, all these 3 versions stay in the system. And in the future, I want to show the installed software in the Listbox, and ask user to select which one to upgrade, there will be 3 items there, same as Add/Remove Program. It is confused. Version 2 has been upgraded (remove). It should not be shown there. Is it possible to realize my requirement? Best regards, Chunyan -----Ursprüngliche Nachricht----- Von: Blair [mailto:[hidden email]] Gesendet: Freitag, 6. November 2009 15:59 An: 'General discussion for Windows Installer XML toolset.' Betreff: Re: [WiX-users] New Entry in Add/Remove Program when upgrade You could try removing OnlyDetect="no" and adding a condition to the RemoveExistingProducts action. However, then version 3 in your scenario will remove both versions 1 and 2 (instead of just 1). Your requirement to leave multiple versions without forcing each to use a different path is the problem. It doesn't leave you with many options. -----Original Message----- From: Jiang, Chunyan (GE Healthcare) [mailto:[hidden email]] Sent: Friday, November 06, 2009 1:59 AM To: General discussion for Windows Installer XML toolset. Subject: [WiX-users] New Entry in Add/Remove Program when upgrade Hi wix-users, I developed one setup msi. And I want it to be upgradable. The requirement is: 1. Version 1 install to PathA. (New Install) 2. Version 2 install to PathB. (New Install) 3. Version 3 install to PathA. (Upgrade) The setup meets the requairment. However, when I perform the above actions, there are 3 items in Add/Remove Program list. Version 1 and Version 3 are in the same path. Actually there are 2 installs, since version 3 just upgrades version 2. I consider the reason is that I set <UpgradeVersion OnlyDetect="yes" Property="PREVIOUSFOUND" ... Here Onlydetect = "yes". I know if I set OnlyDetect="No", then upgrade will replace the older version. And there is no old version item in Add/Remove Program list. But if I set OnlyDetect="No", when I perform second step (install Version 2 to PathB(New Install)), the system will check last install (Version 1 in PathA), and remove the files in PathA. I don't what to break install 1. Is there one way to resolve my problem? Regards Chunyan ---------------------------------------------------------------------------- -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ WiX-users mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/wix-users ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ WiX-users mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/wix-users ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ WiX-users mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/wix-users ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ WiX-users mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/wix-users ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ WiX-users mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/wix-users |
||||||||||||||||
|
Blair-2
|
You can do this with one MSI (I don't see how two MSIs would do anything
more than confuse the issue even more) but you have to know BEFORE you start running the MSI whether you will be upgrading or not. Since that decision depends on the user's chosen installation path, which is gathered in the UI, that decision has to be made via UI BEFORE the MSI starts to run. In other words, drop Windows Installer's UI, and put the UI into your bootstrapping exe. Your bootstrapper will know your UpgradeCode and will do the same product enumeration that the Upgrade table enables, and will check the installation paths of the installed versions the same as your custom action does, and will remove the old version(s) that match the installation paths either before or after (more efficient) it installs the upgrading version. -----Original Message----- From: Jiang, Chunyan (GE Healthcare) [mailto:[hidden email]] Sent: Wednesday, November 11, 2009 6:32 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] New Entry in Add/Remove Program when upgrade Hi, I would like to clarify my requirement again. I read thought the WiX Tutorial 4. And I hope I could develop one setup.msi, which could combine "Minior upgrades" and "New Install". In my scenario, if updage Version 3 to Version 1 in PathA, it should do the "Minor upgrades". It doesn't not change the ProductID. And it only changes the product version and some files, not totally remove all the last install. But if Version 3 installs to a new path, it can act as a new install. Is it possilbe to do this in one setup.msi? If it is not, I want to develop two msi, one is for new install, one is for update. And use an external executable to decide which msi is called. However, there are 90% content same in the NewInstall.msi and Update.msi. Is it possible to create a common part that these two msi can call it? Best regards, Chunyan -----Ursprüngliche Nachricht----- Von: Jiang, Chunyan (GE Healthcare) Gesendet: Mittwoch, 11. November 2009 11:24 An: General discussion for Windows Installer XML toolset. Betreff: Re: [WiX-users] New Entry in Add/Remove Program when upgrade Hi Blair, I would like to ask you if I want to realize my scenario, is it possible to write a custom action to realize removing Version 1? Here I set the main msi still as OnlyDetect="yes". But when select one install from the dialog (Version 1) to upgrade, do the removing verion 1 in the custom action. This custom action only does remove the selected version, don't do the Detect, therefore don't touch version 2. Is it possible? And how to realize it? Regards, Chunyan -----Ursprüngliche Nachricht----- Von: Jiang, Chunyan (GE Healthcare) Gesendet: Mittwoch, 11. November 2009 10:38 An: General discussion for Windows Installer XML toolset. Betreff: Re: [WiX-users] New Entry in Add/Remove Program when upgrade Hi Blair, Thank you for your explain. I still have some questions here. My requirement is to have multiple versions and also be able to upgrade some. In my last email, the Version 3 should be able to upgrade Version1. It means version 1 should be removed. And Version 2 is kept untouched. But now I set OnlyDetect="yes". When I install Version 3 to the path of Version 1, all these 3 versions stay in the system. And in the future, I want to show the installed software in the Listbox, and ask user to select which one to upgrade, there will be 3 items there, same as Add/Remove Program. It is confused. Version 2 has been upgraded (remove). It should not be shown there. Is it possible to realize my requirement? Best regards, Chunyan -----Ursprüngliche Nachricht----- Von: Blair [mailto:[hidden email]] Gesendet: Freitag, 6. November 2009 15:59 An: 'General discussion for Windows Installer XML toolset.' Betreff: Re: [WiX-users] New Entry in Add/Remove Program when upgrade You could try removing OnlyDetect="no" and adding a condition to the RemoveExistingProducts action. However, then version 3 in your scenario will remove both versions 1 and 2 (instead of just 1). Your requirement to leave multiple versions without forcing each to use a different path is the problem. It doesn't leave you with many options. -----Original Message----- From: Jiang, Chunyan (GE Healthcare) [mailto:[hidden email]] Sent: Friday, November 06, 2009 1:59 AM To: General discussion for Windows Installer XML toolset. Subject: [WiX-users] New Entry in Add/Remove Program when upgrade Hi wix-users, I developed one setup msi. And I want it to be upgradable. The requirement is: 1. Version 1 install to PathA. (New Install) 2. Version 2 install to PathB. (New Install) 3. Version 3 install to PathA. (Upgrade) The setup meets the requairment. However, when I perform the above actions, there are 3 items in Add/Remove Program list. Version 1 and Version 3 are in the same path. Actually there are 2 installs, since version 3 just upgrades version 2. I consider the reason is that I set <UpgradeVersion OnlyDetect="yes" Property="PREVIOUSFOUND" ... Here Onlydetect = "yes". I know if I set OnlyDetect="No", then upgrade will replace the older version. And there is no old version item in Add/Remove Program list. But if I set OnlyDetect="No", when I perform second step (install Version 2 to PathB(New Install)), the system will check last install (Version 1 in PathA), and remove the files in PathA. I don't what to break install 1. Is there one way to resolve my problem? Regards Chunyan ---------------------------------------------------------------------------- -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ WiX-users mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/wix-users ---------------------------------------------------------------------------- -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ WiX-users mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/wix-users ---------------------------------------------------------------------------- -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ WiX-users mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/wix-users ---------------------------------------------------------------------------- -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ WiX-users mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/wix-users ---------------------------------------------------------------------------- -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ WiX-users mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/wix-users ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ WiX-users mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/wix-users |
||||||||||||||||
|
Chunyan
|
Hi Blair,
Thanks a lot for your suggestion. Here I would like to summarize the workflow: Bootstraper.exe should do the following steps: * Do the UI, list all installed path, ask user to select one to upgrade * When one installation is selected, remove this installation (should not totally remove. There are some files must retain.) * Call MSI to install new version in this path MSI should do the following steps: * Upgrade the selected installation. (Minior upgrade, keep the Product ID, change the version number) * Or do the new install as demand Here I have one question. In my requirement, the selected installation should not be removed totally. There are some files must be retained. So the upgrade should not be the "major upgrade", but the "minior upgrade". The best way is to make one MSI to define which files are used to upgrade, which files are not for upgrade. Could you give me some idea how to realize it? Regards, Chunyan -----Ursprüngliche Nachricht----- Von: Blair [mailto:[hidden email]] Gesendet: Mittwoch, 11. November 2009 18:46 An: 'General discussion for Windows Installer XML toolset.' Betreff: Re: [WiX-users] New Entry in Add/Remove Program when upgrade You can do this with one MSI (I don't see how two MSIs would do anything more than confuse the issue even more) but you have to know BEFORE you start running the MSI whether you will be upgrading or not. Since that decision depends on the user's chosen installation path, which is gathered in the UI, that decision has to be made via UI BEFORE the MSI starts to run. In other words, drop Windows Installer's UI, and put the UI into your bootstrapping exe. Your bootstrapper will know your UpgradeCode and will do the same product enumeration that the Upgrade table enables, and will check the installation paths of the installed versions the same as your custom action does, and will remove the old version(s) that match the installation paths either before or after (more efficient) it installs the upgrading version. -----Original Message----- From: Jiang, Chunyan (GE Healthcare) [mailto:[hidden email]] Sent: Wednesday, November 11, 2009 6:32 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] New Entry in Add/Remove Program when upgrade Hi, I would like to clarify my requirement again. I read thought the WiX Tutorial 4. And I hope I could develop one setup.msi, which could combine "Minior upgrades" and "New Install". In my scenario, if updage Version 3 to Version 1 in PathA, it should do the "Minor upgrades". It doesn't not change the ProductID. And it only changes the product version and some files, not totally remove all the last install. But if Version 3 installs to a new path, it can act as a new install. Is it possilbe to do this in one setup.msi? If it is not, I want to develop two msi, one is for new install, one is for update. And use an external executable to decide which msi is called. However, there are 90% content same in the NewInstall.msi and Update.msi. Is it possible to create a common part that these two msi can call it? Best regards, Chunyan -----Ursprüngliche Nachricht----- Von: Jiang, Chunyan (GE Healthcare) Gesendet: Mittwoch, 11. November 2009 11:24 An: General discussion for Windows Installer XML toolset. Betreff: Re: [WiX-users] New Entry in Add/Remove Program when upgrade Hi Blair, I would like to ask you if I want to realize my scenario, is it possible to write a custom action to realize removing Version 1? Here I set the main msi still as OnlyDetect="yes". But when select one install from the dialog (Version 1) to upgrade, do the removing verion 1 in the custom action. This custom action only does remove the selected version, don't do the Detect, therefore don't touch version 2. Is it possible? And how to realize it? Regards, Chunyan -----Ursprüngliche Nachricht----- Von: Jiang, Chunyan (GE Healthcare) Gesendet: Mittwoch, 11. November 2009 10:38 An: General discussion for Windows Installer XML toolset. Betreff: Re: [WiX-users] New Entry in Add/Remove Program when upgrade Hi Blair, Thank you for your explain. I still have some questions here. My requirement is to have multiple versions and also be able to upgrade some. In my last email, the Version 3 should be able to upgrade Version1. It means version 1 should be removed. And Version 2 is kept untouched. But now I set OnlyDetect="yes". When I install Version 3 to the path of Version 1, all these 3 versions stay in the system. And in the future, I want to show the installed software in the Listbox, and ask user to select which one to upgrade, there will be 3 items there, same as Add/Remove Program. It is confused. Version 2 has been upgraded (remove). It should not be shown there. Is it possible to realize my requirement? Best regards, Chunyan -----Ursprüngliche Nachricht----- Von: Blair [mailto:[hidden email]] Gesendet: Freitag, 6. November 2009 15:59 An: 'General discussion for Windows Installer XML toolset.' Betreff: Re: [WiX-users] New Entry in Add/Remove Program when upgrade You could try removing OnlyDetect="no" and adding a condition to the RemoveExistingProducts action. However, then version 3 in your scenario will remove both versions 1 and 2 (instead of just 1). Your requirement to leave multiple versions without forcing each to use a different path is the problem. It doesn't leave you with many options. -----Original Message----- From: Jiang, Chunyan (GE Healthcare) [mailto:[hidden email]] Sent: Friday, November 06, 2009 1:59 AM To: General discussion for Windows Installer XML toolset. Subject: [WiX-users] New Entry in Add/Remove Program when upgrade Hi wix-users, I developed one setup msi. And I want it to be upgradable. The requirement is: 1. Version 1 install to PathA. (New Install) 2. Version 2 install to PathB. (New Install) 3. Version 3 install to PathA. (Upgrade) The setup meets the requairment. However, when I perform the above actions, there are 3 items in Add/Remove Program list. Version 1 and Version 3 are in the same path. Actually there are 2 installs, since version 3 just upgrades version 2. I consider the reason is that I set <UpgradeVersion OnlyDetect="yes" Property="PREVIOUSFOUND" ... Here Onlydetect = "yes". I know if I set OnlyDetect="No", then upgrade will replace the older version. And there is no old version item in Add/Remove Program list. But if I set OnlyDetect="No", when I perform second step (install Version 2 to PathB(New Install)), the system will check last install (Version 1 in PathA), and remove the files in PathA. I don't what to break install 1. Is there one way to resolve my problem? Regards Chunyan ---------------------------------------------------------------------------- -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ WiX-users mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/wix-users ---------------------------------------------------------------------------- -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ WiX-users mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/wix-users ---------------------------------------------------------------------------- -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ WiX-users mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/wix-users ---------------------------------------------------------------------------- -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ WiX-users mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/wix-users ---------------------------------------------------------------------------- -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ WiX-users mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/wix-users ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ WiX-users mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/wix-users ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ WiX-users mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/wix-users |
||||||||||||||||
|
Chunyan
|
Hi,
Since my requirement is special, which includes both new install and update, I would like to design my package as this: * One MSI(installation package) to do the new install * One MSP (patchwork) to do the update * One MSM (merge module) to contain the common part of new install and update Both MSI and MSP refer to MSM for the common part. And there is no duplicate files in the whole installation CD. The Bootstraper.exe has UI and decides when to do new install (call MSI), when to do update (call MSP). Do you think it is a possible solution for my issue? Regards, Chunyan -----Ursprüngliche Nachricht----- Von: Jiang, Chunyan (GE Healthcare) Gesendet: Donnerstag, 12. November 2009 10:06 An: General discussion for Windows Installer XML toolset. Betreff: Re: [WiX-users] New Entry in Add/Remove Program when upgrade Hi Blair, Thanks a lot for your suggestion. Here I would like to summarize the workflow: Bootstraper.exe should do the following steps: * Do the UI, list all installed path, ask user to select one to upgrade * When one installation is selected, remove this installation (should not totally remove. There are some files must retain.) * Call MSI to install new version in this path MSI should do the following steps: * Upgrade the selected installation. (Minior upgrade, keep the Product ID, change the version number, keep some files, and remove all files) * Or do the new install as demand Here I have one question. In my requirement, the selected installation should not be removed totally. There are some files must be retained. So the upgrade should not be the "major upgrade", but the "minior upgrade". The best way is to make one MSI to define which files are used to upgrade, which files are not for upgrade. Could you give me some idea how to realize it? Regards, Chunyan -----Ursprüngliche Nachricht----- Von: Blair [mailto:[hidden email]] Gesendet: Mittwoch, 11. November 2009 18:46 An: 'General discussion for Windows Installer XML toolset.' Betreff: Re: [WiX-users] New Entry in Add/Remove Program when upgrade You can do this with one MSI (I don't see how two MSIs would do anything more than confuse the issue even more) but you have to know BEFORE you start running the MSI whether you will be upgrading or not. Since that decision depends on the user's chosen installation path, which is gathered in the UI, that decision has to be made via UI BEFORE the MSI starts to run. In other words, drop Windows Installer's UI, and put the UI into your bootstrapping exe. Your bootstrapper will know your UpgradeCode and will do the same product enumeration that the Upgrade table enables, and will check the installation paths of the installed versions the same as your custom action does, and will remove the old version(s) that match the installation paths either before or after (more efficient) it installs the upgrading version. -----Original Message----- From: Jiang, Chunyan (GE Healthcare) [mailto:[hidden email]] Sent: Wednesday, November 11, 2009 6:32 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] New Entry in Add/Remove Program when upgrade Hi, I would like to clarify my requirement again. I read thought the WiX Tutorial 4. And I hope I could develop one setup.msi, which could combine "Minior upgrades" and "New Install". In my scenario, if updage Version 3 to Version 1 in PathA, it should do the "Minor upgrades". It doesn't not change the ProductID. And it only changes the product version and some files, not totally remove all the last install. But if Version 3 installs to a new path, it can act as a new install. Is it possilbe to do this in one setup.msi? If it is not, I want to develop two msi, one is for new install, one is for update. And use an external executable to decide which msi is called. However, there are 90% content same in the NewInstall.msi and Update.msi. Is it possible to create a common part that these two msi can call it? Best regards, Chunyan -----Ursprüngliche Nachricht----- Von: Jiang, Chunyan (GE Healthcare) Gesendet: Mittwoch, 11. November 2009 11:24 An: General discussion for Windows Installer XML toolset. Betreff: Re: [WiX-users] New Entry in Add/Remove Program when upgrade Hi Blair, I would like to ask you if I want to realize my scenario, is it possible to write a custom action to realize removing Version 1? Here I set the main msi still as OnlyDetect="yes". But when select one install from the dialog (Version 1) to upgrade, do the removing verion 1 in the custom action. This custom action only does remove the selected version, don't do the Detect, therefore don't touch version 2. Is it possible? And how to realize it? Regards, Chunyan -----Ursprüngliche Nachricht----- Von: Jiang, Chunyan (GE Healthcare) Gesendet: Mittwoch, 11. November 2009 10:38 An: General discussion for Windows Installer XML toolset. Betreff: Re: [WiX-users] New Entry in Add/Remove Program when upgrade Hi Blair, Thank you for your explain. I still have some questions here. My requirement is to have multiple versions and also be able to upgrade some. In my last email, the Version 3 should be able to upgrade Version1. It means version 1 should be removed. And Version 2 is kept untouched. But now I set OnlyDetect="yes". When I install Version 3 to the path of Version 1, all these 3 versions stay in the system. And in the future, I want to show the installed software in the Listbox, and ask user to select which one to upgrade, there will be 3 items there, same as Add/Remove Program. It is confused. Version 2 has been upgraded (remove). It should not be shown there. Is it possible to realize my requirement? Best regards, Chunyan -----Ursprüngliche Nachricht----- Von: Blair [mailto:[hidden email]] Gesendet: Freitag, 6. November 2009 15:59 An: 'General discussion for Windows Installer XML toolset.' Betreff: Re: [WiX-users] New Entry in Add/Remove Program when upgrade You could try removing OnlyDetect="no" and adding a condition to the RemoveExistingProducts action. However, then version 3 in your scenario will remove both versions 1 and 2 (instead of just 1). Your requirement to leave multiple versions without forcing each to use a different path is the problem. It doesn't leave you with many options. -----Original Message----- From: Jiang, Chunyan (GE Healthcare) [mailto:[hidden email]] Sent: Friday, November 06, 2009 1:59 AM To: General discussion for Windows Installer XML toolset. Subject: [WiX-users] New Entry in Add/Remove Program when upgrade Hi wix-users, I developed one setup msi. And I want it to be upgradable. The requirement is: 1. Version 1 install to PathA. (New Install) 2. Version 2 install to PathB. (New Install) 3. Version 3 install to PathA. (Upgrade) The setup meets the requairment. However, when I perform the above actions, there are 3 items in Add/Remove Program list. Version 1 and Version 3 are in the same path. Actually there are 2 installs, since version 3 just upgrades version 2. I consider the reason is that I set <UpgradeVersion OnlyDetect="yes" Property="PREVIOUSFOUND" ... Here Onlydetect = "yes". I know if I set OnlyDetect="No", then upgrade will replace the older version. And there is no old version item in Add/Remove Program list. But if I set OnlyDetect="No", when I perform second step (install Version 2 to PathB(New Install)), the system will check last install (Version 1 in PathA), and remove the files in PathA. I don't what to break install 1. Is there one way to resolve my problem? Regards Chunyan ---------------------------------------------------------------------------- -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ WiX-users mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/wix-users ---------------------------------------------------------------------------- -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ WiX-users mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/wix-users ---------------------------------------------------------------------------- -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ WiX-users mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/wix-users ---------------------------------------------------------------------------- -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ WiX-users mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/wix-users ---------------------------------------------------------------------------- -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ WiX-users mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/wix-users ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ WiX-users mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/wix-users ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ WiX-users mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/wix-users ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ WiX-users mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/wix-users |
||||||||||||||||
|
Blair-2
|
In reply to this post
by Chunyan
If the ProductCode is the same (Minor Upgrade), you can't change directories
AND leave the previous installation in an old directory (there is no side-by-side installation of more than one instance of the same ProductCode). If the ProductCode is different (Major Upgrade), you have to either have the MSI remove previous installations (without considering the paths) or you have to have your bootstrapper remove the previous installations (based on the paths). You can't have MSI remove the old version, but your removing the old version works the same way as MSI would, do it, AND you can condition the removal upon successful installation, in addition to adding properties so that the removal suppresses removal custom actions if needed. If you use a Major Upgrade on the same installation path, all components with the same GUID and KeyPath will be left alone when the previous product is removed, so Major Upgrades with the bootstrapper are the way to go to meet your requirements. I don't see how Minor Upgrades could help you (unless you either limit the number of simultaneous installations OR restrict the installation paths to a fixed number of possibilities [different twist on the same theme]). -----Original Message----- From: Jiang, Chunyan (GE Healthcare) [mailto:[hidden email]] Sent: Thursday, November 12, 2009 1:06 AM To: General discussion for Windows Installer XML toolset. Cc: [hidden email] Subject: AW: [WiX-users] New Entry in Add/Remove Program when upgrade Hi Blair, Thanks a lot for your suggestion. Here I would like to summarize the workflow: Bootstraper.exe should do the following steps: * Do the UI, list all installed path, ask user to select one to upgrade * When one installation is selected, remove this installation (should not totally remove. There are some files must retain.) * Call MSI to install new version in this path MSI should do the following steps: * Upgrade the selected installation. (Minior upgrade, keep the Product ID, change the version number) * Or do the new install as demand Here I have one question. In my requirement, the selected installation should not be removed totally. There are some files must be retained. So the upgrade should not be the "major upgrade", but the "minior upgrade". The best way is to make one MSI to define which files are used to upgrade, which files are not for upgrade. Could you give me some idea how to realize it? Regards, Chunyan -----Ursprüngliche Nachricht----- Von: Blair [mailto:[hidden email]] Gesendet: Mittwoch, 11. November 2009 18:46 An: 'General discussion for Windows Installer XML toolset.' Betreff: Re: [WiX-users] New Entry in Add/Remove Program when upgrade You can do this with one MSI (I don't see how two MSIs would do anything more than confuse the issue even more) but you have to know BEFORE you start running the MSI whether you will be upgrading or not. Since that decision depends on the user's chosen installation path, which is gathered in the UI, that decision has to be made via UI BEFORE the MSI starts to run. In other words, drop Windows Installer's UI, and put the UI into your bootstrapping exe. Your bootstrapper will know your UpgradeCode and will do the same product enumeration that the Upgrade table enables, and will check the installation paths of the installed versions the same as your custom action does, and will remove the old version(s) that match the installation paths either before or after (more efficient) it installs the upgrading version. -----Original Message----- From: Jiang, Chunyan (GE Healthcare) [mailto:[hidden email]] Sent: Wednesday, November 11, 2009 6:32 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] New Entry in Add/Remove Program when upgrade Hi, I would like to clarify my requirement again. I read thought the WiX Tutorial 4. And I hope I could develop one setup.msi, which could combine "Minior upgrades" and "New Install". In my scenario, if updage Version 3 to Version 1 in PathA, it should do the "Minor upgrades". It doesn't not change the ProductID. And it only changes the product version and some files, not totally remove all the last install. But if Version 3 installs to a new path, it can act as a new install. Is it possilbe to do this in one setup.msi? If it is not, I want to develop two msi, one is for new install, one is for update. And use an external executable to decide which msi is called. However, there are 90% content same in the NewInstall.msi and Update.msi. Is it possible to create a common part that these two msi can call it? Best regards, Chunyan -----Ursprüngliche Nachricht----- Von: Jiang, Chunyan (GE Healthcare) Gesendet: Mittwoch, 11. November 2009 11:24 An: General discussion for Windows Installer XML toolset. Betreff: Re: [WiX-users] New Entry in Add/Remove Program when upgrade Hi Blair, I would like to ask you if I want to realize my scenario, is it possible to write a custom action to realize removing Version 1? Here I set the main msi still as OnlyDetect="yes". But when select one install from the dialog (Version 1) to upgrade, do the removing verion 1 in the custom action. This custom action only does remove the selected version, don't do the Detect, therefore don't touch version 2. Is it possible? And how to realize it? Regards, Chunyan -----Ursprüngliche Nachricht----- Von: Jiang, Chunyan (GE Healthcare) Gesendet: Mittwoch, 11. November 2009 10:38 An: General discussion for Windows Installer XML toolset. Betreff: Re: [WiX-users] New Entry in Add/Remove Program when upgrade Hi Blair, Thank you for your explain. I still have some questions here. My requirement is to have multiple versions and also be able to upgrade some. In my last email, the Version 3 should be able to upgrade Version1. It means version 1 should be removed. And Version 2 is kept untouched. But now I set OnlyDetect="yes". When I install Version 3 to the path of Version 1, all these 3 versions stay in the system. And in the future, I want to show the installed software in the Listbox, and ask user to select which one to upgrade, there will be 3 items there, same as Add/Remove Program. It is confused. Version 2 has been upgraded (remove). It should not be shown there. Is it possible to realize my requirement? Best regards, Chunyan -----Ursprüngliche Nachricht----- Von: Blair [mailto:[hidden email]] Gesendet: Freitag, 6. November 2009 15:59 An: 'General discussion for Windows Installer XML toolset.' Betreff: Re: [WiX-users] New Entry in Add/Remove Program when upgrade You could try removing OnlyDetect="no" and adding a condition to the RemoveExistingProducts action. However, then version 3 in your scenario will remove both versions 1 and 2 (instead of just 1). Your requirement to leave multiple versions without forcing each to use a different path is the problem. It doesn't leave you with many options. -----Original Message----- From: Jiang, Chunyan (GE Healthcare) [mailto:[hidden email]] Sent: Friday, November 06, 2009 1:59 AM To: General discussion for Windows Installer XML toolset. Subject: [WiX-users] New Entry in Add/Remove Program when upgrade Hi wix-users, I developed one setup msi. And I want it to be upgradable. The requirement is: 1. Version 1 install to PathA. (New Install) 2. Version 2 install to PathB. (New Install) 3. Version 3 install to PathA. (Upgrade) The setup meets the requairment. However, when I perform the above actions, there are 3 items in Add/Remove Program list. Version 1 and Version 3 are in the same path. Actually there are 2 installs, since version 3 just upgrades version 2. I consider the reason is that I set <UpgradeVersion OnlyDetect="yes" Property="PREVIOUSFOUND" ... Here Onlydetect = "yes". I know if I set OnlyDetect="No", then upgrade will replace the older version. And there is no old version item in Add/Remove Program list. But if I set OnlyDetect="No", when I perform second step (install Version 2 to PathB(New Install)), the system will check last install (Version 1 in PathA), and remove the files in PathA. I don't what to break install 1. Is there one way to resolve my problem? Regards Chunyan ---------------------------------------------------------------------------- -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ WiX-users mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/wix-users ---------------------------------------------------------------------------- -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ WiX-users mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/wix-users ---------------------------------------------------------------------------- -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ WiX-users mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/wix-users ---------------------------------------------------------------------------- -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ WiX-users mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/wix-users ---------------------------------------------------------------------------- -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ WiX-users mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/wix-users ---------------------------------------------------------------------------- -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ WiX-users mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/wix-users ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ WiX-users mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/wix-users |
||||||||||||||||
|
Blair-2
|
In reply to this post
by Chunyan
Only when you drop your requirement to install multiple versions to
different paths simultaneously. -----Original Message----- From: Jiang, Chunyan (GE Healthcare) [mailto:[hidden email]] Sent: Thursday, November 12, 2009 2:40 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] New Entry in Add/Remove Program when upgrade Hi, Since my requirement is special, which includes both new install and update, I would like to design my package as this: * One MSI(installation package) to do the new install * One MSP (patchwork) to do the update * One MSM (merge module) to contain the common part of new install and update Both MSI and MSP refer to MSM for the common part. And there is no duplicate files in the whole installation CD. The Bootstraper.exe has UI and decides when to do new install (call MSI), when to do update (call MSP). Do you think it is a possible solution for my issue? Regards, Chunyan -----Ursprüngliche Nachricht----- Von: Jiang, Chunyan (GE Healthcare) Gesendet: Donnerstag, 12. November 2009 10:06 An: General discussion for Windows Installer XML toolset. Betreff: Re: [WiX-users] New Entry in Add/Remove Program when upgrade Hi Blair, Thanks a lot for your suggestion. Here I would like to summarize the workflow: Bootstraper.exe should do the following steps: * Do the UI, list all installed path, ask user to select one to upgrade * When one installation is selected, remove this installation (should not totally remove. There are some files must retain.) * Call MSI to install new version in this path MSI should do the following steps: * Upgrade the selected installation. (Minior upgrade, keep the Product ID, change the version number, keep some files, and remove all files) * Or do the new install as demand Here I have one question. In my requirement, the selected installation should not be removed totally. There are some files must be retained. So the upgrade should not be the "major upgrade", but the "minior upgrade". The best way is to make one MSI to define which files are used to upgrade, which files are not for upgrade. Could you give me some idea how to realize it? Regards, Chunyan -----Ursprüngliche Nachricht----- Von: Blair [mailto:[hidden email]] Gesendet: Mittwoch, 11. November 2009 18:46 An: 'General discussion for Windows Installer XML toolset.' Betreff: Re: [WiX-users] New Entry in Add/Remove Program when upgrade You can do this with one MSI (I don't see how two MSIs would do anything more than confuse the issue even more) but you have to know BEFORE you start running the MSI whether you will be upgrading or not. Since that decision depends on the user's chosen installation path, which is gathered in the UI, that decision has to be made via UI BEFORE the MSI starts to run. In other words, drop Windows Installer's UI, and put the UI into your bootstrapping exe. Your bootstrapper will know your UpgradeCode and will do the same product enumeration that the Upgrade table enables, and will check the installation paths of the installed versions the same as your custom action does, and will remove the old version(s) that match the installation paths either before or after (more efficient) it installs the upgrading version. -----Original Message----- From: Jiang, Chunyan (GE Healthcare) [mailto:[hidden email]] Sent: Wednesday, November 11, 2009 6:32 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] New Entry in Add/Remove Program when upgrade Hi, I would like to clarify my requirement again. I read thought the WiX Tutorial 4. And I hope I could develop one setup.msi, which could combine "Minior upgrades" and "New Install". In my scenario, if updage Version 3 to Version 1 in PathA, it should do the "Minor upgrades". It doesn't not change the ProductID. And it only changes the product version and some files, not totally remove all the last install. But if Version 3 installs to a new path, it can act as a new install. Is it possilbe to do this in one setup.msi? If it is not, I want to develop two msi, one is for new install, one is for update. And use an external executable to decide which msi is called. However, there are 90% content same in the NewInstall.msi and Update.msi. Is it possible to create a common part that these two msi can call it? Best regards, Chunyan -----Ursprüngliche Nachricht----- Von: Jiang, Chunyan (GE Healthcare) Gesendet: Mittwoch, 11. November 2009 11:24 An: General discussion for Windows Installer XML toolset. Betreff: Re: [WiX-users] New Entry in Add/Remove Program when upgrade Hi Blair, I would like to ask you if I want to realize my scenario, is it possible to write a custom action to realize removing Version 1? Here I set the main msi still as OnlyDetect="yes". But when select one install from the dialog (Version 1) to upgrade, do the removing verion 1 in the custom action. This custom action only does remove the selected version, don't do the Detect, therefore don't touch version 2. Is it possible? And how to realize it? Regards, Chunyan -----Ursprüngliche Nachricht----- Von: Jiang, Chunyan (GE Healthcare) Gesendet: Mittwoch, 11. November 2009 10:38 An: General discussion for Windows Installer XML toolset. Betreff: Re: [WiX-users] New Entry in Add/Remove Program when upgrade Hi Blair, Thank you for your explain. I still have some questions here. My requirement is to have multiple versions and also be able to upgrade some. In my last email, the Version 3 should be able to upgrade Version1. It means version 1 should be removed. And Version 2 is kept untouched. But now I set OnlyDetect="yes". When I install Version 3 to the path of Version 1, all these 3 versions stay in the system. And in the future, I want to show the installed software in the Listbox, and ask user to select which one to upgrade, there will be 3 items there, same as Add/Remove Program. It is confused. Version 2 has been upgraded (remove). It should not be shown there. Is it possible to realize my requirement? Best regards, Chunyan -----Ursprüngliche Nachricht----- Von: Blair [mailto:[hidden email]] Gesendet: Freitag, 6. November 2009 15:59 An: 'General discussion for Windows Installer XML toolset.' Betreff: Re: [WiX-users] New Entry in Add/Remove Program when upgrade You could try removing OnlyDetect="no" and adding a condition to the RemoveExistingProducts action. However, then version 3 in your scenario will remove both versions 1 and 2 (instead of just 1). Your requirement to leave multiple versions without forcing each to use a different path is the problem. It doesn't leave you with many options. -----Original Message----- From: Jiang, Chunyan (GE Healthcare) [mailto:[hidden email]] Sent: Friday, November 06, 2009 1:59 AM To: General discussion for Windows Installer XML toolset. Subject: [WiX-users] New Entry in Add/Remove Program when upgrade Hi wix-users, I developed one setup msi. And I want it to be upgradable. The requirement is: 1. Version 1 install to PathA. (New Install) 2. Version 2 install to PathB. (New Install) 3. Version 3 install to PathA. (Upgrade) The setup meets the requairment. However, when I perform the above actions, there are 3 items in Add/Remove Program list. Version 1 and Version 3 are in the same path. Actually there are 2 installs, since version 3 just upgrades version 2. I consider the reason is that I set <UpgradeVersion OnlyDetect="yes" Property="PREVIOUSFOUND" ... Here Onlydetect = "yes". I know if I set OnlyDetect="No", then upgrade will replace the older version. And there is no old version item in Add/Remove Program list. But if I set OnlyDetect="No", when I perform second step (install Version 2 to PathB(New Install)), the system will check last install (Version 1 in PathA), and remove the files in PathA. I don't what to break install 1. Is there one way to resolve my problem? Regards Chunyan ---------------------------------------------------------------------------- -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ WiX-users mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/wix-users ---------------------------------------------------------------------------- -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ WiX-users mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/wix-users ---------------------------------------------------------------------------- -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ WiX-users mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/wix-users ---------------------------------------------------------------------------- -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ WiX-users mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/wix-users ---------------------------------------------------------------------------- -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ WiX-users mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/wix-users ---------------------------------------------------------------------------- -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ WiX-users mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/wix-users ---------------------------------------------------------------------------- -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ WiX-users mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/wix-users ---------------------------------------------------------------------------- -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ WiX-users mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/wix-users ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ WiX-users mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/wix-users |
||||||||||||||||
|
Chunyan
|
Hi Blair,
I am sorry to confuse you on this issue. I think my requirement has been changed. I want to install multiple versions to different paths simultaneously. At the same time, there is requirement to update the specific installation. It must be minor upgrade, because there are some files should not be removed. So I think it is better to use two MSI to fulfill the task. And use bootstraper.exe to decide new install or upgrade. It makes things easy. However, I have a question for the minor upgrade MSI. Since there are mutliple versions installed, and user chooses which one to upgrade, the minor upgrade MSI doesn't know the Product ID. If I set a new Product ID to this minor upgrade MSI, is it possible to set it to another Product ID to this minor upgrade MSI when the installed version is selected by user? Does it work? value =::MsiSetPropertyW(hInstaller,L"ProductID",PreviousProduct); Best regards, Chunyan -----Ursprüngliche Nachricht----- Von: Blair [mailto:[hidden email]] Gesendet: Donnerstag, 12. November 2009 18:26 An: 'General discussion for Windows Installer XML toolset.' Betreff: Re: [WiX-users] New Entry in Add/Remove Program when upgrade Only when you drop your requirement to install multiple versions to different paths simultaneously. -----Original Message----- From: Jiang, Chunyan (GE Healthcare) [mailto:[hidden email]] Sent: Thursday, November 12, 2009 2:40 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] New Entry in Add/Remove Program when upgrade Hi, Since my requirement is special, which includes both new install and update, I would like to design my package as this: * One MSI(installation package) to do the new install * One MSP (patchwork) to do the update * One MSM (merge module) to contain the common part of new install and update Both MSI and MSP refer to MSM for the common part. And there is no duplicate files in the whole installation CD. The Bootstraper.exe has UI and decides when to do new install (call MSI), when to do update (call MSP). Do you think it is a possible solution for my issue? Regards, Chunyan -----Ursprüngliche Nachricht----- Von: Jiang, Chunyan (GE Healthcare) Gesendet: Donnerstag, 12. November 2009 10:06 An: General discussion for Windows Installer XML toolset. Betreff: Re: [WiX-users] New Entry in Add/Remove Program when upgrade Hi Blair, Thanks a lot for your suggestion. Here I would like to summarize the workflow: Bootstraper.exe should do the following steps: * Do the UI, list all installed path, ask user to select one to upgrade * When one installation is selected, remove this installation (should not totally remove. There are some files must retain.) * Call MSI to install new version in this path MSI should do the following steps: * Upgrade the selected installation. (Minior upgrade, keep the Product ID, change the version number, keep some files, and remove all files) * Or do the new install as demand Here I have one question. In my requirement, the selected installation should not be removed totally. There are some files must be retained. So the upgrade should not be the "major upgrade", but the "minior upgrade". The best way is to make one MSI to define which files are used to upgrade, which files are not for upgrade. Could you give me some idea how to realize it? Regards, Chunyan -----Ursprüngliche Nachricht----- Von: Blair [mailto:[hidden email]] Gesendet: Mittwoch, 11. November 2009 18:46 An: 'General discussion for Windows Installer XML toolset.' Betreff: Re: [WiX-users] New Entry in Add/Remove Program when upgrade You can do this with one MSI (I don't see how two MSIs would do anything more than confuse the issue even more) but you have to know BEFORE you start running the MSI whether you will be upgrading or not. Since that decision depends on the user's chosen installation path, which is gathered in the UI, that decision has to be made via UI BEFORE the MSI starts to run. In other words, drop Windows Installer's UI, and put the UI into your bootstrapping exe. Your bootstrapper will know your UpgradeCode and will do the same product enumeration that the Upgrade table enables, and will check the installation paths of the installed versions the same as your custom action does, and will remove the old version(s) that match the installation paths either before or after (more efficient) it installs the upgrading version. -----Original Message----- From: Jiang, Chunyan (GE Healthcare) [mailto:[hidden email]] Sent: Wednesday, November 11, 2009 6:32 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] New Entry in Add/Remove Program when upgrade Hi, I would like to clarify my requirement again. I read thought the WiX Tutorial 4. And I hope I could develop one setup.msi, which could combine "Minior upgrades" and "New Install". In my scenario, if updage Version 3 to Version 1 in PathA, it should do the "Minor upgrades". It doesn't not change the ProductID. And it only changes the product version and some files, not totally remove all the last install. But if Version 3 installs to a new path, it can act as a new install. Is it possilbe to do this in one setup.msi? If it is not, I want to develop two msi, one is for new install, one is for update. And use an external executable to decide which msi is called. However, there are 90% content same in the NewInstall.msi and Update.msi. Is it possible to create a common part that these two msi can call it? Best regards, Chunyan -----Ursprüngliche Nachricht----- Von: Jiang, Chunyan (GE Healthcare) Gesendet: Mittwoch, 11. November 2009 11:24 An: General discussion for Windows Installer XML toolset. Betreff: Re: [WiX-users] New Entry in Add/Remove Program when upgrade Hi Blair, I would like to ask you if I want to realize my scenario, is it possible to write a custom action to realize removing Version 1? Here I set the main msi still as OnlyDetect="yes". But when select one install from the dialog (Version 1) to upgrade, do the removing verion 1 in the custom action. This custom action only does remove the selected version, don't do the Detect, therefore don't touch version 2. Is it possible? And how to realize it? Regards, Chunyan -----Ursprüngliche Nachricht----- Von: Jiang, Chunyan (GE Healthcare) Gesendet: Mittwoch, 11. November 2009 10:38 An: General discussion for Windows Installer XML toolset. Betreff: Re: [WiX-users] New Entry in Add/Remove Program when upgrade Hi Blair, Thank you for your explain. I still have some questions here. My requirement is to have multiple versions and also be able to upgrade some. In my last email, the Version 3 should be able to upgrade Version1. It means version 1 should be removed. And Version 2 is kept untouched. But now I set OnlyDetect="yes". When I install Version 3 to the path of Version 1, all these 3 versions stay in the system. And in the future, I want to show the installed software in the Listbox, and ask user to select which one to upgrade, there will be 3 items there, same as Add/Remove Program. It is confused. Version 2 has been upgraded (remove). It should not be shown there. Is it possible to realize my requirement? Best regards, Chunyan -----Ursprüngliche Nachricht----- Von: Blair [mailto:[hidden email]] Gesendet: Freitag, 6. November 2009 15:59 An: 'General discussion for Windows Installer XML toolset.' Betreff: Re: [WiX-users] New Entry in Add/Remove Program when upgrade You could try removing OnlyDetect="no" and adding a condition to the RemoveExistingProducts action. However, then version 3 in your scenario will remove both versions 1 and 2 (instead of just 1). Your requirement to leave multiple versions without forcing each to use a different path is the problem. It doesn't leave you with many options. -----Original Message----- From: Jiang, Chunyan (GE Healthcare) [mailto:[hidden email]] Sent: Friday, November 06, 2009 1:59 AM To: General discussion for Windows Installer XML toolset. Subject: [WiX-users] New Entry in Add/Remove Program when upgrade Hi wix-users, I developed one setup msi. And I want it to be upgradable. The requirement is: 1. Version 1 install to PathA. (New Install) 2. Version 2 install to PathB. (New Install) 3. Version 3 install to PathA. (Upgrade) The setup meets the requairment. However, when I perform the above actions, there are 3 items in Add/Remove Program list. Version 1 and Version 3 are in the same path. Actually there are 2 installs, since version 3 just upgrades version 2. I consider the reason is that I set <UpgradeVersion OnlyDetect="yes" Property="PREVIOUSFOUND" ... Here Onlydetect = "yes". I know if I set OnlyDetect="No", then upgrade will replace the older version. And there is no old version item in Add/Remove Program list. But if I set OnlyDetect="No", when I perform second step (install Version 2 to PathB(New Install)), the system will check last install (Version 1 in PathA), and remove the files in PathA. I don't what to break install 1. Is there one way to resolve my problem? Regards Chunyan ---------------------------------------------------------------------------- -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ WiX-users mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/wix-users ---------------------------------------------------------------------------- -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ WiX-users mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/wix-users ---------------------------------------------------------------------------- -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ WiX-users mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/wix-users ---------------------------------------------------------------------------- -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ WiX-users mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/wix-users ---------------------------------------------------------------------------- -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ WiX-users mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/wix-users ---------------------------------------------------------------------------- -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ WiX-users mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/wix-users ---------------------------------------------------------------------------- -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ WiX-users mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/wix-users ---------------------------------------------------------------------------- -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ WiX-users mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/wix-users ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ WiX-users mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/wix-users ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ WiX-users mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/wix-users |
||||||||||||||||
|
Blair-2
|
As far as I know, no, it does not work.
-----Original Message----- From: Jiang, Chunyan (GE Healthcare) [mailto:[hidden email]] Sent: Friday, November 13, 2009 2:46 AM To: General discussion for Windows Installer XML toolset. Cc: [hidden email] Subject: AW: [WiX-users] New Entry in Add/Remove Program when upgrade Hi Blair, I am sorry to confuse you on this issue. I think my requirement has been changed. I want to install multiple versions to different paths simultaneously. At the same time, there is requirement to update the specific installation. It must be minor upgrade, because there are some files should not be removed. So I think it is better to use two MSI to fulfill the task. And use bootstraper.exe to decide new install or upgrade. It makes things easy. However, I have a question for the minor upgrade MSI. Since there are mutliple versions installed, and user chooses which one to upgrade, the minor upgrade MSI doesn't know the Product ID. If I set a new Product ID to this minor upgrade MSI, is it possible to set it to another Product ID to this minor upgrade MSI when the installed version is selected by user? Does it work? value =::MsiSetPropertyW(hInstaller,L"ProductID",PreviousProduct); Best regards, Chunyan -----Ursprüngliche Nachricht----- Von: Blair [mailto:[hidden email]] Gesendet: Donnerstag, 12. November 2009 18:26 An: 'General discussion for Windows Installer XML toolset.' Betreff: Re: [WiX-users] New Entry in Add/Remove Program when upgrade Only when you drop your requirement to install multiple versions to different paths simultaneously. -----Original Message----- From: Jiang, Chunyan (GE Healthcare) [mailto:[hidden email]] Sent: Thursday, November 12, 2009 2:40 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] New Entry in Add/Remove Program when upgrade Hi, Since my requirement is special, which includes both new install and update, I would like to design my package as this: * One MSI(installation package) to do the new install * One MSP (patchwork) to do the update * One MSM (merge module) to contain the common part of new install and update Both MSI and MSP refer to MSM for the common part. And there is no duplicate files in the whole installation CD. The Bootstraper.exe has UI and decides when to do new install (call MSI), when to do update (call MSP). Do you think it is a possible solution for my issue? Regards, Chunyan -----Ursprüngliche Nachricht----- Von: Jiang, Chunyan (GE Healthcare) Gesendet: Donnerstag, 12. November 2009 10:06 An: General discussion for Windows Installer XML toolset. Betreff: Re: [WiX-users] New Entry in Add/Remove Program when upgrade Hi Blair, Thanks a lot for your suggestion. Here I would like to summarize the workflow: Bootstraper.exe should do the following steps: * Do the UI, list all installed path, ask user to select one to upgrade * When one installation is selected, remove this installation (should not totally remove. There are some files must retain.) * Call MSI to install new version in this path MSI should do the following steps: * Upgrade the selected installation. (Minior upgrade, keep the Product ID, change the version number, keep some files, and remove all files) * Or do the new install as demand Here I have one question. In my requirement, the selected installation should not be removed totally. There are some files must be retained. So the upgrade should not be the "major upgrade", but the "minior upgrade". The best way is to make one MSI to define which files are used to upgrade, which files are not for upgrade. Could you give me some idea how to realize it? Regards, Chunyan -----Ursprüngliche Nachricht----- Von: Blair [mailto:[hidden email]] Gesendet: Mittwoch, 11. November 2009 18:46 An: 'General discussion for Windows Installer XML toolset.' Betreff: Re: [WiX-users] New Entry in Add/Remove Program when upgrade You can do this with one MSI (I don't see how two MSIs would do anything more than confuse the issue even more) but you have to know BEFORE you start running the MSI whether you will be upgrading or not. Since that decision depends on the user's chosen installation path, which is gathered in the UI, that decision has to be made via UI BEFORE the MSI starts to run. In other words, drop Windows Installer's UI, and put the UI into your bootstrapping exe. Your bootstrapper will know your UpgradeCode and will do the same product enumeration that the Upgrade table enables, and will check the installation paths of the installed versions the same as your custom action does, and will remove the old version(s) that match the installation paths either before or after (more efficient) it installs the upgrading version. -----Original Message----- From: Jiang, Chunyan (GE Healthcare) [mailto:[hidden email]] Sent: Wednesday, November 11, 2009 6:32 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] New Entry in Add/Remove Program when upgrade Hi, I would like to clarify my requirement again. I read thought the WiX Tutorial 4. And I hope I could develop one setup.msi, which could combine "Minior upgrades" and "New Install". In my scenario, if updage Version 3 to Version 1 in PathA, it should do the "Minor upgrades". It doesn't not change the ProductID. And it only changes the product version and some files, not totally remove all the last install. But if Version 3 installs to a new path, it can act as a new install. Is it possilbe to do this in one setup.msi? If it is not, I want to develop two msi, one is for new install, one is for update. And use an external executable to decide which msi is called. However, there are 90% content same in the NewInstall.msi and Update.msi. Is it possible to create a common part that these two msi can call it? Best regards, Chunyan -----Ursprüngliche Nachricht----- Von: Jiang, Chunyan (GE Healthcare) Gesendet: Mittwoch, 11. November 2009 11:24 An: General discussion for Windows Installer XML toolset. Betreff: Re: [WiX-users] New Entry in Add/Remove Program when upgrade Hi Blair, I would like to ask you if I want to realize my scenario, is it possible to write a custom action to realize removing Version 1? Here I set the main msi still as OnlyDetect="yes". But when select one install from the dialog (Version 1) to upgrade, do the removing verion 1 in the custom action. This custom action only does remove the selected version, don't do the Detect, therefore don't touch version 2. Is it possible? And how to realize it? Regards, Chunyan -----Ursprüngliche Nachricht----- Von: Jiang, Chunyan (GE Healthcare) Gesendet: Mittwoch, 11. November 2009 10:38 An: General discussion for Windows Installer XML toolset. Betreff: Re: [WiX-users] New Entry in Add/Remove Program when upgrade Hi Blair, Thank you for your explain. I still have some questions here. My requirement is to have multiple versions and also be able to upgrade some. In my last email, the Version 3 should be able to upgrade Version1. It means version 1 should be removed. And Version 2 is kept untouched. But now I set OnlyDetect="yes". When I install Version 3 to the path of Version 1, all these 3 versions stay in the system. And in the future, I want to show the installed software in the Listbox, and ask user to select which one to upgrade, there will be 3 items there, same as Add/Remove Program. It is confused. Version 2 has been upgraded (remove). It should not be shown there. Is it possible to realize my requirement? Best regards, Chunyan -----Ursprüngliche Nachricht----- Von: Blair [mailto:[hidden email]] Gesendet: Freitag, 6. November 2009 15:59 An: 'General discussion for Windows Installer XML toolset.' Betreff: Re: [WiX-users] New Entry in Add/Remove Program when upgrade You could try removing OnlyDetect="no" and adding a condition to the RemoveExistingProducts action. However, then version 3 in your scenario will remove both versions 1 and 2 (instead of just 1). Your requirement to leave multiple versions without forcing each to use a different path is the problem. It doesn't leave you with many options. -----Original Message----- From: Jiang, Chunyan (GE Healthcare) [mailto:[hidden email]] Sent: Friday, November 06, 2009 1:59 AM To: General discussion for Windows Installer XML toolset. Subject: [WiX-users] New Entry in Add/Remove Program when upgrade Hi wix-users, I developed one setup msi. And I want it to be upgradable. The requirement is: 1. Version 1 install to PathA. (New Install) 2. Version 2 install to PathB. (New Install) 3. Version 3 install to PathA. (Upgrade) The setup meets the requairment. However, when I perform the above actions, there are 3 items in Add/Remove Program list. Version 1 and Version 3 are in the same path. Actually there are 2 installs, since version 3 just upgrades version 2. I consider the reason is that I set <UpgradeVersion OnlyDetect="yes" Property="PREVIOUSFOUND" ... Here Onlydetect = "yes". I know if I set OnlyDetect="No", then upgrade will replace the older version. And there is no old version item in Add/Remove Program list. But if I set OnlyDetect="No", when I perform second step (install Version 2 to PathB(New Install)), the system will check last install (Version 1 in PathA), and remove the files in PathA. I don't what to break install 1. Is there one way to resolve my problem? Regards Chunyan ---------------------------------------------------------------------------- -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ WiX-users mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/wix-users ---------------------------------------------------------------------------- -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ WiX-users mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/wix-users ---------------------------------------------------------------------------- -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ WiX-users mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/wix-users ---------------------------------------------------------------------------- -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ WiX-users mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/wix-users ---------------------------------------------------------------------------- -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ WiX-users mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/wix-users ---------------------------------------------------------------------------- -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ WiX-users mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/wix-users ---------------------------------------------------------------------------- -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ WiX-users mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/wix-users ---------------------------------------------------------------------------- -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ WiX-users mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/wix-users ---------------------------------------------------------------------------- -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ WiX-users mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/wix-users ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ WiX-users mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/wix-users |
||||||||||||||||
|
Chunyan
|
Hi Blair,
I found an article from MSDN, which is talking about multiple instance. I think my requirement is similiar like multiple instance, although the software version could be different. The link is here http://msdn.microsoft.com/en-us/library/aa369528(VS.85).aspx It says: The easiest way to initiate a maintenance installation, and reinstall an instance, is to reference the product code of the instance. If you initiate the maintenance installation by using the package path, you must also specify the product code of the instance. From the command line, use the /n {Product Code} option. From code or script, use the MSIINSTANCEGUID property. And example: The following example reinstalls an instance without re-caching the package. The instance is referred to by its product code {00000001-0002-0000-0000-624474736554}. msiexec /I {00000001-0002-0000-0000-624474736554} REINSTALL=ALL REINSTALLMODE=omus /qb Does it mean that retrieving the installed ProductID, then using command line to pass it the install package. Does it meet my requirement that update the user selected installed software by minor upgrade, but does not know the ProductID ahead? Regards, Chunyan -----Ursprüngliche Nachricht----- Von: Blair [mailto:[hidden email]] Gesendet: Freitag, 13. November 2009 18:24 An: Jiang, Chunyan (GE Healthcare); 'General discussion for Windows Installer XML toolset.' Betreff: RE: [WiX-users] New Entry in Add/Remove Program when upgrade As far as I know, no, it does not work. -----Original Message----- From: Jiang, Chunyan (GE Healthcare) [mailto:[hidden email]] Sent: Friday, November 13, 2009 2:46 AM To: General discussion for Windows Installer XML toolset. Cc: [hidden email] Subject: AW: [WiX-users] New Entry in Add/Remove Program when upgrade Hi Blair, I am sorry to confuse you on this issue. I think my requirement has been changed. I want to install multiple versions to different paths simultaneously. At the same time, there is requirement to update the specific installation. It must be minor upgrade, because there are some files should not be removed. So I think it is better to use two MSI to fulfill the task. And use bootstraper.exe to decide new install or upgrade. It makes things easy. However, I have a question for the minor upgrade MSI. Since there are mutliple versions installed, and user chooses which one to upgrade, the minor upgrade MSI doesn't know the Product ID. If I set a new Product ID to this minor upgrade MSI, is it possible to set it to another Product ID to this minor upgrade MSI when the installed version is selected by user? Does it work? value =::MsiSetPropertyW(hInstaller,L"ProductID",PreviousProduct); Best regards, Chunyan -----Ursprüngliche Nachricht----- Von: Blair [mailto:[hidden email]] Gesendet: Donnerstag, 12. November 2009 18:26 An: 'General discussion for Windows Installer XML toolset.' Betreff: Re: [WiX-users] New Entry in Add/Remove Program when upgrade Only when you drop your requirement to install multiple versions to different paths simultaneously. -----Original Message----- From: Jiang, Chunyan (GE Healthcare) [mailto:[hidden email]] Sent: Thursday, November 12, 2009 2:40 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] New Entry in Add/Remove Program when upgrade Hi, Since my requirement is special, which includes both new install and update, I would like to design my package as this: * One MSI(installation package) to do the new install * One MSP (patchwork) to do the update * One MSM (merge module) to contain the common part of new install and update Both MSI and MSP refer to MSM for the common part. And there is no duplicate files in the whole installation CD. The Bootstraper.exe has UI and decides when to do new install (call MSI), when to do update (call MSP). Do you think it is a possible solution for my issue? Regards, Chunyan -----Ursprüngliche Nachricht----- Von: Jiang, Chunyan (GE Healthcare) Gesendet: Donnerstag, 12. November 2009 10:06 An: General discussion for Windows Installer XML toolset. Betreff: Re: [WiX-users] New Entry in Add/Remove Program when upgrade Hi Blair, Thanks a lot for your suggestion. Here I would like to summarize the workflow: Bootstraper.exe should do the following steps: * Do the UI, list all installed path, ask user to select one to upgrade * When one installation is selected, remove this installation (should not totally remove. There are some files must retain.) * Call MSI to install new version in this path MSI should do the following steps: * Upgrade the selected installation. (Minior upgrade, keep the Product ID, change the version number, keep some files, and remove all files) * Or do the new install as demand Here I have one question. In my requirement, the selected installation should not be removed totally. There are some files must be retained. So the upgrade should not be the "major upgrade", but the "minior upgrade". The best way is to make one MSI to define which files are used to upgrade, which files are not for upgrade. Could you give me some idea how to realize it? Regards, Chunyan -----Ursprüngliche Nachricht----- Von: Blair [mailto:[hidden email]] Gesendet: Mittwoch, 11. November 2009 18:46 An: 'General discussion for Windows Installer XML toolset.' Betreff: Re: [WiX-users] New Entry in Add/Remove Program when upgrade You can do this with one MSI (I don't see how two MSIs would do anything more than confuse the issue even more) but you have to know BEFORE you start running the MSI whether you will be upgrading or not. Since that decision depends on the user's chosen installation path, which is gathered in the UI, that decision has to be made via UI BEFORE the MSI starts to run. In other words, drop Windows Installer's UI, and put the UI into your bootstrapping exe. Your bootstrapper will know your UpgradeCode and will do the same product enumeration that the Upgrade table enables, and will check the installation paths of the installed versions the same as your custom action does, and will remove the old version(s) that match the installation paths either before or after (more efficient) it installs the upgrading version. -----Original Message----- From: Jiang, Chunyan (GE Healthcare) [mailto:[hidden email]] Sent: Wednesday, November 11, 2009 6:32 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] New Entry in Add/Remove Program when upgrade Hi, I would like to clarify my requirement again. I read thought the WiX Tutorial 4. And I hope I could develop one setup.msi, which could combine "Minior upgrades" and "New Install". In my scenario, if updage Version 3 to Version 1 in PathA, it should do the "Minor upgrades". It doesn't not change the ProductID. And it only changes the product version and some files, not totally remove all the last install. But if Version 3 installs to a new path, it can act as a new install. Is it possilbe to do this in one setup.msi? If it is not, I want to develop two msi, one is for new install, one is for update. And use an external executable to decide which msi is called. However, there are 90% content same in the NewInstall.msi and Update.msi. Is it possible to create a common part that these two msi can call it? Best regards, Chunyan -----Ursprüngliche Nachricht----- Von: Jiang, Chunyan (GE Healthcare) Gesendet: Mittwoch, 11. November 2009 11:24 An: General discussion for Windows Installer XML toolset. Betreff: Re: [WiX-users] New Entry in Add/Remove Program when upgrade Hi Blair, I would like to ask you if I want to realize my scenario, is it possible to write a custom action to realize removing Version 1? Here I set the main msi still as OnlyDetect="yes". But when select one install from the dialog (Version 1) to upgrade, do the removing verion 1 in the custom action. This custom action only does remove the selected version, don't do the Detect, therefore don't touch version 2. Is it possible? And how to realize it? Regards, Chunyan -----Ursprüngliche Nachricht----- Von: Jiang, Chunyan (GE Healthcare) Gesendet: Mittwoch, 11. November 2009 10:38 An: General discussion for Windows Installer XML toolset. Betreff: Re: [WiX-users] New Entry in Add/Remove Program when upgrade Hi Blair, Thank you for your explain. I still have some questions here. My requirement is to have multiple versions and also be able to upgrade some. In my last email, the Version 3 should be able to upgrade Version1. It means version 1 should be removed. And Version 2 is kept untouched. But now I set OnlyDetect="yes". When I install Version 3 to the path of Version 1, all these 3 versions stay in the system. And in the future, I want to show the installed software in the Listbox, and ask user to select which one to upgrade, there will be 3 items there, same as Add/Remove Program. It is confused. Version 2 has been upgraded (remove). It should not be shown there. Is it possible to realize my requirement? Best regards, Chunyan -----Ursprüngliche Nachricht----- Von: Blair [mailto:[hidden email]] Gesendet: Freitag, 6. November 2009 15:59 An: 'General discussion for Windows Installer XML toolset.' Betreff: Re: [WiX-users] New Entry in Add/Remove Program when upgrade You could try removing OnlyDetect="no" and adding a condition to the RemoveExistingProducts action. However, then version 3 in your scenario will remove both versions 1 and 2 (instead of just 1). Your requirement to leave multiple versions without forcing each to use a different path is the problem. It doesn't leave you with many options. -----Original Message----- From: Jiang, Chunyan (GE Healthcare) [mailto:[hidden email]] Sent: Friday, November 06, 2009 1:59 AM To: General discussion for Windows Installer XML toolset. Subject: [WiX-users] New Entry in Add/Remove Program when upgrade Hi wix-users, I developed one setup msi. And I want it to be upgradable. The requirement is: 1. Version 1 install to PathA. (New Install) 2. Version 2 install to PathB. (New Install) 3. Version 3 install to PathA. (Upgrade) The setup meets the requairment. However, when I perform the above actions, there are 3 items in Add/Remove Program list. Version 1 and Version 3 are in the same path. Actually there are 2 installs, since version 3 just upgrades version 2. I consider the reason is that I set <UpgradeVersion OnlyDetect="yes" Property="PREVIOUSFOUND" ... Here Onlydetect = "yes". I know if I set OnlyDetect="No", then upgrade will replace the older version. And there is no old version item in Add/Remove Program list. But if I set OnlyDetect="No", when I perform second step (install Version 2 to PathB(New Install)), the system will check last install (Version 1 in PathA), and remove the files in PathA. I don't what to break install 1. Is there one way to resolve my problem? Regards Chunyan ---------------------------------------------------------------------------- -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ WiX-users mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/wix-users ---------------------------------------------------------------------------- -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ WiX-users mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/wix-users ---------------------------------------------------------------------------- -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ WiX-users mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/wix-users ---------------------------------------------------------------------------- -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ WiX-users mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/wix-users ---------------------------------------------------------------------------- -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ WiX-users mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/wix-users ---------------------------------------------------------------------------- -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ WiX-users mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/wix-users ---------------------------------------------------------------------------- -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ WiX-users mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/wix-users ---------------------------------------------------------------------------- -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ WiX-users mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/wix-users ---------------------------------------------------------------------------- -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ WiX-users mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/wix-users ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ WiX-users mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/wix-users |
||||||||||||||||
|
Blair-2
|
You have to know the number of instances you will support before-hand and
generate an instance transform for each instance you will ever have. I understood your requirement to have an open-ended number of "instances", each of a different build of your product. The multiple instance pattern allows them to all be the same build, just installed in different locations with (possibly) different feature (or even component) sets. -----Original Message----- From: Jiang, Chunyan (GE Healthcare) [mailto:[hidden email]] Sent: Tuesday, November 17, 2009 2:58 AM To: Blair; General discussion for Windows Installer XML toolset. Subject: AW: [WiX-users] New Entry in Add/Remove Program when upgrade Hi Blair, I found an article from MSDN, which is talking about multiple instance. I think my requirement is similiar like multiple instance, although the software version could be different. The link is here http://msdn.microsoft.com/en-us/library/aa369528(VS.85).aspx It says: The easiest way to initiate a maintenance installation, and reinstall an instance, is to reference the product code of the instance. If you initiate the maintenance installation by using the package path, you must also specify the product code of the instance. From the command line, use the /n {Product Code} option. From code or script, use the MSIINSTANCEGUID property. And example: The following example reinstalls an instance without re-caching the package. The instance is referred to by its product code {00000001-0002-0000-0000-624474736554}. msiexec /I {00000001-0002-0000-0000-624474736554} REINSTALL=ALL REINSTALLMODE=omus /qb Does it mean that retrieving the installed ProductID, then using command line to pass it the install package. Does it meet my requirement that update the user selected installed software by minor upgrade, but does not know the ProductID ahead? Regards, Chunyan -----Ursprüngliche Nachricht----- Von: Blair [mailto:[hidden email]] Gesendet: Freitag, 13. November 2009 18:24 An: Jiang, Chunyan (GE Healthcare); 'General discussion for Windows Installer XML toolset.' Betreff: RE: [WiX-users] New Entry in Add/Remove Program when upgrade As far as I know, no, it does not work. -----Original Message----- From: Jiang, Chunyan (GE Healthcare) [mailto:[hidden email]] Sent: Friday, November 13, 2009 2:46 AM To: General discussion for Windows Installer XML toolset. Cc: [hidden email] Subject: AW: [WiX-users] New Entry in Add/Remove Program when upgrade Hi Blair, I am sorry to confuse you on this issue. I think my requirement has been changed. I want to install multiple versions to different paths simultaneously. At the same time, there is requirement to update the specific installation. It must be minor upgrade, because there are some files should not be removed. So I think it is better to use two MSI to fulfill the task. And use bootstraper.exe to decide new install or upgrade. It makes things easy. However, I have a question for the minor upgrade MSI. Since there are mutliple versions installed, and user chooses which one to upgrade, the minor upgrade MSI doesn't know the Product ID. If I set a new Product ID to this minor upgrade MSI, is it possible to set it to another Product ID to this minor upgrade MSI when the installed version is selected by user? Does it work? value =::MsiSetPropertyW(hInstaller,L"ProductID",PreviousProduct); Best regards, Chunyan -----Ursprüngliche Nachricht----- Von: Blair [mailto:[hidden email]] Gesendet: Donnerstag, 12. November 2009 18:26 An: 'General discussion for Windows Installer XML toolset.' Betreff: Re: [WiX-users] New Entry in Add/Remove Program when upgrade Only when you drop your requirement to install multiple versions to different paths simultaneously. -----Original Message----- From: Jiang, Chunyan (GE Healthcare) [mailto:[hidden email]] Sent: Thursday, November 12, 2009 2:40 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] New Entry in Add/Remove Program when upgrade Hi, Since my requirement is special, which includes both new install and update, I would like to design my package as this: * One MSI(installation package) to do the new install * One MSP (patchwork) to do the update * One MSM (merge module) to contain the common part of new install and update Both MSI and MSP refer to MSM for the common part. And there is no duplicate files in the whole installation CD. The Bootstraper.exe has UI and decides when to do new install (call MSI), when to do update (call MSP). Do you think it is a possible solution for my issue? Regards, Chunyan -----Ursprüngliche Nachricht----- Von: Jiang, Chunyan (GE Healthcare) Gesendet: Donnerstag, 12. November 2009 10:06 An: General discussion for Windows Installer XML toolset. Betreff: Re: [WiX-users] New Entry in Add/Remove Program when upgrade Hi Blair, Thanks a lot for your suggestion. Here I would like to summarize the workflow: Bootstraper.exe should do the following steps: * Do the UI, list all installed path, ask user to select one to upgrade * When one installation is selected, remove this installation (should not totally remove. There are some files must retain.) * Call MSI to install new version in this path MSI should do the following steps: * Upgrade the selected installation. (Minior upgrade, keep the Product ID, change the version number, keep some files, and remove all files) * Or do the new install as demand Here I have one question. In my requirement, the selected installation should not be removed totally. There are some files must be retained. So the upgrade should not be the "major upgrade", but the "minior upgrade". The best way is to make one MSI to define which files are used to upgrade, which files are not for upgrade. Could you give me some idea how to realize it? Regards, Chunyan -----Ursprüngliche Nachricht----- Von: Blair [mailto:[hidden email]] Gesendet: Mittwoch, 11. November 2009 18:46 An: 'General discussion for Windows Installer XML toolset.' Betreff: Re: [WiX-users] New Entry in Add/Remove Program when upgrade You can do this with one MSI (I don't see how two MSIs would do anything more than confuse the issue even more) but you have to know BEFORE you start running the MSI whether you will be upgrading or not. Since that decision depends on the user's chosen installation path, which is gathered in the UI, that decision has to be made via UI BEFORE the MSI starts to run. In other words, drop Windows Installer's UI, and put the UI into your bootstrapping exe. Your bootstrapper will know your UpgradeCode and will do the same product enumeration that the Upgrade table enables, and will check the installation paths of the installed versions the same as your custom action does, and will remove the old version(s) that match the installation paths either before or after (more efficient) it installs the upgrading version. -----Original Message----- From: Jiang, Chunyan (GE Healthcare) [mailto:[hidden email]] Sent: Wednesday, November 11, 2009 6:32 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] New Entry in Add/Remove Program when upgrade Hi, I would like to clarify my requirement again. I read thought the WiX Tutorial 4. And I hope I could develop one setup.msi, which could combine "Minior upgrades" and "New Install". In my scenario, if updage Version 3 to Version 1 in PathA, it should do the "Minor upgrades". It doesn't not change the ProductID. And it only changes the product version and some files, not totally remove all the last install. But if Version 3 installs to a new path, it can act as a new install. Is it possilbe to do this in one setup.msi? If it is not, I want to develop two msi, one is for new install, one is for update. And use an external executable to decide which msi is called. However, there are 90% content same in the NewInstall.msi and Update.msi. Is it possible to create a common part that these two msi can call it? Best regards, Chunyan -----Ursprüngliche Nachricht----- Von: Jiang, Chunyan (GE Healthcare) Gesendet: Mittwoch, 11. November 2009 11:24 An: General discussion for Windows Installer XML toolset. Betreff: Re: [WiX-users] New Entry in Add/Remove Program when upgrade Hi Blair, I would like to ask you if I want to realize my scenario, is it possible to write a custom action to realize removing Version 1? Here I set the main msi still as OnlyDetect="yes". But when select one install from the dialog (Version 1) to upgrade, do the removing verion 1 in the custom action. This custom action only does remove the selected version, don't do the Detect, therefore don't touch version 2. Is it possible? And how to realize it? Regards, Chunyan -----Ursprüngliche Nachricht----- Von: Jiang, Chunyan (GE Healthcare) Gesendet: Mittwoch, 11. November 2009 10:38 An: General discussion for Windows Installer XML toolset. Betreff: Re: [WiX-users] New Entry in Add/Remove Program when upgrade Hi Blair, Thank you for your explain. I still have some questions here. My requirement is to have multiple versions and also be able to upgrade some. In my last email, the Version 3 should be able to upgrade Version1. It means version 1 should be removed. And Version 2 is kept untouched. But now I set OnlyDetect="yes". When I install Version 3 to the path of Version 1, all these 3 versions stay in the system. And in the future, I want to show the installed software in the Listbox, and ask user to select which one to upgrade, there will be 3 items there, same as Add/Remove Program. It is confused. Version 2 has been upgraded (remove). It should not be shown there. Is it possible to realize my requirement? Best regards, Chunyan -----Ursprüngliche Nachricht----- Von: Blair [mailto:[hidden email]] Gesendet: Freitag, 6. November 2009 15:59 An: 'General discussion for Windows Installer XML toolset.' Betreff: Re: [WiX-users] New Entry in Add/Remove Program when upgrade You could try removing OnlyDetect="no" and adding a condition to the RemoveExistingProducts action. However, then version 3 in your scenario will remove both versions 1 and 2 (instead of just 1). Your requirement to leave multiple versions without forcing each to use a different path is the problem. It doesn't leave you with many options. -----Original Message----- From: Jiang, Chunyan (GE Healthcare) [mailto:[hidden email]] Sent: Friday, November 06, 2009 1:59 AM To: General discussion for Windows Installer XML toolset. Subject: [WiX-users] New Entry in Add/Remove Program when upgrade Hi wix-users, I developed one setup msi. And I want it to be upgradable. The requirement is: 1. Version 1 install to PathA. (New Install) 2. Version 2 install to PathB. (New Install) 3. Version 3 install to PathA. (Upgrade) The setup meets the requairment. However, when I perform the above actions, there are 3 items in Add/Remove Program list. Version 1 and Version 3 are in the same path. Actually there are 2 installs, since version 3 just upgrades version 2. I consider the reason is that I set <UpgradeVersion OnlyDetect="yes" Property="PREVIOUSFOUND" ... Here Onlydetect = "yes". I know if I set OnlyDetect="No", then upgrade will replace the older version. And there is no old version item in Add/Remove Program list. But if I set OnlyDetect="No", when I perform second step (install Version 2 to PathB(New Install)), the system will check last install (Version 1 in PathA), and remove the files in PathA. I don't what to break install 1. Is there one way to resolve my problem? Regards Chunyan ---------------------------------------------------------------------------- -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ WiX-users mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/wix-users ---------------------------------------------------------------------------- -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ WiX-users mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/wix-users ---------------------------------------------------------------------------- -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ WiX-users mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/wix-users ---------------------------------------------------------------------------- -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ WiX-users mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/wix-users ---------------------------------------------------------------------------- -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ WiX-users mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/wix-users ---------------------------------------------------------------------------- -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ WiX-users mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/wix-users ---------------------------------------------------------------------------- -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ WiX-users mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/wix-users ---------------------------------------------------------------------------- -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ WiX-users mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/wix-users ---------------------------------------------------------------------------- -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ WiX-users mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/wix-users ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ WiX-users mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/wix-users |
||||||||||||||||
| Free Embeddable Forum Powered by Nabble | Help |
