Installshield Merge Module Rather Than Run-Time Engine

[jacko]

I create installations for our company using Installshield 11 Professional.  At this point, the only way to install the necessary files to run a Lab View application is to add the Lab View 7.1 run time engine into the setup.  

What I am looking for is an alternative.  I am hoping there is some sort of merge module out there which can be added to Installshield so I don't have to call the Lab View run-time engine installer from my installer. 

Does such a thing exist? 

Or does anyone have any advice on how I can make a Lab View installer using InstallShield and make the installation unified?

I don't prefer the current setup I have where our software installation begins, then the run-time engine installer takes over, and then our setup continues.

Thanks for any help,
Adam

[ChrisJ]

Hi Adam,

There is some useful information here that might be of help:

http://digital.ni.com/public.nsf/websearch/373FAF5ED3A6FB1486256D7D0001496C?OpenDocument

Good Luck!
Chris J

[jacko]

Thanks for your reply Chris, that was helpful info!


Best,
Adam

[rolfk]

---

@jacko wrote:

Thanks for your reply Chris, that was helpful info!


Best,
Adam

---

There is actually a function in the Distribution Kit Builder under applibs\distkit\NiMsiDistKit.llb\MSI DK List Merge Module Dependents.vi that will return to you all dependencies to a specific merge module. It is password protected but the front panel is simple enough that it should be understandable to be called in a simple VI of your own. It returns an ID code but the first part of the name should give you an idea about which merge module is meant. Alternatively you could actually get the ID code for each merge module as well through applibs\distkit\NiMsiDistKit.llb\MSI DK Get Merge Module Signature.vi and compare the returned ID codes to identify each merge module 100%.

Of course if you would know the MSI API, the functions in those VIs could be implemented with a few API calls too.

Rolf Kalbermatter

[jacko]

Hi Rolf,

It seems to me that you are explaining the problem I encountered after finding the merge modules which Chris led me to.  That problem was which merge modules to use?  I have in fact been trying to identify which modules I'd need, and was going to do it by trial and error.  If there is an easier way then I'll give your method a shot. 

Is this what you are refering to in your message above? 

Thanks,
Adam

[rolfk]

---

@jacko wrote:


Hi Rolf,

It seems to me that you are explaining the problem I encountered after finding the merge modules which Chris led me to.  That problem was which merge modules to use?  I have in fact been trying to identify which modules I'd need, and was going to do it by trial and error.  If there is an easier way then I'll give your method a shot. 

Is this what you are refering to in your message above? 

---

Well, I'm not sure I understand you correct, but yes I think that is what my message meant. Basically if you look at the two VIs and try them out you will more or less see how they work.

You can then try to create a small tool, that given a *.msm file as input will tell you which other msm files you need to include in your Install Shield installer. If that is easier than trial and error is of course something you can depate over. Also note that the order of inclusion of msm files in an installer seems to be important too. The lowest one in a depency chain should be first I believe.

For your particular problem you would look at the LVRunTime.msm file to get a list of all other modules you need to include in your installer. I actually would suspect that Install Shield should have some functionality to list dependencies of merge modules, too.

Rolf Kalbermatter