R
Richard Kucia
I'm modifying the CabWiz .inf file so that some data files are installed in
a folder beneath the application's folder. If the PDA user removes the
application, these files and their folder are also removed. This is the
behavior I expected, and it works fine.
Is there a trick I can use so that CabWiz creates an EMPTY folder beneath
the application's folder?
Here's the reason: When the application starts up, it always creates a few
folders (e.g. "Exports") beneath the application folder if those folders do
not already exist. It's possible that a user might never use the exporting
feature, and thus the application never creates any new files in the
"Exports" folder.
If the user chooses to remove the application, then these folders should
also be removed. However (if I understand "Add/Remove Programs" logic
correctly), that folder will not be removed because it was not created as
part of the installation -- it was created by the application itself.
I know I could just instruct CabWiz to stick a dummy file into the "empty"
folder, but then the application would have to hide the dummy file from the
user somehow, or delete it when the application starts up. I'm just asking
if there's a simpler solution to this problem at CabWiz-time instead of
runtime.
Richard Kucia
a folder beneath the application's folder. If the PDA user removes the
application, these files and their folder are also removed. This is the
behavior I expected, and it works fine.
Is there a trick I can use so that CabWiz creates an EMPTY folder beneath
the application's folder?
Here's the reason: When the application starts up, it always creates a few
folders (e.g. "Exports") beneath the application folder if those folders do
not already exist. It's possible that a user might never use the exporting
feature, and thus the application never creates any new files in the
"Exports" folder.
If the user chooses to remove the application, then these folders should
also be removed. However (if I understand "Add/Remove Programs" logic
correctly), that folder will not be removed because it was not created as
part of the installation -- it was created by the application itself.
I know I could just instruct CabWiz to stick a dummy file into the "empty"
folder, but then the application would have to hide the dummy file from the
user somehow, or delete it when the application starts up. I'm just asking
if there's a simpler solution to this problem at CabWiz-time instead of
runtime.
Richard Kucia