Interop problem
-
I am working on a winamp plugin in managed c++. i have another dll referenced in my project that i need to use (in C#). Everything compiles fine, however when the dll is loaded into winamp it throws a FileNotFoundException stating it can't load the C# dll. the dll is in the same directory as the c++/cli. what do i need to do to get the assembly detected? thanks in advance,
Don't be overcome by evil, but overcome evil with good
-
I am working on a winamp plugin in managed c++. i have another dll referenced in my project that i need to use (in C#). Everything compiles fine, however when the dll is loaded into winamp it throws a FileNotFoundException stating it can't load the C# dll. the dll is in the same directory as the c++/cli. what do i need to do to get the assembly detected? thanks in advance,
Don't be overcome by evil, but overcome evil with good
-
Could not load file or assembly 'Facebook, Version=1.6.2951.20499, Culture=neutral, PublicKeyToken=null' or one of its dependencies. The system cannot find the file specified.
Don't be overcome by evil, but overcome evil with good
teejayem wrote:
it can't load the C# dll. the dll is in the same directory as the c++/cli. what do i need to do to get the assembly detected?
teejayem wrote:
assembly 'Facebook, Version=1.6.2951.20499,
So the DLL is "Facebook.dll"? Does of the DLL match the one in the exception message?
teejayem wrote:
I am working on a winamp plugin in managed c++.
Is the winamp interface to your DLL a native C++ interface? If so then there is probably some way (configuration data) to tell winamp where your DLL is right? So when the .NET runtime is loaded into the Winamp process, the .NET runtime doesn't know anything about the Winamp configuration data that points to the folder with those DLL's. The .NET runtime is using the current working folder of the Winamp process to look for that assembly, plus of course however else it looks for assemblies, but it certainly won't look in a folder that is only known to the Winamp native code.
led mike
-
teejayem wrote:
it can't load the C# dll. the dll is in the same directory as the c++/cli. what do i need to do to get the assembly detected?
teejayem wrote:
assembly 'Facebook, Version=1.6.2951.20499,
So the DLL is "Facebook.dll"? Does of the DLL match the one in the exception message?
teejayem wrote:
I am working on a winamp plugin in managed c++.
Is the winamp interface to your DLL a native C++ interface? If so then there is probably some way (configuration data) to tell winamp where your DLL is right? So when the .NET runtime is loaded into the Winamp process, the .NET runtime doesn't know anything about the Winamp configuration data that points to the folder with those DLL's. The .NET runtime is using the current working folder of the Winamp process to look for that assembly, plus of course however else it looks for assemblies, but it certainly won't look in a folder that is only known to the Winamp native code.
led mike
yeah the facebook dll does match (version number and everything). you were right though, I put the facebook.dll in the directory where the executable lives (instead of the plugin directory where my plugin lives) and it worked perfectly! I always thought that the dependencies all had to be in the same folder (or else should be registered) and it had me totally messed up. thank you so much!
Don't be overcome by evil, but overcome evil with good