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.
The menus won't be yelling at me any more? WOOHOO!
Can it be safely used with other VS 2012 / 2013 versions on a Machine side-by-side?
@Vidya Vrat Agarwal
It's best if you don't run side-by-side with other VS versions. If you look at the known issues in the KB article (support.microsoft.com/.../2967191) you'll see that, though we've made progress since the last CTP, there are still issues. Use a fresh/clean system or the Azure VM.
There are known issues when you install Visual Studio "14" CTP 14.0.21901.1 DP on the same computer as Visual Studio 2013. While we expect that an uninstallation of Visual Studio "14" and then a repair of Visual Studio 2013 should fix these issues, our safest recommendation is to install Visual Studio "14" in a virtual machine, a virtual hard disk (VHD), a fresh computer, or another non-production test-only computer that does not have Visual Studio 2013 on it. These Visual Studio side-by-side issues are expected to be fixed soon.
@Vidya Vrat Agarwal: I wouldn't install it on anything except a vm or test enviroment. Like John says at the bottom "Please install the CTP on a test environment, such as a clean VM or clean machine, and not on a primary-use machine.".
I am really happy to see Visual Studio update this often, I am starting to trust Microsoft, I like the Google style of updates every few weeks of Chrome and Chrome Dev Tools, and it looks like Microsoft is catching up with VS.NET.
Will there be at last the option to italicize a font for some syntax elements (in Fonts and Colors tab, just below "Bold" checkbox?) A one-hour fix requested for (and not implemented since) no less than 7 years.
How about installing it over "14" CTP1?
Can you guys add this to your installer test matrix:
Pre-create all the folders on another drive that VS installer or VS update installer normally creates during install/update. Then MKLINK /D the folders on C: program files (including "Microsoft SDKs"), to another drive, and now run the installer.
If the directory links do no longer exist after the installer/update was run, then block the release until that is fixed.
I didn't look at this closely but I think some of the LightSwitch related processes actually deletes the folders in Program files and re-creates them. This causes a bit of a mess if you had redirected those folders before running an update. (Happened atleast on 2013 Update 3)
I DON'T YELL TO YOU BUT JUST KEEP WITH A MICROSOFT-WIDE EMPHASIS ON TYPOGRAPHY AND CASING AS A KEY STRUCTURE-DEFINING ELEMENT.
"We updated the Configuration and Platform dropdown values for VC++ Property Page dialog to remember the last user selection when the dialog is closed." : Thank you, Thank you, Thank you! :-)
Why does Visual Studio 14 install the Visual C++ 11 and 12 redistributables? Are they really needed?
THE ALLCAPS MENU DISASTER IN VS2013 IS REASON FOR A NEW RELEASE ALL BY ITSELF. WTF MICROSOFT WHY ARE YOU SHOUTING AT ME?
@Marcel, VS14 CTP2 is built with the VC++ 12 toolset and hence needs the VC12 redist to run. There are also a couple of other components that are still built with the VC11 toolset and hence the need of the vc11 redist. We are working on removing all VC11 dependencies (toolset & redist) from VS14.
Visual C++ Team
THANK YOU THANK YOU THANK YOU THANK YOU THANK YOU THANK YOU THANK YOU THANK YOU THANK YOU THANK YOU THANK YOU THANK YOU THANK YOU THANK YOU THANK YOU THANK YOU THANK YOU THANK YOU THANK YOU THANK YOU THANK YOU THANK YOU THANK YOU THANK YOU THANK YOU THANK YOU THANK YOU ... for removing the upper case menus. It was a terrible idea.