Issue with cwdaq.ocx and Interop .dlls in .Net 2.0

[dc128]

We have an older .Net 1.1 program that uses DAQ traditional and some NI user interface controls.  There have some modifications to other portions of the program, but not to the portions dealing with data acquisition, user interfaces, or data storage.  I double-checked, via diff, the modifications made to the files to be certain of this.

Both versions work properly on the developer's machine.

We have two test machines, each running a different version of Windows.  Traditional DAQ 7.4 and an older version of traditional DAQ (7.0 or 7.1) is installed on the other machine.  The hardware and NI software on the test machines seem to be configured correctly.

On the test machines, the new version installed next to the old version, but many of the .dlls and ActiveX components in common were updated when installing the new version.

When I attempt to acquire data with the new version of the program, it does nothing.  When I attempt to acquire data with the old version of the program, it works properly.   No error messages are displayed in either case.  The same behavior is observed on both test machines.

My best guess is that, when installing the new version, there is some linkage issue with my AxInterop.CWDAQControlsLib.dll, Interop.CWDAQControlsLib.dll, and cwdaq.ocx.  I've examined the dependencies for the .dlls for both the old and new version and haven't found any obvious differences.

I'm hoping that someone can provide me with some suggestions on possible causes and solutions.  Converting to DAQmx is the next step in updating this program and would obviously solve it, but the changes made so far are needed in a shorter time frame.

I'm not authorized to release the code, but I'll try to provide any details you need.

Thanks.

[dc128]

Also, it would probably help to mention that the code was converted from .Net 1.1 to .Net 2.0.

[MilanR]

Hi dc128,

Do both of the test machines (with one running Traditional DAQ 7.4 and one running Traditional DAQ 7.1) exhibit the same behavior? Do both machines have problems running the newly compiled program and no problem running the old program? Which version of Traditional DAQ are you compiling with on the development machine?

One thing to try is create a quick example that reads from the hardware and see if that is working on the development machine and both of the test machines. This will help to see if the current configuration is capable of linking against the drivers correctly.

Finally, what is the hardware you are using?