/bundles/itninjaweb/img/Breadcrumb_cap_w.png
Hi All,
I am crating msi's for the first time and my TL dot'n want to use any third party intall creating software. So i'm trying to create a nested msi using msidb tool in windows installer sdk.
It is adding child msi to parent msi, problem - it is not adding a entry in custom action table for nested installation. As a result when i invoke the parent msi, inturn it is not invoking the child msi.

Do any one know what is the problem in this.
Any help welcome.
0 Comments   [ - ] Hide Comments

Comments

Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
Answer this question or Comment on this question for clarity

Answers

0
- Nested MSIs are the spawn of the Devil. Do NOT do it if you can avoid it.
- If your employer is too cheap to spring for a proper authoring tool, there are some freeware tools which you can use. A Google search will turn some up.
- If you *must* do nested MSI and don't want to use or are disallowed from using 3rd-party tools, use Orca to add the child MSI to the Binary table. There are innumerable posts here about how to do that. Orca is part of a free download from Microsoft.
Answered 04/09/2008 by: VBScab
Red Belt

Please log in to comment
0
create 3 nested msi (i believe type 23)


Install:
ARPSYSTEMCOMPONENT=1 ALLUSERS=[ALLUSERS] TRANSFORMS=whatever.mst
NOT Installed
INSERT AFTER your "Reinstall" custom action

Reinstall:
ALLUSERS=[ALLUSERS] REINSTALL=ALL REINSTALLMODE=OMUS
REINSTALL="ALL"
INSERT AFTER CostFinalize


Remove:
ALLUSERS=[ALLUSERS] REMOVE=ALL
REMOVE="ALL" AND NOT UPGRADINGPRODUCTCODE
INSERT AFTER InstallValidate
Check Exit COde
Answered 04/10/2008 by: linstead
Blue Belt

Please log in to comment