
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-18-2015 07:16 PM
Hi All,
I am building a deployment package for a software our company uses "Colligo", Part of the install process for this software includes a number of prerequisite checks or installs (dotNet4.0, Visual C++1020, etc). We currently use a batch file to do this. I wonder if it is possible to have the installer package check for the install of dotNet4.0 for example, if it does not exist is there a way to call the dotNet4.0 package and then continue with the initiating package after dotNet has been installed
Thanks for the advise
I am building a deployment package for a software our company uses "Colligo", Part of the install process for this software includes a number of prerequisite checks or installs (dotNet4.0, Visual C++1020, etc). We currently use a batch file to do this. I wonder if it is possible to have the installer package check for the install of dotNet4.0 for example, if it does not exist is there a way to call the dotNet4.0 package and then continue with the initiating package after dotNet has been installed
Thanks for the advise
Solved! Go to Solution.
Labels:
- Labels:
-
General Discussion
1 ACCEPTED SOLUTION
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-19-2015 09:08 AM
You can create one big package, use the Condition step to look for the existence of .NET 4.0 related files or registry keys and choose a different course of action depending on the success or failure of the step. More info on deployment steps can be found in this knowledge base article.
2 REPLIES 2

Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-19-2015 10:47 AM
At this moment there is no way to 'Chain' different/separate installers/packages together.
The only option is to create one big package containing all the required steps.
The only option is to create one big package containing all the required steps.
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-19-2015 09:08 AM
You can create one big package, use the Condition step to look for the existence of .NET 4.0 related files or registry keys and choose a different course of action depending on the success or failure of the step. More info on deployment steps can be found in this knowledge base article.
