Put common changes from multiple files to one file using install shield 2016

Question

0.00/5 (No votes)

See more:

Hi All,

I have a requirement in my project. I have multiple install shield files for different different environment like Test, QA and Prod. I need to merge the common changes in one file and keep change separate which are not common.
The benefit of doing this is if I need to do one common change there is no need to change in all the file .

Looking forward to hear from you.

Regards,
Gaurav Gupta

What I have tried:

I am trying to know about Merge Module Project but not sure if we can achieve this using Install Shield or not.

Posted 14-Jun-17 4:08am

gaurav mangal

Updated 14-Jun-17 6:17am

Richard MacCutchan

Add a Solution

Comments

Richard MacCutchan 14-Jun-17 10:43am

I have deleted your repost of this question; please post once only.

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Dave Kreskowiak · Answer 1 · 2017-06-14T06:17:00

You can put all of your "common" files and registry settings in an .MSI and then just the changes that make the installation a Test, a QA, or Prod in a transform (.MST). The .MST is just the changes to apply to a .MSI at install-time to "customize" the installation.

You don't need a Merge Module for this at all.