On Mon, Feb 14, 2011 at 3:08 PM, Christopher Painter <chr...@deploymentengineering.com> wrote: > Well, Evil Genius, you clearly no more about installs then myself and Rob > Mensching combined so knock yourself.
I am not sure where I said I know more about installers? I freely admit to being a n00b at implementing an installer. But does that mean I cannot have an opinion on how a service executable should appear on my systems? I've used Windows NT since 1993, so I have seen and used my share of services. In my current environment, I have a bunch of home-brewed services. This is a problem too -- we should have joined many of these together, but that is currently outside the scope of my assignment. The number of services is enough to be unwieldy to provide batch files for (as per your suggestion), but just the right amount that it sort of could work... I've seen my share of "sort of works" solutions before, and it does not assist maintainability. I did not like InstallUtil when I first encountered it (and still don't). And I do not like <ServiceInstall>. Mind you, adding a condition to ServiceInstall entries would be helpful. Or standardize a way to add service metainfo to the resource section of executables would be neat too (i.e. replace InstallUtil). -- Rune ------------------------------------------------------------------------------ The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: Pinpoint memory and threading errors before they happen. Find and fix more than 250 security defects in the development cycle. Locate bottlenecks in serial and parallel code that limit performance. http://p.sf.net/sfu/intel-dev2devfeb _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
