For more information, see Visual Studio projects - C++. This may seem obvious, but if a calling app finds and loads a different copy of the DLL, the debugger will never hit the breakpoints you set. Make sure to call the DLL in its correct location. You can create a custom build task to copy the DLL files to your \Debug output folder, or you can copy the files there manually. pdb file and any other files the DLL requires. To debug a DLL, a calling app must be able to find its. Make sure to build a Debug version of the DLL before you start debugging.
#How to read dll files full
Under Linker > Input > Additional Dependencies, specify the full path and filename for the LIB files.įor more information on C++ project settings, see Windows C++ property page reference. Under Linker > General > Additional Libraries Directories, specify the folder that has LIB files. Under C/C++ > General > Additional Include Directories, specify the folder that has header files. Select the C/C++ DLL project in Solution Explorer and select the Properties icon, or right-click the project and select Properties.Īt the top of the Properties pane, under Configuration, select All Configurations. To set C/C++ header and LIB file locations:
You can create a custom build task to copy these files to your \Debug output folder, or you can copy the files there manually.įor C/C++ projects, you can set header and LIB file locations in the project property pages, instead of copying them to the output folder. pdb file, and any other files the DLL requires.
To debug an external DLL, a calling project must be able to find the DLL, its. In the Properties pane, under Linker > Debugging, select Yes (/ASSEMBLYDEBUG) for Debuggable Assembly.įor more information, see /ASSEMBLYDEBUG. Select the C++ DLL project in Solution Explorer and select the Properties icon, or right-click the project and select Properties.