11-10-2009 04:15 AM - edited 11-10-2009 04:17 AM
Dear all
When I build an application from my project LabView asks for nilvce.dll. As this DLL is not installed on the computer I press ignore item and LV goes on build the application. Finally the execute is successfully build and I can execute it. How can I avoid referencing nilvce.dll?
But I observe that this executable is consuming almost all processor power while waiting for GUI-events. This does not occur in the development system and there is no wait missing in any of the loops in the program. Occationally the program hangs while executing Enqueue Element At Opposite End.VI from the Queues palette.
Is there a link between these topic and referencing nilvce.dll?
Regards,
Jörn
P.S.: I am working with LabView 8.6.1f1
11-10-2009 05:04 AM
11-10-2009 05:32 AM
Hi muks,
you could have known from this threat that your tip does not exactly meet the point. nilvce.dll does not exist. But it is referenced by some elements. I suspect that these elements might cause my other problem. And furthermore building the executable and running it (up to some point) works without having this DLL on my computer. So would like to gather some information about the objects referencing nilvce.dll in the hope that I can remove them to get rid of my second problem.
Regards,
Jörn
11-10-2009 01:59 PM
I have found the solution to my second problem: After detaching the application, building a new one and compile after each step I found the reason: In one sub-VI I programmatically closed the front panel and configured the VI to close the front after execution. That is too close and hang up the runtime engine in a power consuming loop like the classical loop without wait. So it doesn't has to do something with nilvce.dll.
Nevertheless it would be nice to know who to remove referencing nilvce.dll to clean up the code.
Regards, Jörn