In our company we have several modules that can be included in several products. Just what merge modules are for.
My problem is that each module exists in both a developer version and a release version, both having a merge module located two different places.
When building one of our products, from the development branch, we want to include the merge module from the development branch as well and when building from release branch we want the release merge module.
Is it possible to include merge modules not in the repository? Just like the path variables where we can switch between two different versions of the same file just by changing the path variable.
Hobe someone have a greate idea because it will just make life much easier making merge modules instead of starting all over every time.
The Merge Modules tab on the Options dialog box (which is displayed when you click Options on the Tools menu) lets you define the directories where merge modules are stored. So, perhaps modifying the locations there, depending on which build you are generating, will meet your requirements.
If you build releases from the command line with ISCmdBld.exe, you can use the -o command-line parameter to set the merge module locations. As an alternative, you can use an .ini file to set command-line parameters such as the merge module locations. So, perhaps switching between a development branch .ini file and a release branch .ini file--where the appropriate merge module paths are specified--would be useful.
