LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Installed Program Error

I have attached my "problem VI", About.vi. Thanks you for the personal attention to this matter.
0 Kudos
Message 11 of 14
(567 Views)

The reason you are having the problem is the .NET issue I mentioned earlier.

 

The property  and invoke nodes in your About.vi are the same .NET interfaces I had problems with.

 

Install .NET framework on the problem machines and you should be good to go

0 Kudos
Message 12 of 14
(562 Views)

Thanks for the input. Valuable info. 

 

My app/installer will be downloaded from a website. Other than specifying a PC running 2000, XP, or Vista, I have no control over the configuration of the target machines. Any other suggestions?

 

How did you determine that it was a .NET issue?

0 Kudos
Message 13 of 14
(550 Views)
How I could tell it was a .NET property: When you right click on the offending property nodes you get a .NET menu. 
 
As far as how to deal with the issue, you have a couple of options.
 
1) Provide documentation that specifies that the MS .NET framework must be installed prior to running this application. You could even write a small LV app or batch file that they could use to check for presence of .NET on the computer (by looking for the appropriate registry keys)
 
2) Remove the .NET calls from your about screen and use the EXE version vis attached here. These use a dll call to a MS library called version.dll (I am not sure who wrote them, but they work nearly identical to the .NET versions)
 
3) Add the .NET installer to your installation and run it's setup.exe after your installer has completed.
 
My personal vote is for #2
 
 
 

 
Message 14 of 14
(545 Views)