The official source of product insight from the Visual Studio Engineering Team
Today we released CTP 2 of Visual Studio “14,” which is the codename for the next version of Visual Studio. To get started, you can download the bits (also available on MSDN subscriber downloads), or use the VM in Azure we’re making available (see the note below). In addition to the new features we added in CTP 1, this CTP also includes:
You can find a complete list of new features in the Visual Studio “14” CTP knowledge base article.
Note: We intend this preview to be used for testing and feedback purposes. It’s not meant for production environments. Please install the CTP on a test environment, such as a clean VM or clean machine, and not on a primary-use machine.
We’re looking forward to your feedback on the CTP. As always, please post your suggestions on UserVoice and any bugs you find on our Connect site.
John Montgomery, Director of Program Management, Visual Studio Platform
John has been at Microsoft for 15 years, working in developer technologies the whole time. Most recently before working on the Visual Studio core development environment, he was working on the tools for Windows 8 development.
@Kangyuan Niu, you wrote:
"We are currently making major modifications to the way our compiler handles initialization".
Sounds hopeful :-) Is there any chance that those compiler bugs regarding value-initialization will then finally be fixed? Visual C++ usually compiles an attempt to value-initialize an object, but it may then leave parts of the object uninitialized.
Bug reports on this issue have been marked as "Won't Fix", for example:
Bug ID 499606, "Presence of copy constructor breaks member class initialization", by Alex Vakulenko
Bug ID 484295, "VC++ does not value-initialize members of derived classes without user-declared constructor", by Sylvester
Bug ID 100744, "Value-initialization in new-expression", reported by Pavel back in 2005 (was removed from Connect!)
In 2010 I wrote an extensive compiler test on value-initialization for Boost: svn.boost.org/.../boost_no_com_value_init.ipp Please try it out! For example as follows:
// Returns the number of test failures (zero = OK).
See also http://rextester.com/TFH63485 Note that it has some link errors, introduced by VS2013, as I reported: "error LNK2019, trying to value-initialize an array by a mem-initializer of a constructor", connect.microsoft.com/.../900715 Hope you can fix that as well :-)
We are still using VS2012 at work.VS2013 was out no longer ago.I think you should release VS every 3 years or so.
I actually liked the all-caps menus. I'd love the option to turn it back on.
Neither 499606 nor 484295 can be reproduced in Visual Studio "14" CTP 3. Please try our the latest release and verify that value initialization indeed works correctly now.
Light Bulb Editor Adornment: following NetBeans I see...
Where is Silver Twist ?
@Kangyuan Niu Thanks for informing us that these value-initialization bugs (ID 499606 and ID 484295, both reported in 2009) are finally fixed, with Visual; Studio "14" CTP! Martin Moene (martin-moene.blogspot.nl) just informed me that indeed, most run-time test failures of my value-initialization test svn.boost.org/.../boost_no_com_value_init.ipp appear vanished with VS "14" CTP 3! Only value-initialization of pointer-to-member objects appears to remain troublesome.
I cannot believe that such utter trivialities as all-caps menus are the main worry for some people! As if there weren't more pressing issues, like improved conformity of the compiler with the "new" C++11 standard, for example!
@Kangyuan Niu, I'm very glad about those major compiler bug fixes regarding value-initialization (including ID 499606 and 484295). But I feel you challenged me by saying "Please... verify that value initialization indeed works correctly now". :-)
Just reported: "[C++] Pointer-to-member data member of value-initialized aggregate should have null member pointer value", connect.microsoft.com/.../956553
Also still in VS "14" CTP 3: "[C++] error LNK2019, trying to value-initialize an array by a mem-initializer of a constructor", connect.microsoft.com/.../900715
Can you please fix these two as well? :-)
Please spend resources on making the C++ compiler fully C++11 compliant in VS2013. The bells and whistles are meaningless if the meat and potatoes are missing.
Please give us atleast a Option for a all uppercase menu style. Currently it Looks just bad.