There are many ways to do this but I think one of the easiest options is to link the application to the DLL at link time and then use a definition file to define the symbols to be exported from the DLL. CAVEAT: The definition file approach works bests for undecorated symbol names. If you … Read more
In a Windows C++ DLL, all global objects (including static members of classes) will be constructed just before the calling of the DllMain with DLL_PROCESS_ATTACH, and they will be destroyed just after the call of the DllMain with DLL_PROCESS_DETACH. Now, you must consider three problems: 0 – Of course, global non-const objects are evil (but … Read more
A “static” solution (in the sense it can capture a stack trace on demand) would be Process Monitor. A more dynamic solution would be ApiMonitor, but it may be too old to be compatible with the applications to monitor. Worth a try though.
__declspec(dllimport) is a client-side MSVC attribute that can be specified for imported code and data. It isn’t required for code. It is an optimization; a client-side compiler hint that a function call isn’t direct but imported. The imported function pointer for a function named foo() will be __imp_foo. Without the hint, a thunk is created … Read more
The basics are simple. Windows has a search path for DLLs, much the same way it has a $PATH for finding executables. If you can figure out what DLLs an app requests without an absolute path (triggering this search process), you can then place your hostile DLL somewhere higher up the search path so it’ll … Read more
This is a known bug in Windows Azure VS Tools Workarounds: Remove Newtonsoft.Json.dll file from Program Files\Microsoft SDKs\Windows Azure.NET SDK\v2.3\ref\ folder. Uninstall Windows Azure VS Tools v 2.3
or one of its dependencies That’s the usual problem, you cannot see a missing unmanaged DLL with Fuslogvw.exe. Best thing to do is to run SysInternals’ ProcMon utility. You’ll see it searching for the DLL and not find it. Profile mode in Dependency Walker can show it too.
Simple way assuming class Foo: Create a C++/CLI project, call this FooWrapper. Make FooWrapper depend on the unmanaged dll (however you normally would). Create a managed class ManagedFoo which contains a single private instance field of type Foo*. provide public wrapping functions in ManagedFoo which forward on to the underlying instance field. Optionally (though recommended): … Read more
PDB files contain debug information and are useful if you need to step through the DLL’s code at any point. ILK files are used by the linker. They are not needed unless the DLL is to be recompiled. EXP files contain information about things exported from the DLL