/build/static/layout/Breadcrumb_cap_w.png

Moving action sequences in InstallExecuteSequence table

I have done some tests moving the WriteRegistryValues sequence to after the PublishProduct sequence so that some registry entries I have added to the Registry table get added. I have to do this as PublishProduct deletes them even when I use a transform file to add them.

The product in question is Office 2003 and after the manual changes the product installed, ran and uninstalled without incident. I would just like to know if there may be any other problems that may occur by doing the above?.

thanks.

0 Comments   [ + ] Show comments

Answers (5)

Posted by: aogilmor 15 years ago
9th Degree Black Belt
0
according to msi.chm it should be OK:
WriteRegistryValues Action
The WriteRegistryValues action sets up an application's registry information. The registry information is gated by the Component table. A registry value is written to the registry if the corresponding component has been set to be installed either locally or as run from source. For more information, see Registry table.
Sequence Restrictions

The InstallValidate action must come before the WriteRegistryValues action. If there is a RemoveRegistryValues action, then it must come before the WriteRegistryValues action.

PublishProduct Action
The PublishProduct action manages the advertisement of the product information with the system. This action publishes the product if the product is in advertise mode or if any feature is being installed or reinstalled.
Sequence Restrictions

The PublishProduct action must come after the PublishFeatures action.
Posted by: benners 15 years ago
Senior Yellow Belt
0
aogilmor

Thanks for the reply aogilmor, I have been doing some more tests and from what I can see the, if I move the sequences as described in my first post it is OK when I install one application. If I install another application the Modify\Repair dialog pops up for the first application, it seems to think the second app is the first app so some values must get overwrote :-(

I can't see any way around that so I may have to move on to some of my other options.
1. Create a custom action and call a reg file with the entries in it.But this causes problems when the install runs from the MSOCACHE folder.
2. Create a table with my registry entries and try to emulate how the msi calls the Registry table. Is this possible?.

Thanks for your help
Posted by: aogilmor 15 years ago
9th Degree Black Belt
0
ORIGINAL: benners

aogilmor

Thanks for the reply aogilmor, I have been doing some more tests and from what I can see the, if I move the sequences as described in my first post it is OK when I install one application. If I install another application the Modify\Repair dialog pops up for the first application, it seems to think the second app is the first app so some values must get overwrote :-(

do you mean another Office app? If so, you need to realize that the apps (Excel, Word, etc.) are actually features within the Office product. To install them individually you need to use the ADDLOCAL=Feature syntax.

I would not recommend adding a custom table or running a reg file manually.
Posted by: benners 15 years ago
Senior Yellow Belt
0
Sorry for the confusion, here is what I did.
1. Installed OneNote, it installed OK and ran OK
2. Tried to install Project but the Modify\Repair dialog came up for Onenote.

Something in the registry table must have overwrote what the PublishProduct action did.
Posted by: aogilmor 15 years ago
9th Degree Black Belt
0
ORIGINAL: benners

Sorry for the confusion, here is what I did.
1. Installed OneNote, it installed OK and ran OK
2. Tried to install Project but the Modify\Repair dialog came up for Onenote.

Something in the registry table must have overwrote what the PublishProduct action did.



If you're going to install another office product when office is already installed (Project and OneNote are both Office products) you need to use the ADDLOCAL syntax.
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ