why does labview load vis from exe instead of vi.lib?

[dsavir]

Hi,

I have a small but annoying problem.

My project calls an exe that we created using labview. In the project folder there is folder "SpectrumAnalyzer" with "Spectrumanalyzer.exe". Every time I open my project, Labview is conflicted about the same 4 VIs and asks me if to load them from vi.lib or from SpectrumAnalyzer.exe (screenshot attached). Why does it do this? How do I tell labview not to load VIs from witthin EXEs?

Thanks,

Danielle

[Yamaeda]

remove the .exe from the project. 🙂

/Y

[Ranjeet_Singh]

Its a cnflict issue for sure. 

[dsavir]

Yamaeda, I can't do that because I want the installer to have the exe as well, so that we need to run only one installer to install our program and the exe (which can be called by the customer separately). We have done this before and not had any problems. Is there another way? Why does it make sense for LabView to search in an exe anyway? It can't use the VI from there (it shows File not Found). Isn't there some setting I can change for this?

Thanks,

Danielle

[Yamaeda]

---

@dsavir wrote:

Yamaeda, I can't do that because I want the installer to have the exe as well, so that we need to run only one installer to install our program and the exe (which can be called by the customer separately). We have done this before and not had any problems. Is there another way? Why does it make sense for LabView to search in an exe anyway? It can't use the VI from there (it shows File not Found). Isn't there some setting I can change for this?

---

It makes sense for LV to search for files in the project. 🙂 Cant you in the installer include the exe directly from disk without having it in the project?

/Y

[dsavir]

Hi,

Not that I know of. I can choose things in the installer only from the project. Like I said, we've done this before, we have both a post installer exe and a TCP-based communicator exe in the project. LabView doesn't ask me about all the TCP VIs, only about these 4.

Well, if this is the only solution, we'll either live with it or find another way to add it to the installer.

Thanks,

Danielle

[Yamaeda]

Yeah it sounds annoying for sure. I'd assume after you've told the project once it should use the vi.lib it shouldn't really ask again, unless there's some rights issue preventing this information to be written, or similar.

/Y

[Ranjeet_Singh]

During the building of your application why dont you browse from lib file instead of exe file i.e. when you include your file in project.

[dsavir]

Hi,

I don't take from the lib file, I take my built exe. the exe includes some VIs from vi.lib. Because of this, every time I open my project it tries to take some of the VIs from the exe instead of Vi.lib. So far, no problems when building the application, only when opening the project.

Thanks,

Danielle 

[Ranjeet_Singh]

@dsavir wrote:

Hi,

I don't take from the lib file, I take my built exe. the exe includes some VIs from vi.lib. Because of this, every time I open my project it tries to take some of the VIs from the exe instead of Vi.lib. So far, no problems when building the application, only when opening the project.

Thanks,

Danielle 

---

Are you have some file which is common and have different place, which is called by exe and from lib file