This might be impossible or at least very hard. The DLL’s contents don’t depend (a lot) on it being written in C++; it’s all machine code. That code might have been optimized so a lot of information that was present in the original source code is simply gone. That said, here is one article that … Read more
You cannot get the exact code, but you can get a decompiled version of it. The most popular (and best) tool is Reflector, but there are also other .Net decompilers (such as Dis#). You can also decompile the IL using ILDASM, which comes bundled with the .Net Framework SDK Tools.
I’m currently on Windows 10 build 1809, and depends.exe hangs for every dll I try it with. The depends home page says “Dependency Walker runs on Windows 95, 98, Me, NT, 2000, XP, 2003, Vista, 7, and 8” so I guess it’s not supported. Try Dependencies – An open-source modern Dependency Walker, it works fine … Read more
You can only load a 32bit DLL into a 64 bit process when you are loading the dll as a datafile. You can’t execute the code. (http://support.microsoft.com/kb/282423) Microsoft recommends that you use interprocess COM to use 32 bit code with a 64 bit application. Here’s an article explaining the process.
I’ve achieved the same results using the GAC in the past, but you should question your reasons for having to reference more than one version and try to avoid it if possible. If you must do it, a binding redirect may help in your case. Also, have you read this yet?
I’ve copied and pasted this from my own post on it: The format of a .NET dll is: PE header CLR header CLR metadata CLR IL code Native data PE header The PE header is the portable executable header that all Win32 applications and libraries have, and instructs Windows what to do with the file. … Read more
Naming the output file libjvm.dll.a will allow gcc to recognize it as a library named jvm. The .dll.a suffix indicates (by convention) that it is an import library, rather than a static library (which would simply be named libjvm.a, again by convention).
Throwing C++ exceptions across DLL boundaries is only possible when all modules use the same C++ runtime, in which case they share a heap as well. But this can be a maintenance burden, especially when libraries from multiple vendors are involved, so it is discouraged. If you want error-handling which is portable across multiple compilers/compiler … Read more
Did you try something like this: <dependency> <groupId>com.foo</groupId> <artifactId>footron</artifactId> <version>4.2</version> <scope>runtime</scope> <type>dll</type> </dependency> You can add them to maven’s repository with something like this: mvn install:install-file -Dfile=footron.dll -DgroupId=com.foo -DartifactId=footron -Dversion=4.2 -Dpackaging=dll -DgeneratePom=true Haven’t done this for DLLs but something like this should work.
No, a 64-bit process can only load 64-bit DLLs and a 32-bit process can only load 32-bit DLLs. What you’re probably thinking of is that a 64-bit operating system can run 32-bit processes. The main issue with .NET is that – prior to VS2010 – executable projects defaulted to “AnyCPU” which means it would load … Read more