You can't launch another MSI from a Visual Studio custom action. That's
because you can't have two simultaneous MSI installs running at the point
where VS sequences its custom actions. OnAfterInstall is a bit of a
misnomer. It's not called after the install, it's actually called at the end
of the Install custom action, so it happens in pretty much the same place as
the Install custom action.
You can't do what you want to do with Visual Studio setup projects. What you
want to do is more easily handled by a launch program that looks for the
existing MSI file, launches it, then launches yours. VS setup projects just
don't offer IDE support of the things you're trying to do. If you're doing a
lot of this kind of thing, VS probably isn't what you should be using. There
are a bunch of tools here, some free, some not, but you seem to be
continually trying to do things that Windows Installer will do, but not VS
setup projects.
http://www.codeproject.com/dotnet/dotNetInstaller.asp
http://installsite.org/pages/en/msi/authoring.htm

Signature
Phil Wilson
[Microsoft MVP-Windows Installer]
Definitive Guide to Windows Installer
http://apress.com/book/bookDisplay.html?bID=280
> Hi,
>
[quoted text clipped - 27 lines]
>
> Anna