Edit note: After a seemingly enourmous amount of bad feedback MS got from their customers regarding the drop-XP-stunt, they have announced that a patch will be released that'll allow to build executables for XP. So the base for this Q is no lonher really there, but I think it collects some very interesting infos.
As established here: What is special about the executables compiled with Visual Studio 11 which results in that the executables cannot be executed on Windows XP?
and in this Connect bug/issue: https://connect.microsoft.com/VisualStudio/feedback/details/690617, Visual Studio 11 (planned release 2012) is planned to no longer support Windows XP.
That means you cannot create a native C++ executable that can be executed on Windows XP. (One reason being that the new CRT will use Windows API calls that are only available on Windows Vista and higher.)
In one answer, Anders writes:
They seem to drop support for older systems in every new release of VS (NT4,2000,XP) ...
What interests me now is whether this move by Microsoft to drop Windows XP support completely from VS11 C++ can actually be compared to prior releases.
What I mean is, when was support for which OS (NT3.5 / NT4 / 2000sp6 // Win95 / Win98 / ...) completely dropped from Visual C++. (and "what part" of Visual C++ -- the compiler, the CRT, the Windows SDK?)
For example, I think I know that VC6 is the last version of VS that can be used to create executables that run on Windows NT