Resources |
|
|
|
Resources |
|
|
Resources |
|
|
|
Resources |
|
|
|
|
||
OverviewDependenciesPrimer FilesGlobal FunctionsScript FilesPlugins
Many of today's development tools require that you distribute certain runtime files along with your application. In Setup Factory, these are referred to as dependency modules.
Dependency modules are run at the very beginning of the setup, before any screens are displayed or any project actions are executed. All dependency modules that have been added to the list will be executed sequentially in top-down order as they appear at design time. Each module will execute its own detection script and if required, run its installation script. If any module is determined as not required from its detection script, the next module will be run.
While dependency modules are often used to detect and install, they can also simply be used as detection for technology for used in your install.
Dependency modules can easily be created on your own, or you can download available modules from the Indigo Rose web site, www.indigorose.com.
Tip: You can create new modules by selecting Create new module... from the Advanced button on the Dependencies dialog. Another quick way to create a new module is to modify one of the existing modules and then select Export module... from the Advanced button so you can use it in other projects. You can also include modules from other locations by selecting Browse for module... from the Advanced button.
Please consult your development tool's documentation to determine what files or technology you need to distribute with your software.
A list of the dependency modules that are currently selected to be included in your project.
The names of the modules that will be included in your project.
Brief descriptions of each module.
The build configurations that each dependency module is a part of.
By default, all dependency modules are processed before the first screen of your setup (normally the "Welcome" screen) is shown on the user's desktop. This guarantees that all checks were performed, and all required technologies are available when your setup is starting its tasks. However, there might be situations where this is not desirable.
When this option is checked, the dependency modules are processed only after the last screen of the "Before Installing" sequence is shown to the user (normally the "Ready to Install" screen), and before the On Pre Install event script is started.
For example, if you deploy a database driven application, and your product needs a database engine to be available (such as any edition of SQL Server Express) during the installation for the execution of SQL script, the database engine could be installed even when the user changes his mind when reading the licensing terms (just an example), and aborts the setup prematurely. With this setting enabled, the database engine would be installed only if your application is also installed and the user agreed to proceed with the setup after reaching the "Ready to Install" screen.
Note: When starting the dependency installation after the last screen in the "Before Installing" sequence, it makes sense to perform the installation of the technology in passive mode, instead of asking the user for confirmation. In the installation script of the dependency module, you typically will find a variable to control if a prompt should be shown to the user - it is suggested that this prompt is suppressed.
Here is an example, where you would change the bShowUserPrompt to false in the script, and change the default behavior:
Changing this to false will eliminate the prompt to install the required technology, but will not hide the progress window of the installer running in passive mode, showing the user what is being installed as part of your own installer, which is most likely how you want your setup top perform.
Open the Add Dependency Module dialog so you can add a new dependency module to the current project.
Remove the currently selected dependency module from the setup.
Open the Dependency Module Properties dialog so you can edit the currently selected dependency module.
)Move the selected dependency module up one position in the list. The order in the list represents the order in which the modules will be merged with your project file at build time.
)Move the selected dependency module down one position in the list. The order in the list represents the order in which the modules will be merged with your project file at build time.
Export the current dependency module settings to a file (*.XML).
Create a new dependency module.
Browse your system for a dependency module file (*.XML).
Open your web browser to a web page where you can find more Setup Factory dependency modules.
Learn More: Indigo Rose Software - Setup Factory - Buy Now - Contact Us