2 replies to this topic

[kris]

SourceDir gives you the path to where the .msi exists....is there any Property, such as SourceDir, which I can use to find the path of the setup.exe?  (I compress all my setup files into setup.exe instead of .msi)  When I try to do a SourceDir, I get the .msi path, when what I really want is the setup.exe path???  (I would do a FindFile to solve the problem, but if I do a FindFile I need to search a specific disk, and if the user is running setup.exe off a cd, then I will not be able to search for the cd-rom drive letter, because there is no Property set to the cd-rom drive letter)

[Ian Blake]

This problem is intractable.  If setup does not tell the msi engine where it is, how can msi possibly know.  There is no reason why setup would tell msi.

I assume you have some files external to the installation that you are trying to get to.  Your solution is to write a custom setup.exe.  This is a non trivial task.

[Murali]

The self extracting Setup.exe, when started, extracts all the files in the package on to the temp directory (which lies within Documents And Settings\user\Local Settings\Temp. When SourceDir is used then it gives this Directory instead of where the Setup.exe lies. The only way to identify where the Setup.exe lies is to build the Setup.exe in uncompressed mode.

Thanks Stefan for this information.