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.

  • @Mike @Eric Battalio

    Sorry for the late reply, I was on a trip to Siggraph Asia 2012.

    I've just specify the "5.01" to all the 4 libs my exe is linked to, still no luck. They are all static libs, not those used for dll import.  By using depends.exe,  I can see that my a.exe has LinkerVer 11.0, OSVer 5.1, SubsystemVer 5.1, while my b.exe has LinkerVer 11.0, OSVer 6.0, SubsystemVer 6.0.

    Is there a way to know which lib is causing this kind of issue? I used "dumpbin /headers", it has no version info displayed for libs as for exes.

  • @Mike @Eric Battalio

    Update:

    I've managed to solve this by changing b.exe 's SubSystem property from " "(blank) to "Windows" according to that of a.exe. AND there is really NO difference whether or not I specify 5.01 for the lib projs.

    I've tried to specify different version for a.exe, each time it responds: for "5.02" the OSVer changed to 5.2 in depends; for "4.02" there is a LNK4010 saying, "invalid subsystem version number 4.02; default subsystem version assumed" and it's 6.0 in depends.

    While when I did the same to b.exe, it neither changes OSver nor show LNK4010, always show 6.0 in depends, making me feel that the MinimumRequiredVersion property is somehow ignored. Then I compared their System tab, and  found the solution above.

  • Hi,

    I'm making a dialog base "test.exe" using VS2012 pattform v110_xp. I can compile and generate the exe file, but when a try to execute "test.exe" over a windows XP PC appears the next message: "The procedure entry point ApplicationRecoveryFinished could not be located in the dynamic link library KERNEL32.dll" and If I try execute the same test.exe over W7 It's working...  Could someone help me?

  • I'd also like to know what Michael asked:

    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.

  • @Trout.Z interesting, that's the second time I've heard about users having problems with a blank subsystem version.  I guess the problematic project setting pre-existed before updating, but it didn't matter before until now.

  • @Noemi are you sure you don't have any old stuff in there, like old copies of appcore.cpp, etc in your project.   The new one is calling _AfxApplicationRecoveryFinished.  You should also check for static libs that haven't been rebuilt.  Do a find for ApplicationRecoveryFinished in all files.

  • @Mike,  @Trout.Z

    Please report this issue on Microsoft Connect and send us the link so we can vote. It happens quite a few times (not always). But if you guys know the exact steps of reproduction, please do submit the bug report.

  • So is Update 1 compatible with the Nov CTP? I.e. you can install VS2012, then Nov CTP, then Update 1 and be ok?

  • how to use v110_xp toolset in command line(NMake.exe)?

  • Hi everyone

    If anyone wants to install the 'Visual Studio 2012 Update 1':

    blogs.msdn.com/.../visual-studio-2012-update-1-now-available.aspx

    Plz remember that it MUST be installed BEFORE install the 'C++ November CTP' version. Otherwise the installation of Upd1 will encounter problems and the application made from your project won't running under the Windows XP even if you choiced the vc110_xp as the compiler for your project.

  • @Jennifer @Mike @Eric Battalio

    It's here  :  connect.microsoft.com/.../visual-studio-2012-update-1s-xp-targeting-not-work-for-project-with-blank-subsystem-property

  • Please vote for the support of C99, C11 and C++98 missing libraries in Visual Studio 2012:

    connect.microsoft.com/.../decades-old-missing-c99-headers-ever-coming-to-vs-stack

  • Cudos for Nice work!

    I can't seem to get delegating constructors to work (c++11). Was not "delegating constructors" added?

    I downloaded/installed  VS2012 Desktop Express and Update1 and tried delegating constructors but it doesn't like it much...

  • Is just me or the print of a char address with std::cout is buggy?

    try this code for example:

    #include <iostream>

    #include <cstdlib>

    #include <iostream>

    #include <cstdlib>

    int main()

    {

    char ch = 'a';

    wchar_t wch = 'b';

    std::cout << &ch << std::endl;

    std::cout << &wch << std::endl;

    std::printf( "%p \n", &ch );

    std::printf( "%p \n", &wch );

    system( "PAUSE" ); //yes I know... but I'0m lazy :p

    }

    the printf works fine, but std::cout print garbage in the console for the char address (but not for the wchar_t address). Using std::cout for printing other type (int, short, float, double, etc..) address works fine, only with chars gives problems.

  • @Alessio T

    check this:

    stackoverflow.com/.../how-to-simulate-printfs-p-format-when-using-stdcout

    the overload operator<< for char* treats it as null-terminated string, that's where your garbage stuff comes from.

Page 3 of 4 (50 items) 1234