LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Dependency list in project shows 2 DLL files. What do I need to do when creating a stand-alone executable file to ensure that it is included?

When the executable that I created is run on a stand-alone machine, a search is instantly launched to locate the missing *.DLL files along with about 20 other sub vi files from an example vi file that I downloaded last week.  Once the exampe vi was open, I modified the block diagram and the front panel and then I resaved it with a new name. 
 
The missing sub-vi files are the same files that I saw listed in the Dependencies list of the project along with the 2 DLL files.  This problem shouldn't be happening because I included the top level vi file that contains the sub-vi files into the source files list under the Start-Up VIs window of the application properties.  What needs to be done to make this stand-alone executabale complete?
 
 
/BCU002


Hardware Engineer•Design Reliability/Performance and Validation Group•Wavecom, Inc. - Research Triangle Park, N.C.•http://www.wavecom.com
0 Kudos
Message 1 of 10
(4,316 Views)

Hello BC002,

It sounds like the support files are not being properly attached.  Make sure that the top level VI of your project is moved over to the Startup VIs section and that everything else from the Project Files window is moved to the Dynamic VIs and Support Files window.

If this doesn't help, please provide some additional information about your build specifications.

Happy programming!

Janell R | applications engineer

Message Edited by NIJanell on 04-25-2007 10:23 AM

0 Kudos
Message 2 of 10
(4,313 Views)
Janell,
 
The problems I'm faced with is not being able to include any of the DLL files in the executable so that they are available when the executable is opened.  I thought it would be wise to simply drag the DLL files and all of the other dependency files up to the section list above where the Dependency file section is located and then move them all over to the Dynamic vi and Support Files window but that didn't help anything because when the executable is launched on a different PC, the search for these DLL files automatically starts and then a whole new set of about 35 errors are generated that states: VI files are not executable.  So that idea doesn't work.  So what can I do?
 
 
/BCU002


Hardware Engineer•Design Reliability/Performance and Validation Group•Wavecom, Inc. - Research Triangle Park, N.C.•http://www.wavecom.com
0 Kudos
Message 3 of 10
(4,303 Views)

Hello BCU002,

Unfortunately, I cannot see the images you tried to embed, as they are currently pointing to a location on your computer.  To get those images to show up, you need to first attach the image and then edit your post to point to the website where the image uploaded.  You can right-click on the attachment, choose "Copy Shortcut" and then paste that shortcut into the Insert Image script prompt.

Now, I'm not quite sure what you mean with dragging the dlls into the dependencies.  Instead, add the dll as shown in the project and make sure to move it over to the Support files when building your application, as mentioned in my previous post.  Thanks!

Message Edited by NIJanell on 04-26-2007 01:33 PM

0 Kudos
Message 4 of 10
(4,296 Views)
 
OK...So it's not a simple as clicking the mountian icon Insert an Image above and inserting the location of the picture file on my PC huh?  It works on my end just fine, but I understand you all don't see it. 
 
I really don't understand why this is such a complicated process in this discussion forum, but your explanation isn't working for me.  SO, I'm going to write what I understand to be the proper procedure and you tell me if it's wrong.
  1. Attach my image using the Browse button below.  That makes sense.  Done that.
  2. Edit my post - Edit it?  How is typing this message in the window any different from editing my post???  Are you sugesting that I Edit As HTML(http://forums.ni.com/ni/board/post?board.id=170&message.reply_to_id=244152#) using the shortcut in the lower right hand side of the frame???  I not, please explain a different way.
  3. I right clicked the adress in the window under the Attachment  heading below the lower left hand side of the frame, copied it and pasted it into the Script Prompt: dialog pop-up that appeared when I clicked on the mountain icon Insert an Image in the tools menu.  By the way,
  4. Now I see my image in the post just before I sent it.

Don't you see it now?

 

As for the DLL file - the ONLY way I can find the DLL file that I need is to refresh the dependencies list in my project.  As I explained in my previous posts, those two DLL files came with an example vi that i downloaded from the NI website last week and they must have been embedded inside of the example because I didn't create them myself and I've since resaed the original example vi as one that's been renamed by myself.  In doing so, I presume that the DLL file was inherited from the original example vi file to my own vi file.  However, that's clearly not the case because every time I run the executable file that I created with the renamed example vi file in my project, it immediately launches a searchfor the DLL files that it claims are missing!!!  SInce the DLL files are ONLY visible in the dependencies list, I can't transfer them to the Dynamic VI and Support files window in the Application Builder.  SO, I drag them up the Source Files tree in the Application Builder to the top of the tree where the Start-up vi is located and then I can move them to the Dynamic VI and Support Files window.  Those DLL files don't appaer inthe top level of the tree where the Start-up vi appears before I move it to the Start-up vi window of the Application Builder.  I'll try it again.

 
 
/BCU002


Hardware Engineer•Design Reliability/Performance and Validation Group•Wavecom, Inc. - Research Triangle Park, N.C.•http://www.wavecom.com
0 Kudos
Message 5 of 10
(4,287 Views)

 

Previous post had wrong image inserted.  This is the correct image:

 

Message Edited by BCU002 on 04-26-2007 03:48 PM

/BCU002


Hardware Engineer•Design Reliability/Performance and Validation Group•Wavecom, Inc. - Research Triangle Park, N.C.•http://www.wavecom.com
0 Kudos
Message 6 of 10
(4,285 Views)

Janell,

I did some investigating work and located the DLL files buried in C:\VXIPNP\WinNT\Bin folder that was apparently created when I first installed rscmuk2a_lv7_3_60_02.exe and rscmu200_lv7_4_30.exe.  I explored for the files from the project and included them in the tree of files and then ran the Application Builder again so thatI could include them in the Dynamic VI and Support Files window.  Next time I ran the executable file, I had to go browse for the DLL file once again to complete the opening sequence but this time all I had to do was browse for the data folder where the file was found.  Once that was done, a new error #107380202 occurred at RSCMU_Init_Base.vi popped up.  The reason indicated is VISA: A code library required by VISA could not be located or loaded.  To tell you the truth I don't have the RSCMU200 base station test equipment connected to my laptop at the time I first ran the executable file. Is this the likely cause for the error?  Can you tell me what error #107380202 means?

/BCU002


Hardware Engineer•Design Reliability/Performance and Validation Group•Wavecom, Inc. - Research Triangle Park, N.C.•http://www.wavecom.com
0 Kudos
Message 7 of 10
(4,280 Views)

Hello BCU002,

Please drag the dll files out of the dependencies section so they are on the same level as the start up VIs.  This will make it so they can be moved over to the Dynamic VIs and Support files Window when creating the application.

Thank you,

Janell R | applications engineer

0 Kudos
Message 8 of 10
(4,266 Views)

Janell,

I tried that already before you suggested it and it failed to work.  So what I ended up doing is adding the file to the project as usual by browsing from the project to the folder where the DLL file was found during my special search.  Then I added it to the Dynamic VI and Support Files section and then it worked fine.  Now the files are still sought after when I first run the executable file but now their easier to find in the data folder that resides with the executable file folder that's created by the executable builder.

Solved my own problem that time.

Thanks for your help too.

/BCU002


Hardware Engineer•Design Reliability/Performance and Validation Group•Wavecom, Inc. - Research Triangle Park, N.C.•http://www.wavecom.com
0 Kudos
Message 9 of 10
(4,258 Views)

Hi BCU002,

Just for completeness, the error "VISA could not be located or loaded" typically means that NI-VISA is not installed on your computer.  If you are building an installer for your exe , make sure under the additional installers section you are including VISA.

Brian K.
0 Kudos
Message 10 of 10
(4,239 Views)