LabVIEW Built Application Properties

[Hoof]

I have an application that uses the FileVersionInfo .NET class to get information about the currently loaded application, such as Major Part, Minor Part, Private Part, etc. This information is used to name any dialog windows that may come up and it is also embedded into data files to know what application generated the data. The small VI that I made here is a slimmed down version of what we are doing, just to illustrate my problem. When I run the VI in development, I get a -10401 error (DAQ config error), which is what I would expect. When I run it as a built executable, I get "Load Error 3" and a bunch of DAQ errors. If I switch the order of the 2 cases, build it, and then run it, I get the -10401 error and no Load Error 3. Does anyone have any idea why the order of these pieces of code would matter? They seem to be completely separate things. My problem is that my much larger application works fine in development mode, but when I build it, I get load errors and it will not run. I'm not sure what is conflicting.

Thanks,

-Hoof

[Verne_D]

Hi Hoof,

It's not obvious to me why the order of operation is causing different behavior, besides the possibility the first error causes the program to stop before the second can occur. I know that Load Error 3 is usually corrected by changing subVI properties as detailed in this KnowledgeBase article. Have you seen this before?

Also, what versions of LabVIEW/DAQ are you using?

[Hoof]

We recently made a jump from LabVIEW 8.5.1 (with DAQmx and Traditional DAQ from Feb. 2006 release), to LabVIEW 2009 SP1 (with DAQmx 9.0.2 and Traditional DAQ 7.4.4). Sorry, I don't have the exact versions of the previous configuration, just when they were released.

So we are basically running everything from the Feb. 2010 release, I believe. We did not see this problem in our old configuration, but it is very repeatable with the new software. I did take a look at that knowledge base article previously, and tried including every front panel in the application build, but it did not help. I still receive the error.

Thanks,

-Hoof

[Verne_D]

Hi Hoof,

Would mind posting your VI as a file? I want to see if it runs on my computer. I'm in the process of getting .NET 4 which is where that assembly is from, correct?

[Hoof]

Sorry, I should have posted it as a file originally. The latest version of .NET I have installed is 3.5 SP1. I think that's what you were asking, correct?

Thanks!

-Hoof

[Jim_S]

Hello Hoof,

After working on this issue, I believe that a viable workaround is to place the T-DAQ VI and the .NET calls in separate VIs and threads. In the example that I have attached, I have called the .NET VI dynamically abd I didn't recieve the error any more. If you could try this on your machine to see if this works, I would appreciate it.

JimS

[Jim_S]

Hello Hoof,

I have made some changes to this workaround so that it gets the correct version. I have added it here for you to test.

JimS