dll

问题 Some of you might know why I get these errors, I am scripting in c++ at the moment and I can't figure out why I get these. argument of type "const wchar_t *" is incompatible with parameter of type "LPCSTR" argument of type "wchar_t *" is incompatible with parameter of type "LPSTR" 'int MessageBoxA(HWND,LPCSTR,LPCSTR,UINT)': cannot convert argument 2 from 'const wchar_t *' to 'LPCSTR' 'DWORD GetModuleFileNameA(HMODULE,LPSTR,DWORD)': cannot convert argument 2 from 'wchar_t [260]' to 'LPSTR' I

问题 I've written a C++ console application in Visual Studio 2019 and am trying to deploy it to another windows laptop. Both laptops are up-to-date with 64 bit Windows 10, and my target laptop has installed/up-to-date .NET Framework, vc_redist.x64.exe, and DirectX. In terms of deployment method, I followed this Microsoft walkthrough word for word, with the added step of ensuring that my newly created "setup" project was also targeting x64 platform, since some of the external libraries in my code

问题 I am having a dll and which I am opening into the dependency walker with platform visual studio 2003 and OS is 2000. and my that dll find all dependency. But when I am going to open that dll in to tha another system which is having OS- windows7 and visual studio 2010, I found missing dlls errors. GDIPLUS.DLL, GPSVC.DLL, IESHIMS.DLL. above listed 3 dll were missing. when I have downloded those dlls and put them into the same location where my dll is residing, I am finding below listed missing

问题 Ok, so I can use dumpbin.exe /exports library.dll to find all methods in the dll. ...but how do I find out which arguments to pass into them? Without a header file of course. 回答1: For the usual C-style exports (e.g., Windows API DLLs): You can't. This information is not stored in the DLL and is inevitably lost after compilation (unless you have the headers or debuging symbols). C++ exports, on the other hand, store their signature as part of the mangled function name and you can view them

问题 Ok, so I can use dumpbin.exe /exports library.dll to find all methods in the dll. ...but how do I find out which arguments to pass into them? Without a header file of course. 回答1: For the usual C-style exports (e.g., Windows API DLLs): You can't. This information is not stored in the DLL and is inevitably lost after compilation (unless you have the headers or debuging symbols). C++ exports, on the other hand, store their signature as part of the mangled function name and you can view them

问题 Good morning. I'm trying to learn about DLL injection, so I've wrote a little software, that just gets a String, compares with StrCmp() and if the input was equal "Winner", the software gives a Good boy message, with the porpouse of learn DLL injection. So I write a DLL that loads a Form when inject, the porpouse is using the DLL injection, to modify the Instruction of comparison( JNZ(74) to JMP(EB)), and make the software, accept any string. My DLL code is: library Project2; uses SysUtils,

问题 I have to retrieve values under details tab e.g, File version, Product Version for .dll and .exe files through C#. I'm using the following code for this. FileVersionInfo myFile = FileVersionInfo.GetVersionInfo('Name of the file'); //File Version string fileVersion = myFile.FileVersion; The issue with this code is that it gives incorrect file version for some files. Details tab of these files shows different file version and code retrieves incorrect value. I'm not sure why this is happening.

问题 I have succeeded compiling POCO libraries with MinGW64 (MSYS2). To build it, I installed Windows SDK and added to the PATH environment the path to mc.exe , so I executed: pacman -S mingw-w64-x86_64-cmake # Get POCO git clone -b master https://github.com/pocoproject/poco.git # set Windows SDK to the PATH export PATH="/c/Program Files (x86)/Windows Kits/10/bin/10.0.18362.0/x64:$PATH" # Prepare compilation cd poco /mingw64/bin/cmake -G "MSYS Makefiles" .. # Compile make The compilation succeeded

问题 How would I prevent an import lib from loading the DLL it refers to at runtime until I call something like, say, LoadLibrary ? 回答1: Maybe you need this: http://www.west-wind.com/weblog/posts/2007/Dec/02/Delay-Loading-a-DLL-with-a-Linker-Switch-in-Visual-Studio http://www.codeproject.com/Articles/273419/Dynamic-Libraries-with-Delayed-Function-Loading 来源： https://stackoverflow.com/questions/12685664/prevent-lib-from-loading-dll-at-runtime

问题 I am relative new in c# and I want to use this uDMX API, but when I try to add the uDMX.dll file I get this error: "The reference is not vaild or not supported" (see screenshot (in german)) - I can't add images yet - Or am I doing it completely wrong? I did not find another uDMX api or .dll file. Hope for your help and Ideas. 回答1: You cant import an unmanaged win32 dll into a managed c# application like that, you need to specify the methods and parameters yourself. The uDMX api exposes these