My application conflicts with another Measurement Studio based application.

[richard_brockie]

Hi,

Our instrument is made by a third party, and they appear to use Measurement Studio in the development of their control software.

We use Measurement Studio when developing our test software. When we install our test application on a production machine (no programming environment installed), we sometimes get a message about only being able to use controls for 5 minutes in an "evaluation-only" mode.

It is clear that there are some library file revision conflicts, e.g.: in cwui.ocx and presumably others. The third party is using a slightly different revision of these files to ourselves. What is the the best way to consistently resolve these conflicts?

Thanks,
Richard Brockie

[chericks1]

Hi Richard Brockie,

You are correct in assuming there is a conflict with cwui.ocx.

If the target computer does not have Measurement Studio, it will not contain the .ocx and .dll files required for the executable to run. Microsoft Visual Studio .NET has a Setup and Deployment Projects type that allows you to create a MSI installer that finds all of the dependencies for the project and then installs them on the target machine when the setup is executed.

I've included the following link that demonstrates the process of creating an installer for a Windows application, using .NET or Active X controls.

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

Please respond if you have further questions or if this does not resolve your issue,

Chad AE
NI

[richard_brockie]

Hi Chad,

Thanks for the pointers.

I think I now know my mistake. I wasn't registering the *.ocx files in the installer (my distribution installation is custom due to the nature of the equipment we are controlling). The third party software installation includes the *.ocx files and it appears that the lack of registration on my part was causing my problem.

R.