Duplicate lvanyls.dll file collision in real-time build specification

[jmorris]

Hello again you helpful forum-goers!

I'm having a problem getting a required .dll to deploy to my real-time target along with my real-time executable.  When I include it as a "Always Include" file, with a directory of the support folder (C:\ni-rt\startup\data), I get the following message when I try to build my application (and when I generate the preview of it in the build specification properties):

LabVIEW prevented a file name collision during the build. Duplicate file names cannot be copied to the same destination. You can rename files as part of the build process to avoid name conflicts.

The following files were moved to a unique location:

C:\WIP\CP431 (WIES)\Engine Model\lvanlys.dll
C:\Program Files\National Instruments\LabVIEW 2010\resource\lvanlys.dll

It ends up putting a copy of the dll in both a "data" folder and a "data0" folder inside the support folder listed above, neither of which gets copied to the support folder where I need it to be when I deploy my executable to the real-time target.

However, when I remove the dll from my "always include", the preview in the build specification properties looks correct (one copy of the dll in the support folder), but it does not actually copy the dll into the support folder when I rebuild and deploy it.

Can anyone give me a hint as to how to get the dll deployed with my application, with or without a warning (preferably without)?

I have placed the dll there manually for now, but I want an automated solution so that I don't need to worry about forgetting it in the future if I have to recreate this installation.

Thanks very much!

-Joe

[Patricia B]

Hello,

Are you using LVRT 2010 or LVRT 2010 SP1? Also, what O/S are you developing on?

Regards,

Patricia B.

[jmorris]

Patricia,

I believe my version of LabVIEW is 2010 (the About window says v10.0f2).  The OS is Windows XP SP3.

[Patricia B]

Hello.

Perhaps this article will be of some assistance.

Name Collision Occurs When Building My LabVIEW Executable

https://knowledge.ni.com/KnowledgeArticleDetails?id=kA00Z000000P9nSSAS&l=en-US

Regards,

Patricia B.

[jmorris]

Thanks, Patricia, but it wasn't immediately helpful.  The article talked about LabVIEW 8.6 and earlier only, although it did have a link to the changes in LabVIEW 2009, which included putting all files in the executable instead of outside folders when building. 

From reading the changes article, though, it occurred to me to try reading over the build log file, or select the "why is this in dependencies", to try to determine why the lvanyls.dll file is being included the first time.  Unfortunately I'm on to the next project now, so I don't know when I'll get another chance to look into this.

Thanks for the suggestion!

-Joe