Hello everyone,
I am in the midst of porting an InstallShield InstallScript for MSI project to WiX and I've run into a little trouble. I'm new to WiX and not terribly knowledgeable about Windows Installer, so please forgive me if I'm asking a question for which the answer seems obvious. In my effort to port one of our merge modules to a WiX library, I need to install the content of the WiX library to a custom location - but not the same location as the main product project. I have followed the example on page 125 of Nick Ramirez's book on WiX, in which a type 51 custom action is used to set the AppDataDir property before the "InstallFiles" sequence in the InstallExecuteSequence. The files install to the dynamic location, but - unfortunately - it appears that these components do not remember where they were installed and removing the entire product results in the WiX library contributed files to remain when installed to a non-default location. Is the problem merely that the type 51 custom action should be called earlier in the install execute sequence? For example, should it be set immediately after the AppSearch sequence? Best regards, Sean ------------------------------------------------------------------------------ All of the data generated in your IT infrastructure is seriously valuable. Why? It contains a definitive record of application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-d2d-c2 _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
