| Home | Templates | Classes |
One of the key advantages of ProPath is that it does not require any runtime DLLs or external dependencies.
All logic for folder management, dataset handling, and INI file control is compiled directly into your Clarion application.
This means that deployment is as simple as distributing your application’s executable and data files, with no additional runtime components required.
ProPath integrates entirely at compile time through its template and class system.
Once added to your application, all dataset and folder management routines become part of your compiled program.
The only exception to ProPath’s no-DLL rule is when you use the First Deploy feature.
In that case, the ProPath Loader application can bundle the files you wish to deploy into a single container file that is typically named with a .DLL extension.
This container is not an executable library but a data file that ProPath’s First Deploy logic reads at runtime to extract and place the contained files into their proper locations.
If your application uses First Deploy, you must distribute this container file alongside your executable so that ProPath can access the deployment contents when the program runs.
.DLL data file) in the same folder as your EXE.ProPath will automatically create or validate required folders and configuration files the first time the application runs.
When deploying your application, be aware of Windows data virtualization and UAC elevation behavior.
Running your program directly from an elevated installer can cause configuration or INI files to be written under the Administrator’s profile instead of the end user’s profile.
To understand these issues and how ProPath prevents them, see
Why Use ProPath.
That section explains how Windows redirects writes to protected areas and how tools like SetupBuilder can launch your program non-elevated to avoid these common deployment problems.
ProPath fully supports deployment to shared or network environments.
For example, you can install the EXE and data folders on a network share, allowing multiple workstations to access shared data while keeping user-specific INI files stored locally.
When using multi-dataset configurations, each workstation can automatically initialize its own dataset or reference a shared one, depending on your configuration.
The included demo applications demonstrate ProPath deployment in several real-world scenarios, including:
See the Demo Applications page for step-by-step examples.
| Home | Templates | Classes |