6 ms·

Developers beware: Visual C++ 11 cannot compile executables that work on Windows XP at all: https://connect.microsoft.com/VisualStudio/feedback/details/690617/

Developers beware: Visual C++ 11 cannot compile executables that work on Windows XP at all: https://connect.microsoft.com/VisualStudio/feedback/details/690617/bug-apps-created-with-crt-and-mfc-vnext-11-cannot-be-used-on-windows-xp-sp3 https://connect.microsoft.com/VisualStudio/feedback/details/... C++ devs may want to skip this release and just go for Visual C++ 12 when it's out, since by then hopefully XP will be ignorable.

RandallBrown 15y ago
I'm afraid XP won't be ignorable for another 3 or 4 years at least.
- AshleysBrain 15y ago
  According to: http://gs.statcounter.com/#os-ww-monthly-201101-201201 http://gs.statcounter.com/#os-ww-monthly-201101-201201 XP dropped 14% in the last year, and is now on 34%. So a really dumb calculation says about 2 and a half years if that keeps up, but I guess there will be a longer tail of die-hard users... hard to tell, since it's pretty unprecedented for a particular version of a major OS to be so popular for so long.
  - marshray 15y ago
    So I guess in 2 or 3 years not supporting XP will only cost you 50 to 100 million potential users.
- dmethvin 15y ago
  Microsoft stops providing XP security patches in April 2014. Any organization that wants to use XP after that will need to pay Microsoft to maintain support. Any organization that continues to use XP without support is irresponsible.
  - yuhong 15y ago
    Yea, it is called a Custom Support agreement. Costs $50,000 per quarter for first year and increases every year, BTW.
huhtenberg 15y ago
> Status: Closed as "By Design"
marshray 15y ago
OMG that's insane. Well, our Windows builds may just have to move from 2005 to 2010 and plan to be stuck there for the forseeable future. I was hoping I could use a C++11 compiler for Windows development someday. But it's probably more likely that I'll stop developing for Windows before my company's customers stop running XP.
- jodrellblank 15y ago
  It is not "insane", XP is three years past the end of official support and only two years until the end of extended support. It's two generations old and possibly three by the time this is released. http://windows.microsoft.com/en-us/windows/products/lifecycle http://windows.microsoft.com/en-us/windows/products/lifecycl... XP doesn't run IE9 either, and it came out ages ago. XP is old now.
  - marshray 15y ago
    > XP is three years past the end of official support and only two years until the end of extended support I don't think I've ever met anyone who managed fewer than 25 servers who has ever looked that that calendar.
  - 16s 15y ago
    I know you mean to point out how old and crufty XP is (and that is true), but if you stop and think about it... it's really a testament to C++ and Microsoft engineering that it has done so well for so long.
    - marshray 15y ago
      Well that, and * the long gap between XP and Vista * that it was still selling on new netbooks until quite recently, and * the leveling off of CPU performance.
  - forgotAgain 15y ago
    I'll go out on a limb here and predict that XP extended support will itself be extended. There are simply too many desktops out there using it to be ignored.
duuude 15y ago
Some people might consider that a feature.
acqq 15y ago
As "Mike" commented there: "One big thing that works against us having any sort of nice workaround for this, is the fact that as of Visual C++ 2010, the CRT and MFC rebuild makefiles are no longer included with the source code. In 2008 and earlier, it was so easy to rebuild CRT and MFC DLLs because there was a clear set of makefiles included. Now all there is, is a silly "these are the compiler and linker switches we use, go find your own solution to rebuild these" web page." It's also not something that would take them work to do, as the older library versions already implemented the code paths needed for Windows 2000 and XP. I suspect MS wants the support for older OS-es banned to make new apps unrunable on Wine too.

RandallBrown 15y ago

I'm afraid XP won't be ignorable for another 3 or 4 years at least.

AshleysBrain 15y ago
According to: http://gs.statcounter.com/#os-ww-monthly-201101-201201 http://gs.statcounter.com/#os-ww-monthly-201101-201201 XP dropped 14% in the last year, and is now on 34%. So a really dumb calculation says about 2 and a half years if that keeps up, but I guess there will be a longer tail of die-hard users... hard to tell, since it's pretty unprecedented for a particular version of a major OS to be so popular for so long.
- marshray 15y ago
  So I guess in 2 or 3 years not supporting XP will only cost you 50 to 100 million potential users.
dmethvin 15y ago
Microsoft stops providing XP security patches in April 2014. Any organization that wants to use XP after that will need to pay Microsoft to maintain support. Any organization that continues to use XP without support is irresponsible.
- yuhong 15y ago
  Yea, it is called a Custom Support agreement. Costs $50,000 per quarter for first year and increases every year, BTW.

huhtenberg 15y ago

> Status: Closed as "By Design"

marshray 15y ago

OMG that's insane. Well, our Windows builds may just have to move from 2005 to 2010 and plan to be stuck there for the forseeable future. I was hoping I could use a C++11 compiler for Windows development someday. But it's probably more likely that I'll stop developing for Windows before my company's customers stop running XP.

jodrellblank 15y ago
It is not "insane", XP is three years past the end of official support and only two years until the end of extended support. It's two generations old and possibly three by the time this is released. http://windows.microsoft.com/en-us/windows/products/lifecycle http://windows.microsoft.com/en-us/windows/products/lifecycl... XP doesn't run IE9 either, and it came out ages ago. XP is old now.
- marshray 15y ago
  > XP is three years past the end of official support and only two years until the end of extended support I don't think I've ever met anyone who managed fewer than 25 servers who has ever looked that that calendar.
- 16s 15y ago
  I know you mean to point out how old and crufty XP is (and that is true), but if you stop and think about it... it's really a testament to C++ and Microsoft engineering that it has done so well for so long.
  - marshray 15y ago
    Well that, and * the long gap between XP and Vista * that it was still selling on new netbooks until quite recently, and * the leveling off of CPU performance.
- forgotAgain 15y ago
  I'll go out on a limb here and predict that XP extended support will itself be extended. There are simply too many desktops out there using it to be ignored.

duuude 15y ago

Some people might consider that a feature.

acqq 15y ago

As "Mike" commented there: "One big thing that works against us having any sort of nice workaround for this, is the fact that as of Visual C++ 2010, the CRT and MFC rebuild makefiles are no longer included with the source code. In 2008 and earlier, it was so easy to rebuild CRT and MFC DLLs because there was a clear set of makefiles included. Now all there is, is a silly "these are the compiler and linker switches we use, go find your own solution to rebuild these" web page." It's also not something that would take them work to do, as the older library versions already implemented the code paths needed for Windows 2000 and XP. I suspect MS wants the support for older OS-es banned to make new apps unrunable on Wine too.