M
MovnOn
I've created an installation package for my program.
Before installation, I use the User Interface to get
values that are added to the registry. One of the values
that the user must add is a path to a required input file
for the program. I'm finding that if the user enters a
path which contains a space (example: c:\Program
Files\myProgram\file.txt) that the install will return a
file not found error and abort the install.
I don't understand why the install is even checking that
the file exists, since I'm overriding install with my own
code and I didn't include any code to check that the file
exists. It's not important that the file exist when the
program is installed, only that it exists at runtime
(program will abort if it doesn't exist).
Why does the install check the path and how do I make sure
that it doesn't do that?
Before installation, I use the User Interface to get
values that are added to the registry. One of the values
that the user must add is a path to a required input file
for the program. I'm finding that if the user enters a
path which contains a space (example: c:\Program
Files\myProgram\file.txt) that the install will return a
file not found error and abort the install.
I don't understand why the install is even checking that
the file exists, since I'm overriding install with my own
code and I didn't include any code to check that the file
exists. It's not important that the file exist when the
program is installed, only that it exists at runtime
(program will abort if it doesn't exist).
Why does the install check the path and how do I make sure
that it doesn't do that?