http://tedwvc.wordpress.com/2010/11/07/how-to-get-visual-c-2...
There is an in-depth overview of all the things MSFT have removed to prevent the compiled executables from running on Windows 2000. These things still existed in VS 2008, it's not that they had to develop them.
Me: "Executables made with Visual Studio 2010 run on Windows XP SP3."
You: post the link to the article titled "Executables built with Visual C++ 2010 do not run on Windows XP prior to SP2"
Note the SP numbers and the word "prior" please. Anyway, I know what I write since I have to support Windows 2000 for the projects I'm involved and I have to use Visual Studio 2008 for that. Do you compile any native executables for Windows platforms?
Regardless, "No, executables made with Visual Studio 2010 run on Windows XP SP3. They don't run on Windows 2000" and "No, executables made with Visual Studio 2010 run on Windows XP SP3. They don't run on Windows XP SP2" are entirely different statements.
This is such a bone-headed move I can't believe where that came from. They can't be out of touch that much. I guess people with existing code bases don't have any options anyway, so they though this would be a nice 'incentive' for vendors to pester users into upgrading to new Windows versions.
Very disappointing.
"This behavior is by design in MFC and CRT for Visual Studio vNext. The minimum supported operating systems are Windows Server 2008 SP2 and Windows Vista. Windows XP is not a supported operating system for the release (design-time or run-time)."
source: https://connect.microsoft.com/VisualStudio/feedback/details/... taken from: http://stackoverflow.com/questions/7702463/what-is-special-a...
http://www.worldometers.info/computers/
and there should be 2 billions in 2015, let's assume there's at least 1.4 billion PC's at the moment now. Even if XP has just 25% percent of that, it's 350 million of PC's in the world on which the executable built with VS 11 can't work.
Yes I believe you're right when you say: "new development paradigms and practices they want to get rid of" even if it is a Freudian slip.
Assuming it's the same, then adding this ASM file to your project should solve the problem:
https://github.com/NeoSmart/UtfRedirect/blob/master/UtfRedir...