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
- :
- Component Installed State during Major Upgrade
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
Sep 27, 2010
09:08 AM
Component Installed State during Major Upgrade
Hi All,
I've noticed an issue regarding component "installed state" during a major upgrade. When I am installing the newer version of my MSI I am seeing the following entries regarding component state detection:
MSI (s) (EC:0C) [09:35:52:368]: Component: Test; Installed: Absent; Request: Local; Action: Local
I would expect to see something more like "Installed: Local; Request: Local; Action: Null" since the component is already installed.
I am getting this same result even when the file in my component is the same version.
To make sure there was nothing strange with my MSI I even created a new "basic MSI" project that only contains this one "Test" component and then I set it up to handle the major upgrade.
I don't know if this is important, but we are using RemoveExistingProducts after InstallFinalize so if anything fails during the attempted installation of the new version we can still roll back to the older version.
I've noticed an issue regarding component "installed state" during a major upgrade. When I am installing the newer version of my MSI I am seeing the following entries regarding component state detection:
MSI (s) (EC:0C) [09:35:52:368]: Component: Test; Installed: Absent; Request: Local; Action: Local
I would expect to see something more like "Installed: Local; Request: Local; Action: Null" since the component is already installed.
I am getting this same result even when the file in my component is the same version.
To make sure there was nothing strange with my MSI I even created a new "basic MSI" project that only contains this one "Test" component and then I set it up to handle the major upgrade.
I don't know if this is important, but we are using RemoveExistingProducts after InstallFinalize so if anything fails during the attempted installation of the new version we can still roll back to the older version.
(1) Reply
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Oct 11, 2010
12:45 PM
If REP was before InstallInitialize you'd see two installValidate actions, one from the removal, and one from the new installation.
What you're seeing is quite literal. it is currently "Installed", you want to install it (Request: local), and the installation is still going to process the component for installation (Action: Local) so it can fix or replace reg entries/files.
What you're seeing is quite literal. it is currently "Installed", you want to install it (Request: local), and the installation is still going to process the component for installation (Action: Local) so it can fix or replace reg entries/files.