Search results
5 gru 2013 · DLL files might require other DLL files. In the same way that an application requires a DLL file, a DLL file might be dependent on other DLL files itself. If one of these DLL files in the chain of dependency is not found, the application will not load. This is debugged easily using any dependency walker tools, like Dependency Walker.
4 mar 2011 · The answer depends on what language the DLL was written in. If it was a .NET language then, as pointed out, you can use .NET Reflector. If it's the older Visual Basic (pre-.NET), then the DLL is compiled as what's called p-code and there are a few options for doing some variations on decompiling.
13 mar 2012 · You are correct in that static files are copied to the application at link-time, and that shared files are just verified at link time and loaded at runtime. The dlopen call is not only for shared objects, if the application wishes to do so at runtime on its behalf, otherwise the shared objects are loaded automatically when the application starts.
3 lip 2012 · There are static libraries (LIB) and dynamic libraries (DLL) - but note that .LIB files can be either static libraries (containing object files) or import libraries (containing symbols to allow the linker to link to a DLL). Libraries are used because you may have code that you want to use in many programs.
21 mar 2014 · If the ABI is not reflected in the version, perform a secondary md5sum against the files or perform a reflective compare of the two assemblies. The md5sum would of course "catch" internal/compilation changes even if the ABI didn't change. Reflecting the ABI, while more complicated and potentially dog-slow, could determine ABI changes spot-on.
29 maj 2015 · For .dlls written in .NET, check [SO]: How to decompile a .dll file created in VS.net. Most likely it was written in C. The tools I listed can tell you more. You can also look with a text viewer at the .dll, inside it there might be references to source files (among all those unreadable symbols)
However, since .dll files are by definition just archive library files, the DLL file itself should be readable and not a compiled C or C# file, etc., etc. Basically, .dll files are archives. Well, they should be when a .dll file is created in Visual Studio. The DLL file is created and any information you store in the DLL file file is encrypted.
14 wrz 2009 · For me, it was trying to find a DLL in a path that used to contain the Project, but we'd moved it to a new directory. The Solution had the correct path to the Project, but Visual Studio somehow kept looking in the old location.
28 sty 2009 · DLL (dynamic link library) files can be described as small "sub-programs" which are meant to help a bigger program run well. They provide a means of linking various hardware and software resources (at various points in its run-time sessions) to the main executable program upon which they are based, on an "as-the-need-arises" basis.
31 paź 2008 · Building the DLL from the command line. To build a DLL with Visual Studio from the command line run "C:\Program Files (x86)\Microsoft Visual Studio 12.0\Common7\Tools\vsdevcmd" to set the include path and then run. cl.exe /D_USRDLL /D_WINDLL testDLL.cpp /MT /link /DLL /OUT:testDLL.dll to build the DLL. Building the DLL from the IDE
