Since the newer Visual C++ content is not yet live on MSDN, I copied the key bits from the "What's New for Visual C++ Developers" and replicated it below. Note that this post may be removed after the MSDN content has been available for a few weeks.
Thanks for your patience!
The default behavior when this option is not specified is the same as in Visual Studio 2012.
The Visual Studio IDE has significant improvements to help you be more productive when you code in C++.
To modify the brace-completion settings, on the menu bar in Visual Studio, choose Tools, Options, expand the Text Editor, C/C++, and General nodes, and then make your changes. You can also change the settings for all Visual Studio languages by expanding the Text Editor, All Languages, and General nodes.
To modify specific C++ settings, on the menu bar, choose Tools, Options, expand the Text Editor, C/C++, and Advanced nodes, and then make your changes.
will more c++11 added in the future or we must wait for another VS release?
Nothing yet about cost for vs2013 which is making me nervous. We've only just bought vs2012 professional. I don't really want to have to go to my boss and explain that we now need to purchase another version of devstudio for a few additional C++ features which we thought would be added to vs2012!
> Resizable C++ Project Properties Window.
I'm thankful for any new C++11 mercies we can get. The template stuff is nice for library code and all. But seriously, how hard can implicitly-defined default move ctor & assignment functions really be? I die a little inside every single day I have to write out totally redundant move ctors & assignment operators by hand. That's code that's cumbersome to maintain, thrice the length any sensible person would expect it to be and bound to be overseen when new class members are added, thus expiring and breaking unnoticedly every other month.
Even worse, everyone else will suffer severe pain once they realize their manually written and carefully maintained move ctors & assignment operators in fact break implicitly-defined copy functionality when the copiler finally gets round to implementing sensible copy/move member function generation rules as specified by C++11 *. Right now, you're not only lagging behind C++11, you're making it worse just by leaving out some seemingly trivial functionality. I hope you can fix that till RTM, you will have my eternal gratitude for it!
* If the class deﬁnition declares a move constructor or move assignment operator, the implicitly declared copy constructor is defined as deleted.
Can Microsoft just announce EOL for MFC if we're not going to see significant updates to it ever again? I feel a proper announcement would go a long way to getting organisations off of it
does chrono uses high definition performance timer in this release?
@CodingCat +1 for adding "implicitly-defined default move ctor & assignment functions". As I understand (maybe wrongly) these would require "noexcept" to also be implemented in VS2012/13
On my personal "wants list" I really would like "defaulted and deleted Functions", "non-static data member initializers" and "constexpr" to be added.
> Improved ISO C/C++ Standards Support
I'm glad I didn't buy 2012. I would be seriously pissed off right now. I mean you DID said you would do out of band compiler updates (no, buggy CTP doesn't count).
> C99 Libraries
It's so embarrassing that those were missing for such a long time that I feel weird to be happy about it. But I am.
> Brace Completion
> Toggle Header/Code File
Finally! Just 5 to 10 more releases like this and I won't have to buy VisualAssistX to be able to work with C++
Only additions I really want for MFC/ATL is that move constructors/operators to be added to CString and some other data classes.
Still no non-static member initializers? Shame on you! :p
@All, thanks for the feedback.
About conformance, for more forward-looking information please catch Herb Sutter and "The Future of C++" at Build. It will be available as a live stream on Friday. See channel9.msdn.com/.../2-306 for more details.
Nothing new in UI development for native apps. Go Figure.
Looking forward to Herb's build session.
The Visual C++ Team really needs to focus faster on c++11 compliance.
clang and gcc are already fully compliant, authoritative c++ 11 books are finally there.
It is high time for us to be able to use c++ 11.
I think that the Visual C++ team starts focussing on C++14 now. We already have a pretty good idea of what will be in and that way we don't have another wait to catch up in 2 years
@STL (hoping he reads this): Is there any reason that std::mutex uses windows Mutexes, instead of the more efficient CRITICAL_SECTION API? Is there some feature of std::mutex that CRITICAL_SECTION doesn't support?