LV dev package develops dependency upon ISE installer .msi file (LV-based app)

[JimPryle]

Hi,

I am using LV7.1 to create custom applications. Installation of these applications requires additional access to Windows registry amongst other things, so we are using InstallShield Express to distribute the application rather than the LV native option.

Recently I noticed that when we install the custom LV application on a PC which already has the LV professional development package installed, the LV development package develops a dependency upon the .msi file within the InstallShield installer. This wasn't apparent when I first installed the custom application, but became so when other users logged onto my PC (running XP SP2) and didn't have access privileges to the .msi file inquestion.

Has anyone experienced anything like this before? Or can anyone suggest a means of identifying the specific dependency?

Any assistance would be appreciated.

Jim P.

[SachaE]

Hi,

   unfortunately we don't have a copy of Installshield here. I'm downloading the trial version (12) from here :

http://support.installshield.com/

which leads to here, but the server is currently coming up as not available despite me adding the macrovision and installshield sites to my trusted websites.

http://mktg.macrovision.com/mk/submit/eval_submit?pver=ISWEXP120E&pcode=isw&pname=installshield&ed=2...

so I can try this. Do you have a small application that shows this issue that I can try wrapping up here?

I'm trying another source for the evaluation verions from here :

http://www.componentsource.com/products/510530/19545/summary.html

(Hope it's the same one)

Do all the users have the same access to the PC (i.e. admin or power user level) or is the .msi file in a private directory?

On a quick side note, LabVIEW 8's project style approach, the distribution installer allows you to make registry setups.

You can download an evaluation version here to have a look at - exactly what do you need to do with the registry during install?

http://digital.ni.com/demo.nsf/websearch/14f9ce475127ade786256ac60070926c?opendocument

You could always put the registry access vi's as the first thing that runs as part of your application and get around the issue that way too.

Finding out the specific dependency, you could have a look at this page on the installshield website :

http://support.installshield.com/kb/view.asp?articleid=Q101515

Thanks

Sacha Emery
National Instruments (UK)

[SachaE]

Hi,

  I just ran through the wizard for Installshield express and had it set to one target (Single Executable) so I didn't get a .msi file, just the setup.exe, and I can't find any dependencies on the finally installed .exe target.

Can you please send your .ise file, and a small .exe that exhibits the same behaviour, and I'll try building it here.

Thanks

Sacha Emery
National Instruments (UK)