Nick Meredith wrote:
Then we reaised that we actually needed to control the install location at a higher level in the tree (COMBINEDPRODUCTFOLDER -- see code extract below) so that we could fix the structure of directories below this level. We changed the ConfigurableDirectory on the Feature to the new directory and changed the UI to set this value instead. The installer still runs through okay and defaults the directory for the user at the right level, then goes ahead and installs.The problem is that the files are still created under the default C:\Program Files\... location regardless of what the user enters in the UI. Can anyone explain what I'm doing wrong -- I'm sure you should be able to do this?
That should work fine. You don't need to specify the ConfigurableDirectory attribute on the feature, however; that's used to allow each feature to have its directory specified. I don't see how it would matter, but try omitting that attribute from you feature to see if it helps. Otherwise, standard MSI recommendation applies: Get a verbose log and search for every mention of COMBINEDPRODUCTFOLDER to see that it gets the defaults, then gets the user-supplied directory, then gets passed from the UI to the execute sequence.
-- sig://boB http://joyofsetup.com/
------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/
_______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
