Application builder dll

Hello,
I'm going to build an app.exe for my customer. When I sent it to him he claimes several missing dll's. On my machine I have everything and nothing is missing.
Is there a simple way to find out which dll's (and perhaps other things) are necessary for the distribution?
Thanks in advance
Klaus

Your dlls should be in the project and listed as dependencies. When you build the installer, they should get included. You did build an installer didn't you? You should also include any hardware drivers (DAQmx, NI-GPIB) that your program uses.

Similar Messages

Build dll error in application builder 8.6.1

Hello,
I get always an error in the LV 8.6 application builder, when I build a dll. There is only one function in it, that has a string and an error input, and nothing else. I attach a screenshot of the VI prototype, and hier is the error description:
Error 1 occurred at Building DLL.
A component needed for Application Builder does not support the required functionality. This might have been caused by installing an older version of LabVIEW after this version was installed. Reinstall the current LabVIEW version to correct this issue.
Possible reason(s):
LabVIEW: An input parameter is invalid. For example if the input is a path, the path might contain a character not allowed by the OS such as ? or @.
=========================
NI-488: Command requires GPIB Controller to be Controller-In-Charge.
After that I reinstalled LV8.6, I tried to reinstall only the 8.6 app builder, but no success.

Hello,
thank you for the reply.
I have solved the problem. I uninstalled the last installed LV version, this was 8.0. Then ran appbuilder again in 8.6, then I have got an instruction to run applibs\lvdllbuilder\lvdb.exe. Since then works.
regards
Mitulatbati

Application Builder: Can you create non-blocking, return-immediately functions in a dll?

I need to include a procedure in a dll that is non-blocking, i.e. it should return immediately after the procedure has been called, and not return after its processes are completed.
The procedure is a LabView 7.0 VI, and the dll is being created using the Application Builder. Currently the procedure completes its desired task and then returns, but I would like the function to return immediately. Thanks for your help!

Rischaard,
I don't know if that will work in a dll, however as an idea:
use the vi-server functions:
Your dll-procedure opens a OwnTreat.vi(wich will do the work) with vi-server, and run it without waiting for completion.
First thing OwnTreat.vi should do is opening (with vi-server) a reference to itself (So your caller dll can close without stopping the OwnTreat.vi)
Then OwnTreat.vi con do what YOU want. When finished close the self-reference
Maybe you need a short wait or a feedback to make sure that OwnTreat has opened his own reverence before your dll stops.
Greetings from Germany
Henrik
LV since v3.1
“ground” is a convenient fantasy
'˙˙˙˙uıɐƃɐ lɐıp puɐ °06 ǝuoɥd ɹnoʎ uɹnʇ ǝsɐǝld 'ʎɹɐuıƃɐɯı sı pǝlɐıp ǝʌɐɥ noʎ ɹǝqɯnu ǝɥʇ'

DLL created with LV 7.1 Application Builder doesn,t work when analysis subVIs are present

I'm looking for a solution of the following problem.
The DLL created by the "sum1.vi" source works properly, while the DLL create by "sum2.vi" always gives a zero result.
The "sum2.vi" source contains an additional "Hanning Window" VI (not wired), that seems to be the cause of the problem.
If I delete the Hanning VI and re-build the DLL, the same works fine
Is there a solution or is it not possible to make Labview DLLs when containing analysis VIs as filters, windows, FFTs, and so on?
Thank you for your answers.
N. Roberto
Attachments:
sum1.vi ‏12 KB
sum2.vi ‏14 KB

Roberto N. wrote:
Thank you Jordan, I'm using Labview 7.1.
Anyway I've resolved the problem by adding the "lvanlys.dll" file (present in "..\Labview 7.1\resource\lvanlys.dll" path) as support file in the building process. Now the DLL containing the analysis functions works correctly.
Natalino Roberto
Ok, you probably got lucky since the lvanlys.dll seems to implement that function directly. However most Advanced Analysis functions are just redirected by lvanlys.dll to the Intel Math Kerneal Library that gets installed with LabVIEW 7.1 and higher. The only way to get that properly installed with your LabVIEW executable or DLL is to create a LabVIEW installer in your Application Builder and make sure to select under "Installer Settings->Advanced" the "LabVIEW Run-Time Engine" and the "Analyze VIs Support". Then use that installer to install your DLL on another computer.
Rolf Kalbermatter
Rolf Kalbermatter
CIT Engineering Netherlands
a division of Test & Measurement Solutions

Application builder supporting dlls for nidaq and nidmm

I was use application builder to create installations. I don't want to include the huge installs for nidaq and nidmm. Is there a list of the dlls required that I can put as supporting files in the application builder.

I spoke with another one of our other Applications Engineers who spoke with either yourself or another person with the same question on the phone today. He indicated that there is no smaller set of DLLs to use as drivers for this code, and that the solution reached on the phone was to make the drivers available on a central server so that they didn't have to be distributed directly with the application. People could just install them from the server instead.
If this is not an option, the full install files for the NI-DAQ and NI-DMM drivers would have to be included with the built appliction and installed by the end user. Or perhaps instructions could be included with the application about where to download the drivers from the NI website (www.ni.com/downloads).
Sincerely,
Ross C
National Instruments

Can I call a regular LabVIEW VI from my C# application without first creating a DLL in the application builder?

I am writing a C# application and have LabVIEW 8.2 and the Application Builder. I want the application to call different standard VIs included in LabVIEW. One way to solve this is to create a blank VI, insert the desired standard VI, have the Application Builder create a DLL and then let the application call the DLL. Something tells me there must be a shortcut to this, is there? Aren't all standard LabVIEW VIs really DLLs underneath the surface? Can I somehow call those DLLs directly?

arnold_w wrote:
Aren't all standard LabVIEW VIs really DLLs underneath the surface?
NO, LabVIEW is a programming language and contains a lot of primitives. Some VIs are wrappers for DLL's but even calling these from C(#) might be a problem.
You can exploit the LabVIEW ActiveX interface to perform all the actions you want.
Ton
Free Code Capture Tool! Version 2.1.3 with comments, web-upload, back-save and snippets!
Nederlandse LabVIEW user groep www.lvug.nl
My LabVIEW Ideas
LabVIEW, programming like it should be!

How to add third party dll in our installer using application builder?

Hello friends,
I have one application (VI) which is using some third party dll of protocol and now I want to make a installer which should install dll along with application exe. Please suggest the way ..
Thanks
Solved!
Go to Solution.

Hi,
I placed it in project file and included it in category of "Always Included" in exe creation. Then after i created installer with needed NI drivers. But this installer didn't registered the dlls in project file. I registered it manually using regsvr32 command..
Any help to do it automatically during installation..
To brief my words, I need help to understand the process of third party dll registration during installation of installer created by application builder..
Thanks

Folder of application builder(*.exe) with run-time DLL

My application consists of main.vi, subvi folder, and example folder.
In addition, I have to add the run-time libraries for add-on tool kit (advanced signal processing, lvwa.dll) which should be located in the root folder.
(For exe application, can I set the location of DLLs to not the root folder but "DLL folder"?)
In my several trials, I can't maintain the hierachy of "example folder".
Instead of my intension, the NI application builder copied the files in the folder to the support directory.
Can I locate the "example folder" to the root folder by using NI application builder?
In summary, I want to get the folder structure by application builder.
main.exe, DLL folder, Example Folder.
메시지가 08-08-2008 01:30 AM에 labmaster에 의해 편집되었음

Hey Labmaster,
What version of LabVIEW are you using?
I am not too clear as to what you are trying to do. You can create folders and add anything from your project when creating an installer under the Source Files section in its properties.
It might be easier if you'd attach a screen shot of what you are doing or trying to do.
Aashish M
Applications Engineer
National Instruments
http://www.ni.com/support/

LabVIEW Application Builder Crash : ntdll.dll faulting module

Hello guys,
I'm currently experiencing problems while building my project (LV2012 (32 bits) , Windows 7). At the very end of application build, LabVIEW crashes with no explanation (Screenshot in french, sorry)
Windows error logging follows :
Event 1000 Application Error
Faulting application name LabVIEW.exe, version : 12.0.0.4024, time stamp : 0x4fea600e
Faulting module name : ntdll.dll, version : 6.1.7601.17725, time stamp : 0x4ec49b8f
Exception code : 0xc0000374
Fault offset : 0x000ce6c3
Faulting process id : 0x16fc
Faulting application start time : 0x01cda5350f41f87c
Faulting application path : C:\Program Files (x86)\National Instruments\LabVIEW 2012\LabVIEW.exe
Faulting module path: C:\Windows\SysWOW64\ntdll.dll
Report Id : 8e5b1344-1128-11e2-97d8-c0f8dae81bad
I had the same problem on LabVIEW 2011. I tried to build my application with another computer (also LV2012 32 bits and Windows 7 64 bits) and I do not have any error.
What is wrong with my computer?
For french people, topic in french
Thank you for your help,
Regards,
Quentin
Solved!
Go to Solution.

Solution found :
-Uninstall all NI products
-Clear registry keys related to LabVIEW
-Delete National Instruments directory into Application Data
-Reinstall LabVIEW

Passing arrays with Call Library Function does not work after application builder

Calling a DLL with Call Library Function which requires an array of data works correctly in Labview, but after building an exe with application builder, the call no longer works. Dereferecing the pointer in the DLL retuns all 0s and not the actual values.
Solved!
Go to Solution.
Attachments:
TEST.zip ‏28 KB

I did not run your code because it is a little unclear to me what it does.
Two things:
First, is the DLL you are calling the DLL-ified version of PopUpNames.vi? Then the problem is likely that the panel is not being built into the DLL.
When LabView builds an application / dll, it strips the front panel and block diagram from all VIs that it doesn't think need to show a panel at run time. This reduces file size and increases code security. The App Builder's panel inclusion logic can be overridden by Build Specifications -> Source File Settings -> Remove front panel. A better method is to put a property node on a control in a window you want to show marking it "visible"; this is sufficient to tell the App Builder it should keep the panel.
Currently Source File Settings shows "no dependencies" (clearly incorrect---another evil side effect of Express VIs I guess) but if you change the settings as shown below to keep ALL panels, one might hope the App Builder can figure it to keep the panel when it deconstructs the Express VI. (Alternatively convert the Express VI into a regular one.)
A second comment: I am a bit flummoxed at the larger goal here. You are calling LabView DLL from LabView, which doesn't make a lot of sense, so I assume your larger goal is to call LabView from C or vice-versa. In that case be aware that your DLL is x86 (32-bit) but you are passing 64-bit ints as your pointers. In this case it is 32-bit LabView with 32-bit pointers in embedeed in 64-bit containers calling 32-bit LabView with 32-bit pointers in embedeed in 64-bit containers, so it all works, but if your going to call this from C or whatnot you're going to have to follow that same design.
When calling C code the LabView Call Library Function does have a "unsigned pointer-sized integer" data type that always appears to be 64 bits in the dev env but which actually passes a 64 or 32-bit int to the DLL depending on the environment. The "pointer sized int" has to be 64 bits in the "LabView" part of the code because LabView's strong typing requires the data type to be determined at compile time. Casting all pointers to the largest data type in LabView makes it possible to write platform-independent code, but down at the Call Library level you still have to put the right number of bytes on the stack.

Error message "VI is not executable"! Need help with Application Builder

Hello,
I have a problem with an application, built with the Application Builder. I have read some threads about the problem I have, but I still don't know a solution.
When I run my front panel from LabVIEW, everything is good. So, now I created an application (and an installer) to be able to run it on other PCs as well. This application does not work. Everytime I start it on my PC, I get the error "VI is not executable. ...". I read in several forums solutions for this error, but I cannot fix it! I've changed my properties for the builder, but with no success. Perhaps, anybody has more ideas, what's the problem.
To get a better idea from my project, here a little description of it:
In the block diagram there is a while loop which is continuously runned. In this loop I only set some properties for the layout of the front panel, such as decorations which will be hidden/shown and changes of colours of indicators... For the rest, it waits for a click on the button "Start" in the front panel. After that, a DLL is called to communicate with a USB device. Some measurements are carried out and the DLL is closed. I hope, you can get a global idea from my block diagram...
I use LabVIEW 8.5, the DLL is a third-party DLL, which we wrote on our own. But I think the DLL works properly, if it is called from a C# application it works and it works, too, by calling it from LabVIEW when I am in development mode.
It's a project for university and I'm just a beginner in LabVIEW, so I don't have so much experiences in it, but I think i improved my knowlegde about LabVIEW very well in the last weeks!
So, i hope to get an answer soon (the deadline for the project is not soooo far away )
If you need more information, please let it know...
I would be very grateful if there is someone with a working solution...
Kind regards from the Netherlands,
Sebastian

Sebastian,
Your architecture makes it very difficult to debug this and other problems. Does the error message mention which VI is causing the problem? It is very important to wire your error clusters everywhere. In LabVIEW, when a node throws an error (Error.Status = T), future nodes do not execute. At the end, place an error cluster indicator that you can see on your front panel. When an error posts, you can right click the indicator (even in a compiled application) and select "Explain Error".
This is a start, but you really need to push this into a queued-state machine before this gets any more complicated. As it were, if anything in your loop hangs, your whole application hangs. See attached for a queued-message handler (not advisable for actual applications, but you get the point. You would want to have a type defined enum in lieu of strings, and shared data between states differently, etc.)
-Jason
Message Edited by LabBEAN on 01-20-2009 08:36 AM
Certified LabVIEW Architect
Wait for Flag / Set Flag
Separate Views from Implementation for Strict Type Defs
Attachments:
State Machine.vi ‏18 KB

Several question s about runtime Engine, application builder and labview player

I am a little confused by all the options to distribute a program.
Please help bij answering (one of) the following questions:
1. Does an application built with the application builder always need the LV runtime engine? The LV runtime engine is 33 Mb to download!
2. Is there anyway to make a 'normal' executable that runs on a windows machine, without any supporting installed software?
3. What is the advantage of the labview player above the runtime Engine?
All questions refer to the latest software versions of NI software
Thanks in advance,
Regards,
Ferry

ferry1979 wrote:
1. Does an application built with the application builder always need the LV runtime engine? The LV runtime engine is 33 Mb to download!
Yes, the runtime engine contains all the stuff that is common to all LabVIEW applications. This is not any different than e.g. the Visual basic runtime (VBrun...) or dforrt.dll for Fortran.
If you built the application, you can strip it a little bit by including the runtime with the installer and leaving out unneeded modules (see image from the 7.1 builder).
The advantage of a seperate runtime engine is that applications are very small. The runtime needs to be installed only once. On any broadband connection, 33MB is peanuts. I distribute everything without runtine, but tell people to download and install the runtime directly from NI.
(In LabVIEW 4, no runtime was needed, with the disadvantage that even the simplest program was multiple megabytes. Not an efficient solution).
(Maybe in a few years LabVIEW will be so prevalent that the LabVIEW runtime will be part of a standard OS install ;
2. Is there anyway to make a 'normal' executable that runs on a windows machine, without any supporting installed software?
No. See above.
3. What is the advantage of the labview player above the runtime Engine?
The two are quite different. The labview player is more a simple educational tool, because it lets users inspect the diagram. It is not designed for any serious application deployment.
Message Edited by altenbach on 08-21-2005 10:05 AM
LabVIEW Champion . Do more with less code and in less time .
Attachments:
runtime.png ‏24 KB

"file already exists in the destination" during application build

I am trying to build an executable and have gotten the following error:
The file already exists in the destination.
C:\Program Files\National Instruments\LabVIEW 8.2\vi.lib\Sentech LV 82\Shared Library - Trigger SDK\StTrgApi.dll
WHen I start the build I go to "Build Executable" then click "Build"
The VI for the project I have open is the Startup VI and I do not list any Dynamic VIs or Support FIles.
I am using Labview 8.2
I installed a user library for a USB camera from Sentech wich I am using and it works fine in Labview 8.2
When I try to do the build I get the error shown above. The file it is referencing is there along with the .lvlib file.
I tried removing the file shown in the error message to see what would happen and I continue to get the same error even though the file is not there. I even restarted LV and still got the same error.
I am new to the application builder (v7 ?) and have not been able to find any good tutorials. Does anyone have any ideas on this error or a good place to learn more about app builder.
Thanks
Keith

I am new to the application builder (v7 ?) and have not been able to find any good tutorials. Does anyone have any ideas on this error or a good place to learn more about app builder.
Thanks
Keith
Hi Keith,
you can check this Link out for a tutorial on app builder.
Regards,
Denver

Error Building DLL, LabView 8.2

Hello everybody,
I'm building a
CVI application. I need some functions of LabView (related to time
series analysis), so I'm trying to build DLLs with the .VIs I need. I
followed all the steps necesary and visited all the related topics at
ni.com. I always get the following error:
Visit the Request Support page at ni.com/ask to learn more about resolving this problem. +¡
Use the following information as a reference:
Error -2147221480 occurred at Building DLL stub.
This can be caused by illegal function or parameter
names. Please verify your names are legal C identifiers and do not
conflict with LabVIEW headers
This error code is undefined. No one has provided a
description for this code, or you might have wired a number that is not
an error code to the error code input.
Once, I got a correct DLL with no errors, so it should be possible for others.
This is an example of what I'm trying to compile:
And this is what appears, only for a moment, at the end of the
compiling (it didn't appear when I manage to build with no errors):
I'm using: LabView 8.2, LabWindows CVI 8.5, NI-DAQ 8.5, Windows XP (SP2)
Any suggestion is really appreciated.
Maybe another way to use this functions in CVI (I need functions related to spectral estimation, ARMA; MUSIC,...)
thank you!
Eduardo Tamargo
Spain

Hi Tamargo,
The following KnowledgeBases may help you find out what is happening:
Creating and Calling LabVIEW DLLs with Various Data Types from Microsoft Visual C++
What are the Differences Between "Array Data Pointer", "Array Handle", and "Array Handle Pointer"?
Calling a LabVIEW DLL from C with an Array in a Cluster as a Parameter
Have you tried developing a very simple VI with an array as an input parameter and checking if the same problem takes place when you build the DLL?
Regards,
David Oña

Application builder (using OpenG source)

I just made a LV program and executable thing in LV8.2.0.
Only one function (for converting cluster->ini) from OpenG was used to make the program easily.
When I copy the program folder, so many OpenG (maybe related to the converting routine) codes were created in subVI folder.
My question is,
1. In distributing source code, Is there some DLL or convenient format file for OpenG not to copy many Vis?
2. In making executable program by NI-application builder, how to treat the OpenG library if I have only one Vi ?
And as other question,
3. In NI buidler, the external libraries (run-time/DAQ/VISA) may be rather big.
How can I make the whole program( application+libraries installer) as small as possible?

labmaster wrote:
1. In distributing source code, Is there some DLL or convenient format file for OpenG not to copy many Vis?
2. In making executable program by NI-application builder, how to treat the OpenG library if I have only one Vi ?
And as other question,
3. In NI buidler, the external libraries (run-time/DAQ/VISA) may be rather big.
How can I make the whole program( application+libraries installer) as small as possible?
3: The DAQmx installer has several versions the smallest being 40 MB? and the largest 150 or something.
I think the VISA installer has the same options.
Ton
Free Code Capture Tool! Version 2.1.3 with comments, web-upload, back-save and snippets!
Nederlandse LabVIEW user groep www.lvug.nl
My LabVIEW Ideas
LabVIEW, programming like it should be!

Application builder dll

Similar Messages

Maybe you are looking for