Install Apache HTTPd during Setup

[leedo2k]

Hello,



I intend to write a program that interacts with a webserver. I first thought of using any 3rd party webserver but resorted to using Apache HTTPd. My question is how is it possible to force my solution setup project to install Apache HTTPd silently during setup?

Any other topic relevant opinions are welcome.

Thanks

[weirddemon]

This question is probably more suited for the deployment forum.

Your question doesn't have enough information for us to answer. What type of installer does the Apache HTTPd package come in? What installer are you using for deployment?

[MartinLiss]

Moved.

[leedo2k]

Sorry for posting at the wrong forum. Well, my application is written in C# using VS 2005. It is a Windows application that requires a webserver to post HTML content to for other end users to share and use. Speaking of web servers I already tested IIS and had some issues so I chose to use Apache web server.

My solution has a setup project to install it on end users machines. My question is how is it possible to have my application setup fire off Apache MSI installer. Knowing that it is known that Windows Installer doesn't allow simultaneous installations to take place of course.

Thanks
Leedo

[dilettante]

You just use a "wrapper" to invoke you installs sequentially. Here's a crude and rude example (WSH script and the guy didn't bother to test result values before proceeding):

Running chained MSI installations (http://blogs.msdn.com/b/willbu/archive/2006/12/05/running-chained-msi-installations.aspx)

Write a small EXE to do this, test the results from each install as needed, embed an elevation manifest. Wrap it all in some sort of self-extracting archive, like those produced by IExpress. IExpress comes in Windows starting with WinXP.

[leedo2k]

Thanks... I guess writing my own EXE to call them in sequence is the best option.
One more important thing here though. Assuming the target computer is a clean one without "Windows Installer" installed on it, I will have to force Windows Installer to be the first MSI to run.

Thanks

[dilettante]

Well I can't imagine what OS is going to (a.) support the .Net Framework and (b.) not have Windows Installer out of the box. Or were you really trying to deploy to 98/Me???

But a clean install package for Installer doesn't come packaged as an MSI, you'd have a chicken and egg problem.

In any case prior to .Net what we do is outlined in HOWTO: Install Windows Installer with Visual Studio Installer Packages (http://support.microsoft.com/kb/283168). Something similar should apply when you use a version of Visual Studio after 6.0 too.

[leedo2k]

Oh yes you are absolutely right.

Thanks