Gonzalo Diethelm wrote:
I guess that's arguable. I already had to provide all those details
(service name, startup information, etc.) in the EXE itself, in order
to support the /install, /remove, /start and /stop switches. Why would
I want to repeat that in the installer, instead of just calling the EXE?
Because the .exe doesn't provide the functionality you get "for free"
from MSI when you duplicate the data in the .msi package. Do you handle
install, uninstall, repair, modify, upgrades, and patching? It's
possible, of course, but at a cost far higher than duplicating the data.
And if data duplication is your biggest concern, you can single-source
it by preprocessing the data, either into a header in your code or an
include file in your WiX authoring (one of the advantages of XML).
--
sig://boB
http://joyofsetup.com/
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
