Visual Studio 2012 Update 1 Now Available!

Visual Studio 2012 Update 1 Now Available!

Rate This
  • Comments 50

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:

  1. In Solution Explorer, open the shortcut menu for your project, and then choose Properties.
  2. In the Property Pages dialog box for the project, under Configuration Properties, General, set the Platform Toolset property to Visual Studio 2012 – Windows XP (v110_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.

Leave a Comment
  • Please add 8 and 6 and type the answer here:
  • Post
  • If I change all 5 vcprojs (1.lib, 2.lib, 3.lib, 4.lib and b.exe) to use vc90 toolset, then b.exe runs on both win7 and XP, if I change back to vc110_xp again, the size of b.exe will grow 0.1MB bigger and only runs on win7

  • When you will release an update to fix hundreds of errors that has Visual Studio 2010? MFC errors, STL errors, Compiler errors, etc, ... Im write to support but I have not yet been answered! ¡many Errors!

    STL bugs list:

    MFC bugs list:

    Compiler bugs list:

    And that is only about C++!

  • Hi Trout.Z in project properties - Librarian tab, set minimum required version to 5.01

    Maybe the project toolset has no effect on librarian tab minimum required version like it does for EXEs and DLLs.

  • @Trout.Z are those all static libraries, or are they import libraries for DLLs? You can use dependency walker ( to check for linker versions on the DLLs.  If they are static libraries I can't reproduce the issue (even without setting the minimum required version as I mentioned before)

  • @Trout.Z Did @Mike's advice work for you?

    @Manuel Those posts are about bugs from Connect that were fixed. That is a good thing, right?

  • @Eric Battalio,

    Would be great if we have a tool in VS to convert the Win32 library (both static and dynamic) project to that of WinRT. I am trying to convert Tesseract-ocr ( for RT. But its dependencies; zlib, libpng, libjpeg, libtiff, giflib and leptonica ( are built in C and apparently nobody care much about C'11.

    Is there a way to convert those libraries for WinRT? Anyone with hands on experience on RT, please reply.

    Is there any free OCR library for WinRT?

  • @VS Performance Team,

    From the following discussion at SO, I presume that unlike Intel's compiler, VS doesn't optimized with the loop interchange technique

    Is there a plan to optimize the compiler with some heuristic algorithm to estimate if loop-interchange would make the difference in the given scenario (like Intel's compiler does)? I am very interested to learn your take on this matter.

  • Installing update 1 corrupted local help: "A content file required the help viewer missing or has been corrupted"

    How can we fix this? (there are similar reported in the past but only for the beta)

  • @stmarti There is a potential solution in the devdocs forum at It looks like it worked (it is marked as an answer by the parent). Did you want to give that a try?

  • The borking of "HELP local, non-default location", has been around since the first CTP.  Every updaet since it gets borked.  History.  Read up on it.  Learn.  Don't commit the same mistakes, over and over, and over and over.

  • @Nick

    Short answer: yes, but (naturally) I can't promise anything.

    Long answer:

    Native code performance is extremely important. Loop performance especially so. I work on the

    compiler team, though, so excuse my bias.

    In VS 2012 we implemented a data dependence framework to be able to do large-scale

    loop optimizations. In VS 2012, the optimizations based on that framework are the auto-vectorizer

    and auto-parallelizer. We know we can do a lot more: loop permutation, if-switching, etc, plus others

    that aren't in the SO thread. Plus improving the existing auto-vectorizer and auto-parallelizer.

    We're working on it.

  • How to use "Visual Studio 2012 – Windows XP (v110_xp)" in command line with nmake? for example, how to build OpenSSL using nmake with v110_xp toolset?

  • Is it possible to use the x86_amd64 compiler from within Visual Studio on a 64-bit machine?

    Normally it uses the native 64-bit CL.exe when installed on a 64-bit machine. However, I'm using IncrediBuild, which does not support virtualization of 64-bit processes atm, so I would want to use the x86_amd64 from my vcxproj, so I get the benefits from my IncrediBuild farm. Compiling on local node only can take over an hour.

    Obviously Xoreax should fix virtualization of 64-bit processes, but it *should* be doable to also use the x86_amd64 compiler with MSVC too, right?

  • What service pack of XP does the v110_xp toolset support?  Is it XP SP2+ like VS2010 or has it changed?

  • @Eric Brumer - MSFT,

    Thanks for the comprehensive -- yet wonderful reply. I am glad to know that VS team is eagerly working on all sorts of optimizations humanly possible to our inefficiently written code. 9-)

    Incidentally, can you guys please do a blog about list of optimizations VC 2012 compiler does and those which are not available at this point? Guess this kind of checklist would make things pretty much clear.

Page 2 of 4 (50 items) 1234