|
Hi Bob, Thanks for the
reply. We have already found out what caused this. U said “MSI
doesn't set INSTALLDIR; it's entirely up to your package what the directory
structure looks like. MSI records where it installs components”. U r completely
right, but as per our experiment installer can resolve the directory paths from
the path where is installs components. As there was no
direct component that was getting installed under the directory “INSTALLDIR”
(all the components were present through intermediate directories) installer
was unable to set the property “INSTALLDIR”. We confirmed this
because just after adding a component beneath “INSTALLDIR”,
installer started calculating “INSTALLDIR” properly. So the paths of the
directories are resolved from the path of components just under it. This was the
info I was looking for. Bob, Can you please
confirm whether I am right or not? Thanks for all your
helps and suggestions so far. Take
Care Anirban
From: But this is a windows
installer variable (supposed to set by the windows installer service itself)
and it should be safe to use it. MSI doesn't set INSTALLDIR; it's entirely up to your
package what the directory structure looks like. MSI records where it installs
components but doesn't persists property changes your package makes. If you
need that data, you need to persist it (e.g., in the registry) and load it
(using RegistrySearch). -- sig://boBhttp://bobs.org |
------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
