Our goal is to get rid of all of this red before it will run correctly on XP.Īn aside: If it were truly a technical limitation to drop XP, then it would be impossible for us to “wrap” every instance of these functions without touching the original CRT and/or MFC static lib source code. To summarize, if we run dependency walker (available from on a built executable that uses CRT and/or MFC 11 on Windows XP SP3, we’ll see a bunch of “red” icons beside the functions that are missing on XP (mostly in kernel32.dll). This means we do not have to use /FORCE:MULTIPLE. If we use this trick we can substitute our own versions of any API symbol that is linked into our app, without causing any multiple symbol errors in the linker. This involves making a small assembly language forwarding directive that calls our own C++ wrapper function. In that article I explained that there is a simple trick that we can use to “wrap” missing API functions. If you’re a long time reader of my blog, you know that I have written another article in the past on how to target Windows 2000 when using Visual Studio 2010. What I need is the ability to use VC 11 (and all of its powerful new language features) AND still be able to target XP as a platform to deploy my apps to. Whether the Visual Studio 11 tools run on XP is a whole other story. So this leaves out XP and Server 2003.Īs you can see from the comments, many users simply will not adopt VC 11 because of its lack of XP targeting support. Note that the connect item was closed as “by design” and it was stated that only Vista SP2 and above is supported. As most of you already know, there is a connect item at Microsoft on this. One of the major limitations of Visual C++ 2012 is that it does not create applications that can run on Windows XP.
Source files and sample projects for this article located at:
In the meantime you can use the below as a temporary workaround until the update has been released. Please use the official Microsoft solution from now on.ĮDIT (June 20, 2012): Microsoft has announced XP targeting support will be added to Visual C++ 2012 in a post-RTM update.
EDIT (April 14, 2013): If you’re having trouble with Microsoft’s XP support after installing Visual Studio 2012 Update 2 then please ignore this blog post! Read the new blog post instead.ĮDIT (November 26, 2012): Microsoft has made their final release of Visual Studio 2012 Update 1 available which includes official XP targeting support!ĮDIT (October 14, 2012): Microsoft has released their CTP of the XP targeting support, negating any further need for these wrappers.
0 kommentar(er)
