Hi,
I have a need to allow end users to install over an existing installation without having to first uninstall. Before I hack up the install scripts I thought I would check if there was an easier way to do this.
Thanks
Install over an existing installation
-
Alex_Ronquillo
- Site Admin
- Posts: 364
- Joined: Mon Jul 30, 2007 11:51 am
- Location: USA
- Contact:
-
Alex_Ronquillo
- Site Admin
- Posts: 364
- Joined: Mon Jul 30, 2007 11:51 am
- Location: USA
- Contact:
I would surgest you let it deinstall still you could make systems very messy otherwise.
But you can move the step into your install phase of the setup so it's transparent to the user.
Look for the IF statement that checks NEEDSUPGRADE in the prerequisites section of your msi code and move it before the apply install command.
Not tried this my self yet but I don't think there would be a problem, am sure someone will soon say
I belive this is how other installers handle it install aware is just telling you about it
But you can move the step into your install phase of the setup so it's transparent to the user.
Look for the IF statement that checks NEEDSUPGRADE in the prerequisites section of your msi code and move it before the apply install command.
Not tried this my self yet but I don't think there would be a problem, am sure someone will soon say
-
Bob T Bunny
- Posts: 30
- Joined: Wed Jul 04, 2007 9:21 pm
Firstly, apologies for the long post.
I have spent about 6 hours today trying to do the same thing (see my post about companion files, any suggestions appreciated!). We want our users to only click once at the beginning, and once at the end. Having to click Next to uninstall the previous version on 20 different computers during an installation is painful, to say the least.
This morning (New Zealand time) I moved the section MLS mentioned to the Apply Install command (actually I think I moved the whole Compile If build not patch section, or something like that), and it worked very nicely.
I did try a few different ways of installing without uninstalling first, and it didn't go well. None of my non-versioned files got installed, even though they meet the file comparison requirements. I'd suggest following the "normal" way of doing it, and let it uninstall.
My only concern is if the install fails for some reason (coming across a corrupt file part way through and falls over, for example). Because the uninstall has happened successfully, the partial installation will roll back, and the computer will be left with no version installed at all!
I have spent about 6 hours today trying to do the same thing (see my post about companion files, any suggestions appreciated!). We want our users to only click once at the beginning, and once at the end. Having to click Next to uninstall the previous version on 20 different computers during an installation is painful, to say the least.
This morning (New Zealand time) I moved the section MLS mentioned to the Apply Install command (actually I think I moved the whole Compile If build not patch section, or something like that), and it worked very nicely.
I did try a few different ways of installing without uninstalling first, and it didn't go well. None of my non-versioned files got installed, even though they meet the file comparison requirements. I'd suggest following the "normal" way of doing it, and let it uninstall.
My only concern is if the install fails for some reason (coming across a corrupt file part way through and falls over, for example). Because the uninstall has happened successfully, the partial installation will roll back, and the computer will be left with no version installed at all!

