This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- Revenera Community
- :
- InstallShield
- :
- InstallShield Forum
- :
- Install components based on installed version
Subscribe
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Jan 18, 2008
10:13 AM
Install components based on installed version
I am creating an update to an installation. The update will be version 1.4. Version 1.2 had a database update that I do not want to run again, but I also want the 1.4 update to be able to update any previous versions.
My database update is done within an Installscript custom action. How can I set a condition on the custom action to only fire if version 1.2 has not already been installed. And if that's not possible, is there a way to find out the installed version in the script?
I'm using a Basic MSI project.
Thanks.
My database update is done within an Installscript custom action. How can I set a condition on the custom action to only fire if version 1.2 has not already been installed. And if that's not possible, is there a way to find out the installed version in the script?
I'm using a Basic MSI project.
Thanks.
(1) Reply
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Jan 20, 2008
09:06 PM
Can you just write your database update to detect that it's already been run and not run again?
I.e. ( pseudo code, not real sql )
REM build 1.2 sql changes
if not exist new table
create new table
end if
REM build 1.4 sql changes
if not exist something else
do something else
end if
This is probably the easiest and most scaleable solution to support.
I.e. ( pseudo code, not real sql )
REM build 1.2 sql changes
if not exist new table
create new table
end if
REM build 1.4 sql changes
if not exist something else
do something else
end if
This is probably the easiest and most scaleable solution to support.