Quote from: James C. Fuller on November 17, 2013, 11:24:39 AM
If you use the _xp toolset setting do you still have the full C++11 constructs you have with Visual Studio 2013?

AFAIK, all that vs120_xp does is tell the compiler to use an older Windows SDK, but you would continue to use the VC12 compiler. However, because you're effectively using a modified version the Windows 7.0A SDK, you won't have access to Windows 8 APIs (although you could hack around that with dynamic linking). Remote debugging won't work correctly, and IIRC there's also some issues with trying to debug applications that use DX9.

Mike,
  I did find a way to use Visual Studio 2013 Express version to target XP. I had the Win7 SDK installed and just needed to tweak the paths from this blog.

http://blogs.msdn.com/b/vcblog/archive/2012/10/08/10357555.aspx

James

Argh!

Compiling the same source code with the same parameters on VS 2013 than VS 2010, produce not only larger code, but also code that doesn't behave the same!

Welcome to MSVC++ 

Quote from: Patrice Terrier on November 24, 2013, 08:30:55 PM
Compiling the same source code with the same parameters on VS 2013 than VS 2010, produce not only larger code, but also code that doesn't behave the same!

Are you using the vs120_xp toolset and setting the WINVER macro to 0x0501 so that your project can continue to target XP? Or are you using the Windows 8 SDK?