A friendly treefrog
Sitting on our window after a rainstorm.
Inno Setup custom data directory location
In my last post, I forgot to point you to Inno Setup; go get the Inno Setup QuickStart Pack to get going.
I showed how to copy a directory full of data, like tutorials or sample data, that might change depending on the customer. That means the files are not known when the installer is compiled.
Here's what it looked like:
Source: {src}\data\*; DestDir: C:\MyCompany\data;
Flags: external recursesubdirs skipifsourcedoesntexist onlyifdoesntexist uninsneveruninstall;
Permissions: users-modify
This time, I 'm going to show how to let the user choose where this directory is located, and whether to install the contents of the directory at all.
First, let's show an obvious choice:
Source: {src}\data\*; DestDir: {userdocs}\MyCompany\data; Flags: [as above....]
That new constant will put the data in a subdirectory of My Documents, for the user that installs the program. This might be fine for you, if each user of your program is going to install it themselves, and generate thei…
I showed how to copy a directory full of data, like tutorials or sample data, that might change depending on the customer. That means the files are not known when the installer is compiled.
Here's what it looked like:
Source: {src}\data\*; DestDir: C:\MyCompany\data;
Flags: external recursesubdirs skipifsourcedoesntexist onlyifdoesntexist uninsneveruninstall;
Permissions: users-modify
This time, I 'm going to show how to let the user choose where this directory is located, and whether to install the contents of the directory at all.
First, let's show an obvious choice:
Source: {src}\data\*; DestDir: {userdocs}\MyCompany\data; Flags: [as above....]
That new constant will put the data in a subdirectory of My Documents, for the user that installs the program. This might be fine for you, if each user of your program is going to install it themselves, and generate thei…