Jump to content

LV 8.2 App Builder uses 7.1 RTE?!?!


Recommended Posts

Hi,

I'm in the process of creating a new exe of our project. A strange thing keeps happening and I don't know what's wrong. I had LV 7.1 installed on the machine, as well as LV 8.2 to transition to the new version. I created an .lvproj and built a new .exe of our application. Lo and behold, it flashes the LV 7.1 flash screen and then asks me to select the VI I want to run, when i select the main VI of the application, it simply gives me an Error 9 message and says that that vi is compiled in version 8.2 of LV and won't open. I tried right-clicking on a vi and trying to force it to associate with 8.2, that didn't work. I uninstalled 7.1 and the 7.1 RTE entirely and when I try to run my LV 8.2 built exe it STILL manages to use the 7.1 run time from somewhere.

After that I tried to re-associate them with 8.2 yet again to no avail. When i run my exe it just tries to open them in the non-existing 7.1 RTE and re-associates them all with 7.1. Please help, i think this is a bug.

All the exe is, is a splashscreen.vi which calls our main application vi through the vi server. This worked perfectly fine in 7.1 (during distribution, we would just save all of our VIs without block diagrams).

I really need some help with this one. Thanks in advance.

Link to comment

QUOTE(Tomi Maila @ Feb 13 2007, 03:03 PM)

Did you follow LV installation order from older to newer. Was all 7.1 components installed first and all 8.2 components after them?

Yes. Everything was installed in proper order. I tried removing all of NI software this morning and then installing just LV 8.2. I still get the same thing. I called NI they don't know what might cause this. The problem is that it did this on 3 different machines.

Basically it looks like windows doesn't want to associate vis with LV 8.2. I tries to use the 7.1 RTE to open all VIs after I run my exe and even if I try to force-associate VIs with LV 8.2 by manually browsing to the LabVIEW.exe i simply get taken back to the Open With dialog box and no version of labview is anywhere in that list.

Link to comment

QUOTE(Aristos Queue @ Feb 13 2007, 05:12 PM)

Is it possible that at some point in your EXE that you call a LV-built DLL that was built against LV 7.1? That's the only thing I can think of.

Well we do have dlls, quiet a few of them but the NI engineer I spoke with, said that on his machine everything worked as expected and opened when he ran the exe. The problem with my machine is that even when I create a simple, new exe with a test vi, it flashes the 7.1 screen and gives the open vi dialog box. I'm going a little crazy at this point, will probably have to uninstall everything and use msiblaster. I can post pictures.

Link to comment

QUOTE(jhoskins @ Feb 13 2007, 06:06 PM)

Hey j,

That romulus guy is me ;-) So i just cross-posted myself hehe. Still no answer, here's what I added there:

==========

Thanks for the reply. I do understand how bizzare this must seem to you, I had the same reaction. I know perfectly well the behavior of LV built exe, been using it for 5 years. The problem here is the bizzare behavior of the .exe (any in fact, i've built several test vis and exes) on 3 different machines.

I'll try to explain what's happening:

1) I create a new project

2) I add my Test.vi to the project

3) I set my Test.vi as the startup vi (Test.vi simply calls my main vi via the vi reference).

4) I build the exe and execute it

5) Upon execution, an LV 7.1 splash screen pops up for a brief second and I get an Open VI file dialog box asking me to select a VI I want to open, all the VI files inside that window take on the appearance of LV7.1 icons, instead of 8.2. If I try to select a VI from that window, I get LabView load error 9: VI version (8.2) is newer than LabView version (7.1).

I'm used to that error after you recompile a 7.1 vi to 8.2, but I don't even have LV7.1 installed. It seems like the exe is trying to use LV7.1 RTE to run itself instead of 8.2. I though I have 8.2 RTE automatically installed by LV Dev, but I guess not since it doesn't show in Add/Remove Programs menu, but it DOES show up in MAX under software, go figure. I wish I could get someone in NI to look into this. I've never had a problem like this, it is happening on 3 PCs here and is taking up a lot of work time. I have source code I can send as well as a short video of what's happening on my machine.

Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Unfortunately, your content contains terms that we do not allow. Please edit your content to remove the highlighted words below.
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.