If you want plain C exports, use a C project not C++. C++ DLLs rely on name-mangling for all the C++isms (namespaces etc…). You can compile your code as C by going into your project settings under C/C++->Advanced, there is an option “Compile As” which corresponds to the compiler switches /TP and /TC. If you … Read more
I think the answer to your question is mostly historical, if you look back at how the two libraries originated and evolved through time. The short answer is, if you are not doing anything “fancy”, use ATL. It’s great for simple user interfaces with COM thrown in. The long answer: MFC was built in the … Read more
Use a post-build action in your project, and add the commands to copy the offending DLL. The post-build action are written as a batch script. The output directory can be referenced as $(OutDir). The project directory is available as $(ProjDir). Try to use relative pathes where applicable, so that you can copy or move your … Read more
It depends on what version you are using. These two 2012 keys have worked well for me with their corresponding versions to download for Update 4. Please be aware that some of these reg locations may be OS-dependent. I collected this info from a Windows 10 x64 box. I’m just going to go ahead and … Read more
In Visual Studio 2013 and later there is a default keyboard shortcut for this: Ctrl+K, Ctrl+O (You will need to hold down Ctrl and type ko and then release Ctrl) In earlier versions, see: Visual Studio Macro to switch between CPP and H files or Open Corresponding File in Visual Assist
To answer the first part of your question: LPCSTR is a pointer to a const string (LP means Long Pointer) LPCTSTR is a pointer to a const TCHAR string, (TCHAR being either a wide char or char depending on whether UNICODE is defined in your project) LPTSTR is a pointer to a (non-const) TCHAR string … Read more
This particular issue is caused by specifying a dependency to a lib file that had spaces in its path. The path needs to be surrounded by quotes for the project to compile correctly. On the Configuration Properties -> Linker -> Input tab of the project’s properties, there is an Additional Dependencies property. This issue was … Read more
Add the following as a additional linker option: /ignore:4099 This is in Properties->Linker->Command Line
There are several approaches: You can normally see assembly code while debugging C++ in visual studio (and eclipse too). For this in Visual Studio put a breakpoint on code in question and when debugger hits it rigth click and find “Go To Assembly” ( or press CTRL+ALT+D ) Second approach is to generate assembly listings … Read more
Use #include <windows.h> instead of #include <windef.h>. From the windows.h wikipedia page: There are a number of child header files that are automatically included with windows.h. Many of these files cannot simply be included by themselves (they are not self-contained), because of dependencies. windef.h is one of the files automatically included with windows.h.