I had a cunning plan. I wanted to install everything - just in case. As a convenience for the victim (uhm, "customer") I wanted to add a feature that would install a service.
If the user misses that feature, he can simply find the executable and register the service using -i as a command line parameter. But <ServiceInstall> of course looks at KeyPath. The easiest way would be to include the executable using <file>, but then how do I manage to let the user keep the file around "just in case"? I have about five services like this. They are not necessarily supposed to be switched on right away. -- Rune ------------------------------------------------------------------------------ Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)! Finally, a world-class log management solution at an even better price-free! Download using promo code Free_Logger_4_Dev2Dev. Offer expires February 28th, so secure your free ArcSight Logger TODAY! http://p.sf.net/sfu/arcsight-sfd2d _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
