LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

how can I avoid the inclusion of the kernel32.dll in the installer?

Solved!
Go to solution
Dear Members
 
Does anyone know how to prevent the inclusion of the Kernel32.dll in the Installer?
The problem is that I am using WINAPI calls. Doning so forces the installer to include
this DLL into the project. This file will copied into the installer package and reside
inside of the program folder after installation.
I have programed the project with LV 8.5 Windows XP and compiled it for 2000 or later.
The same happens if I do so for XP or later.
Is there a way to avoid this binding?
 
Kind regards
With kind regards

Martin Kunze

KDI Digital Instrumentation.com
e-mail: martin.kunze@digital-instrumentation.com
Tel: +49 (0)441 9490852
0 Kudos
Message 1 of 3
(2,627 Views)
Hello,

I found this two threads - I hope this helps:

http://forums.ni.com/ni/board/message?board.id=170&message.id=148047&requireLogin=False

http://forums.ni.com/ni/board/message?board.id=170&message.id=45644&requireLogin=False

With best regards,

Ralf N.
Applications Engineering
Germany
0 Kudos
Message 2 of 3
(2,597 Views)
Solution
Accepted by M_Kunze

Just for historical purposes, there are two very good workaround:

Enter only the library name if the library is in the search path of the system.  See the Call Library Function Dialog Box Help.

Use Specify path on diagram for the Call Library Function Node, and enter the system dll's path in a constant.

 

 

Message Edited by chris.b on 04-01-2009 05:10 PM
Chris Bolin
LabVIEW Partner Program, CLA
0 Kudos
Message 3 of 3
(2,383 Views)