Re: [WiX-users] Deferred vs Immediate custom action

2010-12-28 Thread Rob Mensching
special in the > ca itself. > Cheers > Sean. > > -Original Message- > From: Rob Mensching [mailto:r...@robmensching.com] > Sent: 28 December 2010 16:31 > To: General discussion for Windows Installer XML toolset. > Subject: Re: [WiX-users] Deferred vs Immediate cus

Re: [WiX-users] Deferred vs Immediate custom action

2010-12-28 Thread Sean Farrow
: Rob Mensching [mailto:r...@robmensching.com] Sent: 28 December 2010 16:31 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Deferred vs Immediate custom action Certainly sounds like you are modifying machine state. If the user clicks cancel after the custom a

Re: [WiX-users] Deferred vs Immediate custom action

2010-12-28 Thread Rob Mensching
Certainly sounds like you are modifying machine state. If the user clicks cancel after the custom action runs, should the files be removed (probably "Yes" unless they are temp files in the temp folder)? If so, then you must be deferred and you need a rollback custom action. Which custom action in

[WiX-users] Deferred vs Immediate custom action

2010-12-28 Thread Sean Farrow
Hi: I'm currently using the QuietExec custom action to run a command line tool which itself creates extra files. Given that this creates files is this considered changing the state of the system? If so should I run this as a Deferred action? Or can I get away with an immediate action? Also does