How do I include a dll in a build specification and/or installer?

I have a custom "wrapper" dll built with VC++ that I need to include in a LabVIEW Build Specification and/or LabVIEW Installer. It needs to be installed in the C:\Windows\System32 folder.

Good morning!
You can set your support files to install
in a separate directory than your executable. In the build
specifications for your EXE, select the Destinations category and change
the path for the Support Directory to C\WINDOWS\System32 as shown
below.
Then go the Source File Settings category and set your dll to install in the Support Directory, as shown below.
Let me know if this works!
Take care!
Tanya V
National Instruments
LabVIEW Platform Product Support Engineer

Similar Messages

How can I include a success message in a drag and drop interaction - I don't see this option in the Actions on success options, and cannot figure it out?

How can I include a success message in a drag and drop interaction - I don't see this option in the Actions on success options, and cannot figure it out?

I suspected you used the eye icon on the timeline to hide the message, but that one has no impact whatsoever on the published version. It is only meant to be used for editing reasons on the stage, to hide objects temporarily on a crowded stage. It is confusing, certainly in CP8 where for both instances the same eye icon is used. In previous versions the Properties panel had a checkbox for 'Show in Output', which was IMO much clearer than this eye icon. But of course, that is only my personal opinion.

How do I include metadata information (aperture, shutter speed, ISO and white balance) to each image on contact sheet?

How do I include metadata information (aperture, shutter speed, ISO and white balance) to each image on contact sheet?

Just to expand JimHess reply. This are all the EXIF data you can include on a print. As far as I know, WB is not written to any standard EXIF fields.

How do I include multiple hyperlinked indices in a document and include keyword different from the word they link to?

I would like to include multiple indices in my ID document. How do I do that? I only managed to create a single index. And how do I let an index refer to a different word than the one in the text (e.g. "car" and "plane" are in the text but their index entry is "vehicle")? And how do I turn all index entries into hyperlinks?

I would like to include multiple indices in my ID document. How do I do that? I only managed to create a single index. And how do I let an index refer to a different word than the one in the text (e.g. "car" and "plane" are in the text but their index entry is "vehicle")? And how do I turn all index entries into hyperlinks?

How to include the NIWebAppServer.conf when building a web service installer in LV2010

Hi all,
I'm build a LabVIEW 2010 web service and creates a deployable setup installation as described in Web Services FAQ:
http://zone.ni.com/devzone/cda/tut/p/id/7747#toc12
but also would like to include my .conf file for the NI Application Web Server. The file is located in:
C:\Program Files\National Instruments\Shared\NI WebServer\NIWebAppServer.conf
This is where all settings (listening ports, SSL, users etc.) are configured.
If I look in LabVIEW 2009 build instructions for web services:
http://digital.ni.com/public.nsf/allkb/62B9C2D5C91EE8B28625778800609FF2?OpenDocument
they include this file, but it is a new procedure in LV2010 (as seen in the top link) and I can't seem to get this conf file included and installed on the deployed system automatically for LV2010. Today, I must copy it manually.
Any ideas of how to do this?
Thanks,
Mattias

Having the same problem, even if pointing the installer to install the particular file, the installer will install its own some default file. Did you find any solution?
/Carl

How do u include relevant api's in build.xml when using Ant ?

I am attempting to move from using KToolbar to using Ant to build my midlets.
I have succesfully built a simple midlet but need to know how to modify the build.xml file to include specific api's my application may use such as:
WMA, J2ME Web Services, MMAPI, or specific phone api's like Nokia.
Can anyone help?

You need to specify the wtk.midpapi so that it points to the classes you need:
<property name="wtk.home" value="[fill in the path to the appropiate SDK's class library]]"/>shmoove

Does the Lifecycle product license include the use of Flex Builder Pro and Flex SDK?

I have been trying to find out whether we can use the latest Flex Builder and SDK using the LiveCycle license or do we need to purchase additional license? We will use these products to develop Flash Applications to use with our Livecycle product.

The end user license agreement and the supplement should provide your answer:
http://www.adobe.com/products/eulas/pdfs/MET_and_LC4.pdf
2.1. Definition of OnPremise Software for Additional Adobe LiveCycle Components. If Customer has licensed
Additional Adobe LiveCycle Components as set forth on the Sales Order, then “OnPremise Software” means the
Foundation Components, the LiveCycle SDK Components, the Flex SDK Components, and object code versions of
any of the applicable Additional Adobe LiveCycle Components, including all Documentation and other materials
provided by Adobe to Customer under this Agreement. Customer may install and use the Foundation Components solely for purposes of facilitating use of the OnPremise Software in accordance with this Agreement, subject to
the following additional terms: Licensee’s right to design, implement and/or execute electronic processes that
use the On Premise Software in any way is limited to Short-Lived Processes unless Licensee has obtained a valid
license to the Production Software version of Adobe LiveCycle Process Management; (ii) Customer may install and
use an unlimited number of copies of the LiveCycle Designer software installed as part of the Foundation
Components, and its output, solely with the Foundation Components and specifically designed to operate with
the Foundation Components; and (ii) for each single (1) Deployment, Customer may install and use five (5) copies
of Adobe Flash Builder Pro software (or its successor) provided with the Foundation Components only if Adobe
Flash Builder Pro is installed as part of the Foundation Components and used in combination with the LiveCycle
SDK components to modify Additional Adobe LiveCycle Components and create Applications that integrate with
the LiveCycle Software components; all other usage of Adobe Flash Builder Pro is prohibited.

How to include a .lvlib in a build that was created using a custom .dll

I am trying to build an executable in LV2010 that uses a .lvlib that was created using a .dll from Keyence. I have added the .lvlib to the source files as "Always Included" and I have also added all of the .vi files of the library to "Always Included." I still get the error saying "Missing External Function" when running the program. The executable seems to open fine on the development computer but not on a secondary computer. Any ideas?
Solved!
Go to Solution.

...I assumed too quickly that the problem was resolved. By specifying the path I was actually able to open the executable after installing but none of the .dll functions worked. I noticed that when I specified a path on the diagram, the .dll was no longer included in the dependencies and was no longer included in the build. I guess this would explain why none of the functions were working. I copied the .dll over to the path specified on the diagram and it still did not function.
This brings me back to the original problem I was facing. I actually removed the .lvlib. I replaced all of the library vi references with the Call Library Function and deselected the "Specify path on diagram" Boolean. When I do this, the build includes the .dll in the dependencies list and it includes the .dll file in the destination folder of the install. However, when running the executable I get a list of errors that read, "Missing external function …” I have attached an image of this error. This is the same error that occurred when I was using the library, but I thought maybe the library was the cause of the problem, which is why I used the Call Library Function instead.
*I have tried adding the .dll to the support files and I receive the same error when trying to run the executable.
*I have tried adding the .dll to the support files and making it an “always include” in the installer properties under source files. This returns the same error.
I’m really not sure where to go from here. Any help is greatly appreciated!
Attachments:
Call Library Function.jpg ‏56 KB
Error.JPG ‏23 KB

How can I include external code in an Installer?

My LabVIEW program calls some external code using a Call Library Function Node. The external code takes the form of a DLL, and it needs to be located in the same directory with the executable that LabVIEW builds. However, when I look in the installer properties under Source Files, it won't let me, even under My Computer, except .vi files and a few related types that LabVIEW knows about. I can't select my DLL! And if that's true, this installer spec can't build a complete installer for my program. Is there anyway around this, to get my DLL included?
Thanks,
Ken

To elaborate on smercurio's answer:
If you only specify the DLL name in the Call Library Node configuration, LabVIEW (actually really Windows) will search through the Windows standard locations to find the DLL. LabVIEW will update the path to show the actual location Windows has found the DLL at, but it will assume that it is a standard DLL that either comes with Windwos itself or its own installer.
If you enter the entire path to the DLL LabVIEW will include that DLL in the built automaticaly and copy it into the data folder by default.
If you specify the DLL name on the diagram with the path parameter to the DLL Node, the LabVIEW compiler can not know at compile time what DLL will be used (even if you use a fixed path constant which would be a bad idea anyhow). It is then your responsibility to make sure that the DLL is installed on the target computer at that location.
Rolf Kalbermatter
CIT Engineering Netherlands
a division of Test & Measurement Solutions

Include other directories in build or installer

The engineer I am writing this program for hates to dig around for files so the software specification call for several config files to be found off the root directory.
C:/Program_Name/System_Config
C:/Program_Name/Instrument_Config
C:/Program_Name/Test_Scripts
How can I include these files in a build or installer so they are created on install and default config files placed in the proper directories?
Solved!
Go to Solution.

Look in the Destinations Category in the dialog to create a new installer. The build specifications for an installer by default puts the executables into [Program Files]\YourProjectName where [Program Files] is a token that specifies whatever is the Program Files folder for the PC you are installing to. There are numerous other tokens for other paths such as Windows, System, Desktop, ....
I would first try to put in a new folder under the [Windows Volume] branch of the tree. (There is a New Folder Icon at the bottom of the tree.) I'm assuming Windows Volume is going to be the root of whatever drive you have Windows installed on, which should be C:\
You could also add a new directory such as c:\YourProjectName which would put an absolute path for installing the executable to.

How to use a custom.dll in forms 6i

Hi,
i have made a small dll using a icon-making software, that software has made a .dll of the icon I made in that software
Now i want to use that .dll in my forms 6i. (client/server)
the dll contains only one icon named 'Icon1'
would any one please tell me how can I call that icon in that .dll to view in my forms button at run time..
is this possible..??
just for clarification, for security reasons I am not using the .ico of that icon diect from hardisk in my button thats why i made a .dll of that so that the user may not be able copy my icon
thanks in advance,

Here is the doc
Doc ID:      Note:99824.1
Subject:      How to Display User-Defined Cursors and Icons in Forms
Type:      BULLETIN
Status:      PUBLISHED
     Content Type:      TEXT/X-HTML
Creation Date:      23-FEB-2000
Last Revision Date:      30-OCT-2002
PURPOSE
The purpose of this note is to explain how to display customized
cursors and icons in Forms 6.0 on Windows platform (32 bits).
Assumption is made that resources are stored in a DLL, which is
available in the path at runtime.
It is mandatory to store the cursor in a DLL to make it available
with Forms: .cur cursor files cannot be directly loaded from the
file system.
On the other hand, icons .cio files can directly be read from the
filesystem by Forms Runtime. However we will focus on icons which are
stored in a DLL.
The article is divided into two main parts:
- how to build a resource-only DLL with Visual C++ 5.0
- how to display the cursor and the icon in Forms 6.0
SCOPE & APPLICATION
The intended audience needs to have basic knowledge in Forms Builder
and also in Visual C++ (or any other Win32 compiler).
A typical environment is Forms 6.0, Visual C++ 5.0 and Windows NT.
WHAT IS A RESOURCE ?
A resource can be considered as some extra binary information that can
be added to an executable file. Windows resources are for example icons,
cursors, menus, dialog boxes, keyboard-accelerator tables and much more.
Resources are usually stored in a .rc file, which is compiled by the
resource compiler in order to provide a .res file. These compiled resources
can then be appended to a binary executable file or a DLL.
For instance, Visual C++ 5.0 includes a resource editor which allows you to
draw your icons and your cursors, and store them in a resource file.
Part I - BUILDING A RESOURCE-ONLY DLL
Consider the following setup:
- myicon.ico: icon file
- mycur.cur: cursor file
The objective of this section is to build a DLL called proj.dll which
contains both the icon and the cursor. This operation requires several steps.
Step 1: Create a project
In Visual C++, select menu File->New... In the dialog box, choose the Projects
tab and pick "Win32 Dynamic Link-Library". Fill the project name (e.g. Proj)
and the location (e.g. c:\MyProjects). Check 'Create new workspace', check
Win32 as target platform and click on OK.
This creates a directory c:\MyProjects\Proj, where necessary .rc and .cpp
files can be stored. Place the .ico and .cur files in this directory too.
Step 2: Add a resource file to the project
Create a proj.rc file, edit it and make sure it contains the following lines:
testcur CURSOR DISCARDABLE "mycur.cur"
testico ICON DISCARDABLE "myicon.ico"
This is the resource file. Using the Project->Add to Project->Files... menu,
select the proj.rc file and add it to the current project.
Step 3: Add a dummy C++ file to the project
Create a proj.cpp file, edit it and make sure it contains the following lines:
#include <windows.h>
extern "C"
BOOL WINAPI DllMain (HINSTANCE hInstance, DWORD dwReason, LPVOID)
     return 1;
This creates an entry-point in the DLL. This function does nothing but is mandatory
to have a DLL after the build of the project.
Add the proj.cpp file to the project as described in Step 2.
Step 4: Choose the target type
At this moment, you can choose if you need a 'DEBUG' or a 'RELEASE' flavour of
the DLL. As there is not much to debug in this DLL, the 'RELEASE' flavour is
recommended. Furthermore, it is much more compact.
Using the Build->Set Active Configuration... menu, choose the Proj - Win32 Release
as the active configuration.
Step 5: Build the DLL
Now, it is time to compile the resource file, compile the C++ file, link both
together and build the proj.dll DLL. This operation is performed by using the
Build->Rebuild All menu.
After a short time, you should see "Proj.dll - 0 error(s), 0 warning(s)" in
the Visual C++ message window. This means that the DLL was built successfully.
Step 6: Place the DLL in the appropriate directory
The proj.dll file is currently located under the c:\MyProjects\Proj\Release
directory. Copy it in an appropriate directory which is reachable in the
runtime environment path.
Part II - USING THE ICON AND CURSOR IN THE FORM
At this stage the DLL is created and can be used in the Form application.
Again, this is a multi-step procedure.
Step 1: Load the DLL in the Forms Runtime environment
Assuming the proj.dll DLL is placed in a directory pointed by the
PATH environment variable, below is the piece of PL/SQL code which loads
the DLL into the Forms Runtime environment. This code can be placed in the
WHEN-NEW-FORM-INSTANCE trigger for example:
declare
     hDLL     ORA_FFI.LIBHANDLETYPE;
begin break;
     --Preload the DLL so the cursor and Icons can be found.
     -- I'm assuming the DLL is in the path here
     hDLL := ORA_FFI.LOAD_LIBRARY(NULL,'proj.dll');
exception
     when ORA_FFI.FFI_ERROR then
          for i in 1..TOOL_ERR.NERRORS LOOP
               message(TOOL_ERR.MESSAGE(i));
          end LOOP;
end;
Step 2: Display the cursor stored in the DLL
Now, you may want to change the cursor when the user clicks on
a specific button. This is an example of code that could be set
in the WHEN-BUTTON-PRESSED trigger:
set_application_property(CURSOR_STYLE,'<proj>TESTCUR');
<proj> refers to the proj.dll. Please note the < and > signs
which are mandatory there. TESTCUR is the name of the cursor resource
as defined in the proj.rc file.
Step 3: Display the icon stored in the DLL
You may also want to change the icon of an iconic button after
some specific end-user action. The appropriate code for that is:
set_item_property('IBUTTON',ICON_NAME,'<proj>TESTICO');
IBUTTON is a PushButton, with the Iconic property set to Yes.
TESTICO is the name of the icon resource as defined in the proj.rc file.
Asim.

Stand-Alone Application including ocx, dll and Word template folder

Hi,
I try to create an Stand-Alone Application with labview 2011. My problem is how i can include ocx and dll file in my executable to be run by others computers (the other computer don't have the dll and the ocx using in the application). My program use Word template who is in a folder. How i can integrated this Template folder in my executable folder.
This is the first time I create an executable, so please help me -_-.
Nki
Solved!
Go to Solution.

Hi nki,
To include the ocx and dll files you will need to build an executable for your VI and then create an installer for the additional files. I have linked 2 documents that will explain each of these steps. If you have any questions with this let me know.
http://zone.ni.com/reference/en-XX/help/371361E-01/lvhowto/exe_ex/
http://digital.ni.com/public.nsf/allkb/E09BA0E2F31D304F86256A640070058E?OpenDocument
Patrick H | National Instruments | Software Engineer

Including a DLL in JAR file (Comm API)

Writing a little app that interfaces with serial port device using the communications API and I'd like to bundle it into an executable JAR. JBuilder will create the JAR for me fine, but the issue is with the win32com.dll file thats part of the comms API. I need to include this, I don't think its possible to include as part of the executable, but otherwise the DLL needs to be in the windows\system folder. Could I include the dll as part of the JAR archive and then extract it upon runtime? If so how would I go about this?
Any help much appreciated.

There is another option. Native libraries need to reside within the java.library.path location. As it turns out, if you, at runtime, grab this property and ADD your own location to it, then set it back in to the System.setProperty() call, it will NOT work. The only way to do it is the -Djava.library.path value that tjmaven suggested.
However, if you read up on how a native library is found, it uses the ClassLoader.loadLibrary() which calls the protected findLibrary() method. You can therefore extend ClassLoader to find a path yourself.
One way is to extend URLClassLoader since it has the protection/security stuff AND the ability to look in .jar files for you. Your custom loader is created by a "launcher" class in your .jar file. First, your luancher uses getClass().getProtectionDomain().getCodeSource().getLocation() to get the absolute location of the .jar file its executing within. From there, you open the jar and look for your native library, extract it using the JAR api to a location of your choosing. Now, you instantiate the custom classloader and using this custom loader instance you load the rest of your classes. The main .jar file contains two classes, the launcher and the custom classloader, and contains the native library if you wish to do it this way. The custom classloader, you specify a URL[] of "classpath" entries. You bundle up the rest of your source in a second .jar file that you pass to the URL[] when creating the custom classloader. It will find all your classes in the 2nd jar no sweat. You can even "reload" these classes on the fly by recreating the custom classloader instance if you so wish to add a sort of "reload" feature.
Now, in your custom classloader, you override the findLibrary() and return the SAME STRING PATH that you used to unjar your native files to. This way, when the JVM asks your custom loader to load the library at some path, you return the right path to find the native files in.
I haven't verified that this works just yet, but I will soon. Primarily, my plugin engine over at www.platonos.org will support the ability to place native libraries in plugins, allowing you to effectively wrap a native library use as a plugin. Not yet working, but we'll soon have it in place.

How to change a 'debug' dll to a 'release' dll (without running a new build)?

I recently heard some best practice advice that you shouldn't rebuild your application for each environment, rather you should deploy a single package to your first environment, evaluate it, and if it passes, promote that same package to the next environment.
The first package would have debug configurations built in, including web.config, *pdb files, and dll internal references. I understand how to modify the web.config and remove the *pdb files, but how do you modify a dll to change it from a 'debug'
configuration to a 'release' configuration?
thx
Curt Zarger [email protected]

Hi Curt
In true continuous delivery any build might end up going live so you need to build as release from the beginning.
Cheers - Graham
Blog:
http://pleasereleaseme.net LinkedIn:

Don't include USER32.DLL in built application

Hello,
I would like to avoid including USER32.DLL in the installer for my built application. I am using several Windows API functions from USER32.DLL, and as soon as I select the top-level VI, an entry for USER32.DLL shows up if I click the "Files" button on the "Installer Settings" tab. I want to just use the local version of the DLL once it's installed.
I'm using another windows DLL, and it somehow isn't getting included - I think because in the "Call Library Function" configuration dialog there is no path, just the file name. If I try to delete the path from my calls to USER32.DLL (i.e. delete "C:\WINNT\System32\"), it automatically re-appears once I close and reopen the dialog box. I've also tried using just "USER32.*", but the path still gets added automatically.
Any ideas?
TIA,
Jaegen

Waldemar,
Thank you very much for your insight.
This is a very interesting/intriguing problem ... Please bear with me as I try to describe it:
It seems that LV is treating DLLs exactly as it would a sub-VI. Once one VI which uses a DLL is loaded into memory, all other VIs which use a DLL with the same name, regardless of the path used, use the same DLL. I was trying to delete the path in one VI, while other VIs with the path were in memory. Therefore, as soon as I clicked OK, LV just went ahead and added the path again. However, if I loaded the VIs separately, I was able to delete the path. I was tipped off when I did this with only one sub-VI, then loaded the top-level VI and was presented with the warning that "USER32.DLL" was actually found at "C:\WINNT\system32\USER32.DLL" for the VI I had changed.
Now of course the problem arose as to how I delete the path for a DLL call when the VI has two separate calls to the same DLL (i.e. if I delete the path for one, while the other still has the path, it won't be deleted). I had to mangle the name in one call ("C:\WINNT\system32\xUSER32.DLL"), delete the path in the other ("USER32.DLL"), then delete the path in the first. Likewise, when one VI with a call to the DLL uses a sub-VI which also calls the DLL, I had to go through this process with all the calls in all the VIs.
I hope I'm making sense. I was able to eventually get the paths permanently deleted from every call, and "USER32.DLL" no longer appears when I go to build an executable.
I'm not sure if this is a bug per se. I'm not sure what else LV could do, other than display a warning dialog when you click OK on the DLL config dialog. However, it would be nice if the application builder allowed DLLs to not be included (even if it thinks they need to be).
By the way, I did work out a very interesting work-around for this before realizing the details I described above: I included a batch file in the installer, which I called using the "Run executable after installation" option, which cd'ed to the install path, deleted USER32.DLL, then deleted itself (I didn't know this was possible until now).
I did however discover a bug in the application builder help documentation:
On the page titled "Advanced Installer Settings Dialog Box (Windows, Professional System Only)", the "- Executable" paragraph states "The file must be one of the files that you install in the Installer directory you selected in the Installer Settings tab." This is not the case. It should read:
"The file must be one of the files copied to the *Install Directory* using the "Installation Destination Settings" dialog. (Click the "Files..." button on the "Installer Settings" tab)."
Note "Install Directory", not "Installer directory".
Hopefully this all makes sense and is informative.
Cheers,
Jaegen

How do I include a dll in a build specification and/or installer?

Similar Messages

Maybe you are looking for