You can use the GetModuleHandleEx function and get the handle to a static function in your DLL. You’ll find more information here. After that you can use GetModuleFileName to get the path from the handle you just obtained. More information on that call is here. A complete example: char path[MAX_PATH]; HMODULE hm = NULL; if … Read more
the file is a native DLL which means you can’t add it to a .NET project via Add Reference… you can use it via DllImport (see http://msdn.microsoft.com/en-us/library/system.runtime.interopservices.dllimportattribute.aspx)
As you’ve noted, DYLD_LIBRARY_PATH behaves like LD_LIBRARY_PATH on other *nix. However, there is another environment variable you should look at called DYLD_FALLBACK_LIBRARY_PATH. In general, these are (both on osx and linux) suggested only for development use as they can cause symbol lookup errors when you override with a library that does not have the same … Read more
There is no way to directly use a C++ class in C# code. You can use PInvoke in an indirect fashion to access your type. The basic pattern is that for every member function in class Foo, create an associated non-member function which calls into the member function. class Foo { public: int Bar(); }; … Read more
Does your DLL project have any actual exports? If there are no exports, the linker will not generate an import library .lib file. In the non-Express version of VS, the import libray name is specfied in the project settings here: Configuration Properties/Linker/Advanced/Import Library I assume it’s the same in Express (if it even provides the … Read more
I found the solution by using this answer to a similar question You create 2 folders in your project one for each version of log4net. Place each log4net.dll in its corresponding folder by adding an the file to the solution (not with add reference). You can set the copy to output directory property to copy … Read more
Like the others say, this is a .NET behavior. Assemblies loaded into an AppDomain cannot be unloaded. Only the AppDomain can be unloaded, and powershell uses a single appdomain. I blogged a bit about this some years ago: https://web.archive.org/web/20170707034334/http://www.nivot.org/blog/post/2007/12/07/WhyAppDomainsAreNotAMagicBullet When I test like this, I usually keep a shell open and use a nested shell … Read more
As everyone else says, LoadLibrary is the hard way to do it, and is hardly ever necessary. The DLL should have come with a .lib file for linking, and one or more header files to #include into your sources. The header files will define the classes and function prototypes that you can use from the … Read more
dumpbin is a tool that comes with VC++. To see what DLLs a program will import: Open Visual Studio Menu Item Tools | Visual Studio Command prompt cd to folder containing executable dumpbin /dependents whatever.exe Dump of file whatever.exe File Type: EXECUTABLE IMAGE Image has the following dependencies: AIOUSB.DLL sqlite3.dll wxmsw293u_core_vc_custom.dll wxbase293u_vc_custom.dll KERNEL32.dll ole32.dll OLEAUT32.dll … Read more
In my case the problem occurred in a virtual application’s bin folder. Looking into this bin-folder you will probably see two files (an information I found here): App_global.asax.dll App_global.asax.compiled Removing these resolves the error. The App_global.asax.dll is generated at runtime too which causes the problem. I am however still investigating how these files got there, … Read more