Help understanding installer capabilities

[gjones]

I have downloaded WinINSTALL LE and have read Windows 2000
step by step guide
to creating windows installer packages. I work for a
company that wants to
simplify the deployment of software created in house.
Currently the
application which uses IIS, requires that we manually stop
the website,
unload the dll's stop component services, remove
components being replaced,
copy in the new DLL's re-register new dll's and restart
the web site. What
I've been trying to determine is how much of this is
handled natively in the
Windows 2000 installer and how much of it is scripted in
separately to the
MSI file?
I suspect that the installer handles all the unregister/re-
register
automatically based on the MSI created by WinINSTALL LE.
What I'm not sure
about is the stopping of component services and stopping
of the website (we
don't want to stop IIS just the web site) If anyone could
refer me to a good
reference source for this subject I would be grateful.
..

 

[Phil Wilson]

This is a really useful site, lots of info and comparisons of authoring
tools.
http://www.installsite.org/
There are lots of tools that can build MSI files, so it all comes down to
how much support you want in the tool IDEs for what you want to do. I think
that stopping a particular web site would need a custom action, and this
link should get you started:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dniis/html/autoadm.asp