Exe start takes much time (loading the VIs)

[Matthias_H]

Hello,

the start of my executable takes much time because the VIs of my project (my own VIs the the VIs written by NI) are loading slowly. I can see the loading dialog before I can see my front panel:

It could be that one VI or Control (*.ctl) will load 20 seconds!

That means my VI is not running at this moment. After the VIs were loaded my main VI will run and I can see the front panel.

I leaved the build specification options at their default values.

That means all VIs are set to "include if used" (or how it's called in english) within the build specification options. And I'm not loading VIs dynamically within my application.

Why is the start of the executable so slow?

What can I do to?

Regards

[Norbert_B]

Matthias,

loading code alway will take some time. Depending on the size of the project, you will have a short time or a long time.

So what is the size of your project, e.g. how many VIs, ctls, ... contains your EXE?

Another thing is that you are seeing a "search" dialog. This indicates that relative paths in the project are not correct, so the runtime engine has to search for the components. As you can see, the application IS searching outside the EXE. So you definetly have to check your relativ paths (first instance for finding dependencies).

If you cannot make sure, that all components are loaded using proper relative paths (e.g. because of xctls, lvclasses, ...), you might want to configure search directories for your EXE to shorten the time of search.

One thing which you might want to check is the optimization for code removal from the EXE. It seems that you are cutting out some pieces. 

Play around a little with those options and look if it changes anything.

hope this helps,

Norbert 

[Matthias_H]

Hello,

thank you.

My executable will start on any PC where the LabVIEW runtime is installed. So all VIs are included within the exe file. And so I think the paths will be correct.

I will check it, but this is strange.

I'll test the options you posted.

Maybe it has something to do with LVOOP and the dinamic dispatch VIs. I'll try to set the VIs not to dynamic.

[Matthias_H]

Hello,

I found out why the dialog poped up: I copied my exe file without the "data" directory LabVIEW creates and so the lvanlys.dll was not there.

I think LabVIEW looks for the dll and if the dll doesn't exist the search dialog will pop up.

Thank you and sorry for that.

Regards