It depends if you want to include the same dll that resides in a different path depending on the target resource, or whether you are trying to dynamically call one of many different dlls with different method signatures. (perhaps different versions of a dll)
The former, the best approach is to abstract the full path away from your VBO, by configuring the location of the DLL via the target systems %PATH% windows environment variable. Then in the code stage options place just the file name of the dll.
For the latter, (which can be done more easily if the dll is a COM dll), you could use the CreateObject() method, and call functions on the dll using late binding.
