DLLs that are used by an application should
automatically be included in the build. They should
optionally be renamed, when the hierachy is name-mangled.
I don't think name mangling private DLLs is such a good idea. In general private DLLs are distributed in the application directory itself and that makes sure they are used by that application eventhough there may be a different version of that same DLL in the system somewhere. And if other parts of your application might reference another DLL with the same name before the VIs get to load their own DLL you are in a huge DLL hell mess anyhow already. No name mangling can really help there and potentially make things only worse if those two DLLs are basically the same but with different versions or use global variables or other resources internally.
Either you have system global DLLs (that are already present on a potential target system or installed by a different installer) and then they shouldn't be included in the build at all, or the DLL is private and included in the build but then it can't collide with others without causing DLL hell.
Rolf Kalbermatter
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Logged In: YES
user_id=66382
Originator: NO
I don't think name mangling private DLLs is such a good idea. In general private DLLs are distributed in the application directory itself and that makes sure they are used by that application eventhough there may be a different version of that same DLL in the system somewhere. And if other parts of your application might reference another DLL with the same name before the VIs get to load their own DLL you are in a huge DLL hell mess anyhow already. No name mangling can really help there and potentially make things only worse if those two DLLs are basically the same but with different versions or use global variables or other resources internally.
Either you have system global DLLs (that are already present on a potential target system or installed by a different installer) and then they shouldn't be included in the build at all, or the DLL is private and included in the build but then it can't collide with others without causing DLL hell.
Rolf Kalbermatter