03-27-2006 09:50 PM
03-28-2006 01:45 PM
Good afternoon David,
Thank you for posting to the NI Discussion Forums. What exactly do you mean by a “LabVIEW Exception”? Is an error returned to LabVIEW from a .NET property/invoke node, or do you mean that LabVIEW actually crashes (either your program or the development platform)? 99.9% of the time, LabVIEW treats .NET calls exactly the same as the same .NET calls from any other development environment. Have you tried running the same series of function calls from another VB or C# program to see if the same exception is thrown? I believe that the problem is probably somewhere in the C# code but without a more specific description on what the error is or the nature of the error it might be hard to offer any pointers. You might want to start with the obvious things though -- look to make sure that any resources that are opened are being closed in a proper way, use of highlight execution with error clusters to determine the location of the crash, etc… Also, consider posing a screen-shot of the code if it’s allowed, so that we can take a look at what might be going on.
Hopefully this helps!
03-28-2006 02:08 PM
03-28-2006 06:16 PM
03-29-2006 10:54 AM
LV - 71.
.NET - 2.0
No config files, no panel.
I'll email you screen shots
03-29-2006
04:37 PM
- last edited on
06-24-2025
05:39 PM
by
Content Cleaner
Is this version of 7.1 actually the patched 7.1.1f2? If not, you'll need to upgrade to that in order to run with .NET 2.0. First apply 7.1.1
http://digital.ni.com/softlib
and then 7.1.1f2
http://digital.ni.com/softlib