I had this issue and I solved it with this thread disable incremental linking, by going to Project Properties -> Configuration Properties -> Linker (General) -> Enable Incremental Linking -> “No (/INCREMENTAL:NO)”
Use this method around (a) header(s) that you cannot or don’t want to change, but which you need to include. You can selectively, and temporarily disable all warnings like this: #pragma warning(push, 0) // Some include(s) with unfixable warnings #pragma warning(pop) Instead of 0 you can optionally pass in the warning number to disable, so … Read more
I just stumbled onto this issue accessing some Python libraries: Microsoft Visual C++ 14.0 is required. Get it with “Microsoft Visual C++ Build Tools”. The latest link to that is actually here: https://visualstudio.microsoft.com/downloads/#build-tools-for-visual-studio-2019 When you begin the installer, it will have several “options” enabled which will balloon the install size to 5gb. If you have … Read more
For this specific case, the fix is quite simple: wchar_t szBuff[64]; swprintf(szBuff, L”%p”, m_hWnd); MessageBox(NULL, szBuff, L”Test print handler”, MB_OK); That is, use Unicode strings throughout. In general, when programming on Windows, using wchar_t and UTF-16 is probably the simplest. It depends on how much interaction with other systems you have to do, of course. … Read more
The coded task can be put right at the project file since MSBuild v4.0. Like this: <UsingTask TaskName=”SetEnvironmentVariableTask” TaskFactory=”CodeTaskFactory” AssemblyFile=”$(MSBuildToolsPath)\Microsoft.Build.Tasks.v$(MSBuildToolsVersion).dll”> <ParameterGroup> <Name ParameterType=”System.String” Required=”true” /> <Value ParameterType=”System.String” Required=”true” /> </ParameterGroup> <Task> <Using Namespace=”System” /> <Code Type=”Fragment” Language=”cs”> <![CDATA[ Environment.SetEnvironmentVariable(Name, Value); ]]> </Code> </Task> </UsingTask> Note that in MSBuild 14+, the AssemblyFile reference should be just: … Read more
The sole difference is that a console application always spawns a console if it isn’t started from one (or the console is actively suppressed on startup). A windows application, on the other hand, does not spawn a console. It can still attach to an existant console or create a new one using AllocConsole. This makes … Read more
The core of the necessary code is StackWalk64. To get much from that, you’ll also want/need to get symbol names with SymGetSymFromAddr64 (which requires SymLoadModule64) and (probably) SymGetLineFromAddr64 and GetThreadContext. If the target was written in C++, you’ll probably also want to use UnDecorateSymbolName. Along with those you’ll need a few ancillaries like SymInitialize, SymCleanup, … Read more
The only thing you need to do to use resources (images, dialogs, etc…) in a static library in Visual C++ (2008), is include the static library’s associated .res file in your project. This can be done at “Project settings/Linker/Input/Additional dependencies”. With this solution, the resources of the static library are packed into the .exe, so … Read more
Try this MSDN page: Macros for Build Commands and Properties