LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Labview crashes when referencing PIAs

Labview gives errors about missing references when using a .net class library (but does not say what it was looking for--boo). When attempting to add the references used by the class library to labview, 8 of them caused LV to reference memory location 0--which results in a crash.
Some failing files: System.dll, System.Data.dll, System.XML.dll, Ivi.Visa.Interop.dll

See the attached gif images for the case of System.dll

What is the work around for this?
Why can't LV be more explicit about what references it is looking for?
Download All
0 Kudos
Message 1 of 3
(2,739 Views)
1. The tool that adds Assembly references is meant to be used only for Private Assemblies. System.dll is for example already in the GAC and hence does not need to be added.
2. In LV 7.0, there was a bug where adding an assembly which was already in the GAC caused a crash, this crash has been fixed in LV 7.1
3. As far as the missing reference error is concerned, I believe that the error message does indicate what assembly is missing[ see attached snapshot]. Could you perhaps provide an example?

Thanks
Message 2 of 3
(2,739 Views)
The error is a run time error, not a load time error--see attachment 1.

Attachment 2. Shows that LvFgen is already referenced.

I ran into the crashes trying to satisfy Labview's runtime error. Any ideas on how to determine what is missing? LvFgen works in Visual Studio tests.
Download All
0 Kudos
Message 3 of 3
(2,739 Views)