is there any further info on releasing a pack somewhere?
all i can find is the info from the changelog of beta30 where it says:
added basic support for future packs:
add packs/PACKNAME/core to assembly search path
add packs/PACKNAME/factories to mef container catalog on startup
add packs/PACKNAME/nodes to node search path
now while vvvv finds plugins within packs/myPack/nodes/plugins it won’t find the native dll which these plugins call, which I have put into packs/myPack/core. When I copy my native dll next to vvvv.exe everything works fine (as expected), and funnily enough it works when i move my dll to dx11/core, which makes me believe now there’s something else which needs to be done to add packs/myPack/core to the search path?
first use vpm! yeah!
but more importantly if .NET library A is loaded already in a .NET application .NET library B which depends on A can use A without the need for copying the DLL’s around. So if your library depends on vux’s DX11 and that is already loaded from somewhere in vvvv you don’t have to include it in your own pack.
But you don’t have to include any dependencies in your pack if you manage the dependencies with vpm ;)
openvr_api.dll is a native c++ dll, so that piece of code does custom loading for native DLLs. i have also used it in the VVVV.Audio pack. you can use it until the new beta is out, then it can be removed if you don’t need backwards compatibility.