Here's a quick overview. My Installer is creating a temporary directory in order to run an EXE during setup. Here's the twist. The executable also depends on a .config file that has variables filled out during installation and then is set. All of this works just fine. However ...
When executing the installer, I can clearly see the files get dumped to:
%TEMP%\1\Assemble\Migrate.exe (more files here as well)
This seemed a bit strange to me that the Temp Directory somehow get a "1" sub-directory (see this topic: http://www.advancedinstaller.com/forums ... 502&p=5969). However, on another machine it creates a "2" directory. Not sure what determines that sub-directory name?
Eventually, the installer gets to the point of creating the Imported XML File for the deferred action to execute. However, at this point the Temp Directory switches and the actual configuration file gets created at:
%TEMP%\Assemble\Migrate.exe.config
Whenever my custom action attempts to execute the Migrate.exe file. Obviously, all hell breaks loose, because it doesn't have the appropriate configuration file.
Does anyone have any insight as to what I'm doing wrong? Why does Windows feel the need to create the "1" sub-directory?
Thanks in advanced for any help.
FOLLOW US
Get the latest news in Application Packaging