You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi there,
I am developing a Bonsai.Source package for a thirdparty camera, which provides several non-managed library files. It goes all well in Visual Studio both debug and release mode. And the thirdparty dll files are also autocopied to the bin output folder with MSBuild by adding items in csproj.
However, while i try to install the package in Bonsai.exe with package manager, it complains somthing about thrid party dll files missing assembly manifest, as follows,
Can you guys provide some suggestion about how to tackle such problem? Or any suggestion that the thirdparty dll can be auto-copied to the same folder as package's lib{framework} when installing from package manger?
The text was updated successfully, but these errors were encountered:
When I was trying to get third-party dlls working for Bonsai.SpikeGLX, I found that I had to both include them and add a post-build command to copy them into the target directory. I've directly copied the relevant lines from the .csproj below:
Hi there,
I am developing a Bonsai.Source package for a thirdparty camera, which provides several non-managed library files. It goes all well in Visual Studio both debug and release mode. And the thirdparty dll files are also autocopied to the bin output folder with MSBuild by adding items in csproj.
However, while i try to install the package in Bonsai.exe with package manager, it complains somthing about thrid party dll files missing assembly manifest, as follows,
Can you guys provide some suggestion about how to tackle such problem? Or any suggestion that the thirdparty dll can be auto-copied to the same folder as package's lib{framework} when installing from package manger?
The text was updated successfully, but these errors were encountered: