That's a strange topic, huh?
We have two possible installs happening - one on a "server" and one on a "client." The "client" installer will be packaged inside the "server" one and will be callable from whatever network share the "server" software is installed to.
Both packages require the same DLLs, although the "client" is only a subset of the ones installed by the "server" install.
Both packages also require the same chained MSI, a 17-meg monster which I would dearly love to avoid packaging twice. It's the Crystal reports runtime for VS 2008 - call it CR.MSI.
I have the chained install working just fine for the "Server" install, but of course this doesn't include putting the actual .MSI file into the appdir for reference by the "Client" install. If I could get it there, then the "Client" install could probably reference it using the SOURCEDIR or SETUPEXEDIR workaround described in the knowledgebase.
But adding CR.MSI as an actual file in the "server" installer (in addition to doing the chained install) also includes it twice. And of course, adding it to the "Client" installer would include it twice.
I have tried including it as a file in the "Server" and then doing a custom EXE action to run "msiexec.exe [#CR.MSI] /i /qb" - but I just get the MSIEXEC.exe help screen and it does not install. (running that same command from a cmd window works fine, btw.) So manually invoking the included installer file does not seem to work.
Is there a way to have an included .MSI file behave as though it were chained, and still be able to be referenced by another installer that's been put into the Appdir next to it? Or - can a chained .MSI file somehow be forced to be copied to the appdir for the same purpose?
I hope that was clear.
Thanks,
Rob
FOLLOW US
Get the latest news in Application Packaging