Today, Soma announced the availability of the Visual Studio 2012 Update 1! You can install it either from the download page (see "Visual Studio 2012 Update 1" under the "Additional software" section).
As promised, you can now use the Visual C++ compiler and libraries to target Windows XP and Windows Server 2003. To target Windows XP:
As always, we'd love to hear your feedback. Please submit suggestions to Visual Studio UserVoice. You can also follow us on Twitter (@VisualC) and like us on Facebook (Visual CPP) and post to our wall.
Is there a list of bug fixes to the C++ compiler in Update 1? Has native C++ compiler performance improved? I can't seem to find a detailed list in any of the announcements.
Thanks for XP support. Are you guys looking at the MFC requests on User Voice for Update 2?
Is this relevant to C++ November CTP?
I'm afraid that the C++ November CTP features are not available in this "Update 1". So, nothing new about C++11 in this Update 1? *sad*
Why is it only 1 MB? Where is the full download?
Nothing shows up in "Extensions and Updates"
Oooh, nice. That means upgrading is now actually a somewhat viable option. Of course, because you yanked the command-line compilers out of the Windows SDK, there are still a lot of headaches in upgrading our build server, but this is one obstacle out of the way, at least.
Thanks for listening. :)
Really surprised there's no list of fixes. I see comments that lots of fixes were made, but what specifically for c++ desktop development?
Great job on listening to your customers and providing XP support.
Any idea of when we can expect to see the C++11 ctp as an update. The XP support was announced October 8th. The CTP was announced Nov 2. Should we expect the update in about 3-4 weeks?
Thank you very much for making this possible. We are anxious to migrate to VS 2012.
Indeed, many thanks for listening. We have a forward path. Now for our bit persuadinb our (and your) customers to let go of XP.
To get full download for offline installation - use the /Layout command line option - for more info see:
A few answers.
>>> Is there a list of bug fixes to the C++ compiler in Update 1?
Bug fixes centered on the Visual Studio experience, ARM code generation, and a fix to a race condition in ppltasks.h that caused intermittent crashes in async operations authored with PPL.
>>> Has native C++ compiler performance improved?
If you want to target XP, it is a big improvement :)
>>> Are you guys looking at the MFC requests on User Voice for Update 2?
We do consider customer requests but cannot make any promises.
>>> Is this update relevant to C++11 November CTP?
>>> Any idea of when we can expect to see the C++11 ctp as an update?
At the Build conference, Herb Sutter in his “Future of C++” session (channel9.msdn.com/.../2-005) said more announcements would be forthcoming in the first half of calendar 2013. Waiting is the hardest part :)
Was the native 64bit compiler supposed to be updated as part of this? The cl.exe in bin\amd64\ is dated July 26th with a version of 17.0.50727.1, while the cl.exe's in bin\, bin\x86_arm\ and bin\x86_amd64\ are dated November 6th with a version of 17.0.51106.1.
I've got a solution with 1.lib, 2.lib, a.exe, b.exe， a.exe only depends on 1.lib and link to it. b.exe link to 1.lib, 2.lib ,and some other 3.lib, 4.lib
I've tried with newly released update1, utilizing v110_xp toolset, both a.exe and b.exe can run on win 7, but on only a.exe can run on XP. b.exe reported not a valid win32 app.
I just wonder, if there is a way to identify which lib I linked to is causing this? I've made sure that the vcproj generating 1.lib, 2.lib, 3.lib, 4.lib and b.exe are all using v110_xp toolset