#5 - Dual Paths with an External Control File

Previous  Top  Next

Here are the considerations for this combination of settings:

·	Most data files go into the MAIN folder

·	Control data files and INI files go into the SYSTEM folder

·	The SYSTEM data path has the location set by CSIDL and template values

·	The MAIN data path is set from an External Control File

·	The application INI file is managed by ProPath

·	CapeSoft's FM3 is included in the application

·	First Run is enabled and the user can confirm the MAIN location suggested by CSIDL values or change it

·	Developer Mode is enabled and controlled by an External INI file

Where will the data and INI files go?

In this example, ProPath will use the CSIDL location (as returned by the Windows API) to obtain the base folder, then two other levels ( LANSRAD and DemoDefault ) will be added to it.

The actual data path to the MAIN data folder for this example would be:

XP       C:\Documents and Settings\User Name\My Documents\LANSRAD\DemoDefault
Vista       C:\Users\User Name\Documents\LANSRAD\DemoDefault
Windows 7   C:\Users\User Name\Documents\LANSRAD\DemoDefault

Note: the Company Name is an optional folder level for CSIDL_PERSONAL. Some people prefer to put the product name it that field and eliminate the Company Name.

The actual data path to the SYSTEM data folder for this example would be:

XP       C:\Documents and Settings\User Name\Application Data\LANSRAD\DemoDefault
Vista       C:\Users\User Name\Roaming\LANSRAD\DemoDefault
Windows 7   C:\Users\User Name\Roaming\LANSRAD\DemoDefault