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?
Thanks and best regards.
On Tue, 2007-10-02 at 08:38 -0700, Bob Arnson wrote:
> Gonzalo Diethelm wrote:
>
> > The only reason not to use ServiceInstall and ServiceControl is the
> > DRY principle (Don't Repeat Yourself).Since I MUST provide a way for
> > users to start/stop/install/delete the service from the console, I
> > don't want to replicate that mechanism anywhere else, hence the very
> > simple actions in a DLL that invoke these operations.
>
>
> Both DRY and Occam's Razor include the term "unnecessarily." Correctly
> handling service installation isn't "simple," so this is a case where
> repeating the information has value.
>
>
> --
> sig://boB
> http://joyofsetup.com/
--
Gonzalo Diethelm
[EMAIL PROTECTED]
-------------------------------------------------------------------------
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
