Why?
This is a ready-only archive of the InstallSite Forum. You cannot post any new content here. / Dies ist ein Archiv des InstallSite Forums. Hier können keine neuen Beiträge veröffentlicht werden.
Installing MSI package from DLL-custom action
Started by
Generous
, Feb 09 2001 10:30
7 replies to this topic
Generous
-
- Members
- 53 posts
Posted 09 February 2001 - 10:30
I try install MS Access 2000 Runtime from custom action (DLL,VC++,MsiInstallProduct() function) in InstallExecute sequence, but when i run my installation, Access Runtime setup terminated with error "Another installation is already in progress. Complete that installation before proceeding with this install."
Stefan Krueger
-
- Administrators
- 13,269 posts
InstallSite.org
Posted 09 February 2001 - 13:22
Try to call the other MSI as nested install custom action. See "nested install" in MSi Help.
Generous
-
- Members
- 53 posts
Posted 12 February 2001 - 11:11
Thanks!
OK. I create nested installation action and Access2000 RT has been installed.
OK. I create nested installation action and Access2000 RT has been installed.
But when I try remove Access 2000 RT from add/remove program panel, it not removed with error "...cannot found source..."
Why?
Generous
-
- Members
- 53 posts
Posted 19 February 2001 - 13:43
And one more problem:
On NT4.0 when i uninstall my application MSA also removed from system.
On Win2000 MSA not removed, but when I try uninstall them I get error "cannot find source"
On NT4.0 when i uninstall my application MSA also removed from system.
On Win2000 MSA not removed, but when I try uninstall them I get error "cannot find source"
sarfu
-
- Full Members
- 44 posts
Posted 12 October 2006 - 12:30
stefan i have doubt
can we use nested installtion to uninstall standard installer which is previsously installed by including nested installtions in basic msi
can we use nested installtion to uninstall standard installer which is previsously installed by including nested installtions in basic msi
Glytzhkof
-
- Moderators
- 1,447 posts
Posted 12 October 2006 - 12:52
Nested installation actions are deprecated - they never worked. They have more issues than you can count.
Note: It is illegal on windows for two different InstallExecuteSequences to run simultaneously. This is why doing MSI installs / uninstalls via custom actions will fail. The solution is to use MSI's major upgrade feature OR, do the install / uninstall actions from the InstallUISequence.
Note: It is illegal on windows for two different InstallExecuteSequences to run simultaneously. This is why doing MSI installs / uninstalls via custom actions will fail. The solution is to use MSI's major upgrade feature OR, do the install / uninstall actions from the InstallUISequence.
Regards
-Stein Åsmul
-Stein Åsmul
Glytzhkof
-
- Moderators
- 1,447 posts
Posted 12 October 2006 - 12:53
A third, and perhaps better option, is to run installs from some sort of batch file or bootsrapper setup.exe. Then the setups can be run in sequence, i.e one after the other. This is more reliable for situations when your setup might be run in silent mode (since actions only located in the UI wouldn't be run in these cases).
Regards
-Stein Åsmul
-Stein Åsmul
Gareth at Serif
-
- Full Members
- 85 posts
Posted 18 October 2006 - 14:57
You can also run MSI installations as deferred actions. So long as you ignore the return code your install will launch theirs and end itself while the second one does it's thing. So long as your install doesn't call a reboot, you're laughing - especially if theirs is silent and the user has no idea it's happening seperate to your own install.
The only drawback I've found with this method is when you require two other MSI packages to be installed with your own.
The only drawback I've found with this method is when you require two other MSI packages to be installed with your own.