Using the Deployment Helper Foundation
The Deployment Helper analyzes an Xbase++ executable or DLL file and recursively determines all required DLL dependencies. The tool can operate in two modes: show dependencies or deploy dependencies. In show mode, it displays a list of all detected dependencies. In deploy mode, it copies all dependencies along with the target file to a deployment directory.
The tool automatically includes commonly used database engine DLLs that are typically required by Xbase++ applications. System DLLs are filtered out by default to focus on application-specific dependencies. When available, corresponding .config files are also included in the deployment.
Typical usage scenarios
Analyzing dependencies
This displays all detected dependencies for the specified executable or DLL without copying any files.
1) // Show dependencies for an executable
xppdh myapp.exe
2) // Show dependencies with additional warnings
xppdh -w myapp.exe
3) // Show dependencies including system DLLs
xppdh -nof myapp.exe
Creating deployment packages
This copies the target file and all its dependencies to the .\deploy directory. The deployment directory is created automatically if it does not exist.
1) // Deploy application with all dependencies
xppdh -d myapp.exe
2) // Deploy without config files
xppdh -d -noc myapp.exe
3) // Deploy with specific database engine only
xppdh -d -pg myapp.exe
Customizing database engine inclusion
By default, all supported database engines are included. These options allow selection of specific database engines or exclusion of all database engines.
1) // Deploy with PostgreSQL database engine only
xppdh -d -pg myapp.exe
2) // Deploy with Advantage Database Server only
xppdh -d -ads myapp.exe
3) // Deploy without any default database engines
xppdh -d -nod myapp.exe
If you see anything in the documentation that is not correct, does not match your experience with the particular feature or requires further clarification, please use this form to report a documentation issue.