Personally, I think that is not good advice. In all the time I've spent writing CustomActions the only robust solution is to have a simple native DLL with as few dependencies as possible. Exe CustomActions can't provide progress or data back to the install. The Installer class is just another form of SelfReg and has all the same problems.
I know that I sound like a broken record on this topic but writing CustomActions is a very difficult thing to do properly for all cases and not an task that should be undertaken lightly. Invariably, cutting corners to save you (the developer) time ends up creating grief for the customer. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Cullen Waters Sent: Wednesday, October 11, 2006 3:13 PM To: John Vottero; david adams; wix-users@lists.sourceforge.net Subject: Re: [WiX-users] WiX XML Issue Two ways. One is to create a console application, and use wix's custom tag to call it during execution, passing flags as necessary. Two is to inherit from the Installer class. I'm not sure how you get that code hooked up using Wix, though. Sorry I can't be more help here. ------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
