skazarians

Sorry, I forgot to mention that these DLLs were developed in house.  However, I can see how it would become a mess, especially if there is no defined end to how far to include. Thanks for the responses.  

I am developing a packed library that puts a LabVIEW wrapper on calling functions from a single DLL, and have noticed that, when building it, it does not grab the nested DLLs that are being called by the main DLL.  Is this a known behavior?  And can I set it to copy all dependencies into the builds folder?

I know I can manually set it to include specific files, but seeing as the dependencies are listed within the DLL itself, I would imagine that LabVIEW would automatically dig through those files and find all the dependencies.

I'm using Labview 2012, and the DLL is written in C#.