LabWindows/CVI

cancel
Showing results for 
Search instead for 
Did you mean: 

.Net library problems

Solved!
Go to solution

I've been working on a couple of projects in our main LabWindows CVI project, and for the first time I've used the .NET controller functionality to import a C# library file. One of these is used to control some external hardware, and the other addresses simple functionality to allow General Midi sound to be incorperated.

 

Both work fine on my development machine, both in debug mode advancing a line at a time, and also when installed on the machine. This is where the problems started.

 

Two days ago I attempted to install the program on another PC for testing purposes. Unfortunately the new functionality didnt work and caused the program to crash with the generic "Your program has generated an error and needs to shut down message"

 

Having put in some messageboxes to see where the process breaks down, it appears to occur at the point where the Initialization call occurs.

 

After attempting to run it on another laptop with the same results I then installed the development environment on that PC, and the problem went away, which suggests I'm missing a file or two that I need to distribute as part of the installer.

 

Can someone suggest what might be missing and a list of any files that need to be installed as part of the package.

 

Incidentally we stopped using the installer supplied with LabWindows CVI, as it used to (I am informed) contained some form of encryption, which we are prevented from using in any part of development - something to do with US distribution laws - even though I'm based in the UK. I dont know whether using the LabWindows installer would automatically pull all the files I need to distribute or not. Its been a few years and revisions since I last used it

0 Kudos
Message 1 of 3
(3,064 Views)

Okay... had a thought after posting this as to how I could prove what was going on. I set one of the programs running - the sound producing one - to ping every 5 seconds. I then uninstalled the development environment - we are using CVI2010 SP1. The program continued to run perfectly well even after LabWindows had been completely uninstalled.

 

However as soon as I shut it down, and started it up again it failed with the same generic message I had seen before. This suggests to me that the program is relying on something that was previously available from LabWindows, but since the uninstall has disappeared.

 

So the question is what might that be?

 

Regards


Gavin

0 Kudos
Message 2 of 3
(3,057 Views)
Solution
Accepted by topic author umquat

Okay latest update...

 

Worked out that by installing the full CVI runtime engine on the PC's where the software doesnt work, then the problem gets fixed. However given that the software we are shipping is only a 20 MB download, I'd like to work out as we've done with previous issues, which of the many components contained inside the CVI runtime engine are the ones I actually need, and just ship those.

 

So to recap.... I have a piece of software that fails at the Initialize command when trying to connect to C# Dlls. What am I missing?

 

Best Regards

 

Gavin

0 Kudos
Message 3 of 3
(3,049 Views)