Hi,
We’ve built a custom DLL for our WiX-powered installer because our product has a pretty complicated install sequence. Our custom DLL runs as a deferred custom action since it modifies system files, etc.. The problem we’re facing is that since our DLL does the heavy lifting of registering our files, it also knows when a reboot is required after the installation has completed. Since deferred custom actions cannot set properties that get picked up by e.g. <ScheduleReboot>, I’m a little puzzled as to how to communicate the reboot flag back to the installer. Does anyone have ideas or a recommended practice for doing something like this? Thanks, Soren ------------------------------------------------------------------------------ Start uncovering the many advantages of virtual appliances and start using them to simplify application deployment and accelerate your shift to cloud computing. http://p.sf.net/sfu/novell-sfdev2dev _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
