rprussell
Posts: 38
Joined: Tue Feb 24, 2009 5:34 pm

Need a single file referencable by a nested installer...

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
Cosmin
Posts: 5797
Joined: Tue Jul 10, 2007 6:39 pm
Contact: Website

Re: Need a single file referencable by a nested installer...

Hi Rob,

Unfortunately what you need cannot be done by using a chained installation. However, you can try adding the CR.MSI package into the "Files and Folders" page of the server install. To run it you can use a Launch file or open URL custom action scheduled under "InstallExecuteSequence" -> "InstallFinalize". It should use the option Asynchronous execution, do not wait for return to make sure that it's launched in another process.

Regards,
Cosmin
Cosmin Pirvu - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube
rprussell
Posts: 38
Joined: Tue Feb 24, 2009 5:34 pm

Re: Need a single file referencable by a nested installer...

Hi, Cosmin -

I've revamped things.

The "Server" install will now call the "Client" install as you suggested doing with CR.MSI. The "Client" install will simply chain CR.MSI since it needs to be installed in all cases.

The main problem with that approach (I tried it) is that the FINAL final step of my "Server" installation can't occur until the spawned "Client" MSI is done - so I am forced to wait for it to return.

And so initially, I tried setting it up as "Synchronous, Check return code," and got the (maybe predictable) "another program is being installed" message from Windows Installer.

After that failed, I did set it up as Async/ignore, and got the same message - only this time the FINAL final step went barging ahead and (definitely predictably) failed.

Thoughts?

Rob
Cosmin
Posts: 5797
Joined: Tue Jul 10, 2007 6:39 pm
Contact: Website

Re: Need a single file referencable by a nested installer...

Hi Rob,
The main problem with that approach (I tried it) is that the FINAL final step of my "Server" installation can't occur until the spawned "Client" MSI is done - so I am forced to wait for it to return.
Unfortunately Windows Installer cannot run multiple installs at the same time. However, you can try launching the client installer after "InstallUISequence" -> "ExecuteAction". This way the client installation should start right after the main one.

Doesn't the Crystal reports runtime have a merge module? If it has, you can include it in the client install and the client could be chained with the server install.

Regards,
Cosmin
Cosmin Pirvu - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube

Return to “Common Problems”