Our installer was written using InstallShield and we're moving to Wix. Our old installer does some things I'm not sure how to duplicate in WiX.
The application files sit alongside the installer on a network drive, and the application can be installed one of two ways via a command line switch: 1) "network install" where the application files remain on the network drive, but are registered on the local machine. 2) "local install" where the application files are copied from that same network drive down to the local machine, then registered. Some things are common to both installs like an ODBC DSN and some registry entries. First question: For the "network install" I plan on using type 34 custom actions to register the dll's and self-register the exe's, then unregister on uninstall. Basically the files themselves would be ignored as far as WiX was concerned. Is that the right approach, or can this be done without custom actions? Second question: For the "local install", I need to copy the application files down to the client machine, then remove them on uninstall. How do I reference the application files in the WiX code, but *not* bundle them inside the MSI? I would rather avoid custom actions if possible. ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
