On Sun, Feb 13, 2011 at 5:48 PM, Rob Mensching <r...@robmensching.com> wrote: > The Installer class is an anti-pattern in setup. You shouldn't use it for > anything.
Could you expand on this? Speaking purely as an end-user, I will make the following observations: 1) Windows services should be able to be installed using -i as a command line switch (more and more developers seem to ignore this, but it doesn't make it right) 2) Putting code to register a service in multiple locations is a maintenance nightmare 3) The Installer class allows a fairly OK way to implement a -i switch, while at the same time being easily accessible from a custom action in the installer (search for a class with the RunInstaller(true) attribute would be an elegant solution) 4) Do not forget to set up the event log... (also neatly provided by the ServiceInstaller class) If an old-school network admin accidentally removes the service using 'sc delete', he'd welcome a way to quickly put it back without running an installer. (5 second fix vs however long it takes to run your installer -- which can be quite time consuming these days) -- 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
