Re: [WiX-users] Scheduling Install and Uninstall Custom Actions

2012-06-08 Thread Wilson, Phil
June 07, 2012 8:06 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Scheduling Install and Uninstall Custom Actions Well Phil, I got the idea but I am not sure on which component I use this condition. For basic msi I saw that it used component id of DLL whic

Re: [WiX-users] Scheduling Install and Uninstall Custom Actions

2012-06-07 Thread Ravi Raj
at feature is uninstalled. > > Phil W > > -Original Message- > From: Ravi Raj [mailto:raviraj.callin...@gmail.com] > Sent: Thursday, June 07, 2012 1:33 AM > To: General discussion for Windows Installer XML toolset. > Subject: Re: [WiX-users] Scheduling Install and Uninsta

Re: [WiX-users] Scheduling Install and Uninstall Custom Actions

2012-06-07 Thread Wilson, Phil
WiX-users] Scheduling Install and Uninstall Custom Actions I found a way by opening (via orca) my previous installer (made by Visual Studio 2010 basic msi). All the custom actions are using component conditions. I am not at all comfortable in this. So I am modified my current installer with follo

Re: [WiX-users] Scheduling Install and Uninstall Custom Actions

2012-06-07 Thread Ravi Raj
I found a way by opening (via orca) my previous installer (made by Visual Studio 2010 basic msi). All the custom actions are using component conditions. I am not at all comfortable in this. So I am modified my current installer with following CAs. Its working great. NOT Installed NOT Instal

Re: [WiX-users] Scheduling Install and Uninstall Custom Actions

2012-06-07 Thread Rob Hamflett
Are these actions specified as being deferred, so they actually run as part of the installation script? Rob On 05/06/2012 13:52, Ravi Raj wrote: > I want to schedule my custom actions in following manner: > 1) Install: CA will run *only after* the installer copies all files to the > respective d

Re: [WiX-users] Scheduling Install and Uninstall Custom Actions

2012-06-06 Thread Rob Mensching
If you are modifying machine state, a better way is to make your custom action data driven and use Component States to determine when to do work. You can see that the custom actions in the WiX toolset behave this way. Lots of the code lives under src\ext and src\ca On Tue, Jun 5, 2012 at 5:52 AM,

[WiX-users] Scheduling Install and Uninstall Custom Actions

2012-06-05 Thread Ravi Raj
I want to schedule my custom actions in following manner: 1) Install: CA will run *only after* the installer copies all files to the respective directories. 2) Uninstall: custom action has completed successfully and then installer removes the files from the system. How should I write my custom act