I'm creating a setup and deployment application that will ultimately
install some prerequisites, a windows application, and then transfer a
file to a handheld device. The setup process works fine up to the
point where it attempts to transfer the file to the handheld. The
deployment project uses the Windows boostrapper to handle the prereqs
and kick off the installation. Unfortunately, because of the
bootstrapper.. the application path points to the system32 directory,
where the process is actually running. Is there a way to somehow get
the path where the "Setup.exe" file was actually executed from? This
is an awkward and confusing issue, so please let me know if I need to
reword my question or provide more information.
install some prerequisites, a windows application, and then transfer a
file to a handheld device. The setup process works fine up to the
point where it attempts to transfer the file to the handheld. The
deployment project uses the Windows boostrapper to handle the prereqs
and kick off the installation. Unfortunately, because of the
bootstrapper.. the application path points to the system32 directory,
where the process is actually running. Is there a way to somehow get
the path where the "Setup.exe" file was actually executed from? This
is an awkward and confusing issue, so please let me know if I need to
reword my question or provide more information.