Microsoft makes available first test build of 'Visual Studio 14'

Microsoft makes available first test build of 'Visual Studio 14'

Summary: Microsoft has released a first preview of its its 'Visual Studio 14' development environment, which the company is planning to roll out in calendar 2015.


Microsoft made available for download a first community technology preview of the next release of Visual Studio, codenamed Visual Studio 14, on June 3.


Visual Studio 14 will be available some time in 2015, and there will be a "more complete" preview build and final naming available later in 2014, according to a new blog post by Developer Division chief Soma Somasegar. The first VS'14 CTP is downloadable here.

(Hmm. I thought we were moving away from the confusing number code names with Visual Studio. Supposedly this next version was going to be "Adams." I guess someone voted to postpone going that route? Too bad.)

Anyway, back to features that are part of "VS 14."

Microsoft already said that its "Roslyn" .Net compiler platform, ASP.NET v.Next (codenamed Project K) and supporting Apache Cordova tooling will all be part of the next versio of Visual Studio by the time it ships next year. Microsoft also is continuing to flesh out standards support for Visual C++ in the coming VS release.

With the coming release, the C# and Visual Basic compilers and the integrated development environment are all built on the open-sourced Roslyn "compiler as a service." The preview build includes early coding for the tooling for ASP.NET v.Next and ASP.NET 4.5 Web-application templates.

Microsoft also is simultaneously working on updates for Visual Studio 2013, and recently released a first preview of VS 2013 Update 3.

Topics: Software Development, Microsoft, Open Source, Windows Server


Mary Jo has covered the tech industry for 30 years for a variety of publications and Web sites, and is a frequent guest on radio, TV and podcasts, speaking about all things Microsoft-related. She is the author of Microsoft 2.0: How Microsoft plans to stay relevant in the post-Gates era (John Wiley & Sons, 2008).

Kick off your day with ZDNet's daily email newsletter. It's the freshest tech news and opinion, served hot. Get it.


Log in or register to join the discussion
  • Geez i have just started using vs2013!

    That is very quick. I really like the speed but worried about incompatibility of other productivity tool such as Re Sharper etc. They cost lot of money!
    • Major version

      I am guessing this will be a pretty major version -- new versions of the language, MAJOR new version of .NET, major new version of web tools, and a brand new compiler. So in this case, much more than 2013, I wouldn't be surprised to see incompatibilities.

      It may be that tools like Resharper will be less necessary in the future with the new compiler, but it remains to be seen what the IDE will support natively. Even if VS doesn't support all the capabilities of tools like Resharper out of the box, it should be much easier for folks to implement similar tools with much less effort.
  • "Roslyn" .Net compiler platform

    I hope to see more interesting features with this compiler, and VB language too..
  • Why 14

    Why Microsoft keep changing between year and version number?
    I hope they make tools for mobiles. So, We less depend on other
    Utomo Prawiro
    • Version number is internal-only.

      The version number is just internal. As the article points out, the final version will be branded. I would not be surprised if it were Visual Studio 2015. Every version of Visual Studio since I think 2003 has been branded with the year.
      • Naming

        Not to be pedantic, but why not...I used to run Visual Studio marketing :-)

        The first VS was Visual Studio 97, in 1997.
        Then Visual Studio 6.0 (infamously, this was the one that got us sued by the Feds because of VJ++, which was my product)
        Then Visual Studio .NET 2002, during Microsoft's ill-fated "everything must be .NET" phase. I was the C# product manager during this time.
        Visual Studio .NET 2003
        Visual Studio 2005 (and Visual Studio 2005 Team System, during Microsoft's ill-fated "everything must be a System" phase). Both VSTS and the awesome Express products were my beloved little babies.
        Visual Studio 2008 (I left soon after this launch)

        I'm an iOS and Android guy now, so don't pay much attention to the Microsoft world, so after that I have no idea.
        • Curious Naming

          With a bit of perspective now, does it seem that all the JAVA (and for that matter C#) effort was worthwhile to Microsoft? It seemed to me at the time that all Microsoft did was divide their developer community. They could have delivered 100% compatibility with Windows Mobile instead for example during that time period.
  • What .net version is this?

    Does this use the same .net version as Visual Studio 2013 (4.5.1)? If not, does it overrwrite .net 4.5.1 in the same way it overwrote 4.5, which overwrote 4.0?

    How hard is it to have each version in a separate directory?
    • Maybe you should reswarch why..

      There are reasons, it's not as simple as lets just have another folder side by side.
    • .Net Framework

      Out of the box it's up to .Net Framework 4.5.1

      I'm guessing you would need to install 4.5.2 developer edition to target that version. I haven't yet installed it myself, so I'm just guessing.
  • Compiler-as-a-service??? What a joke!!!!

    Software is no longer software. It's just a service huh? Why do I feel like Microsoft is no longer happy with dipping their hands in my pants once every 3 years? It seems they want to dip their hands into my pants and keep them there permanently. That gives them WAY too much power. That makes us all WAY too dependent on them.

    I am starting to think Microsoft and our gestapo-like federal government are one in the same these days.
    • Ignorance at its finest.

      CaaS is not what you're mistakenly thinking it is. CaaS is not a cloud service, it's a local offline only tool that gives a dev access to all of the analysis goodness of the VB and C# compilers.

      Perhaps take some time to learn about the things you rant about before sounding like an idiot.

      Also comparing the US gov to the Gestapo shows a distrubing lack of knowledge about the real Gestapo.
    • So a feature meant to empower developers...

      you believe is some sort of clandestine attempt to make you dependent on them. Given you believe the federal government is gestapo like, not surprising.

      Get therapy, and an education, you definitely need both.
    • Actually "cloud" compiling is a good thing

      I use a Cruise Control build server, and its nice to just check code in and not have to maintain version numbers, the build config, or any of that. Any time you do work as a team, a build server saves a lot of effort, and can help you tell who is putting in breaking changes, etc.
  • Cannot keep up: I now have VS2012, VS2012 and VS2013 installed.

    Seems we need to support multiple Visual Studios to maintain our variosu projects.
    I still VS2010 still needed for XNA Content pipelien development.

    Its getting pretty tiresome, that microsoft keep stinging us for VS upgrades, to build against their latest platforms.
  • You people bemoaning the frequent updates

    You should really calm down, and try to understand that in order for Microsoft (or any company) to rapidly deploy new versions of the OS and new functionality, they need to be just as nimble at deploying updated developer tools. And that means that the underlying techniques for developing against the platform will change frequently.

    The old model of building win32 applications is gone. If you want to blame someone, blame Apple for the app model that has become so successful. But really, instead of worrying about blame and anger, you should be understanding that adapting to the rapidly changing technology landscape is what's important in order to be a developer these days.

    If all you want to do is continue to develop win32 and .NET applications, nothing is stopping you from sticking with older versions of VS. They will continue to function just fine for many years. Just be prepared that you will not be able to develop for new platforms and apps using the old tools. If you don't think that makes sense, then you have a disconnect that cannot be bridged by reason.
  • Build Style

    I hope they brought back the "Build Style" functionality... I used that every day and all of a sudden it disappeared from VS 2013... :(
  • Darnit!

    I've already got VS 2003, 2008, 2010, 2012, and 2013 on my machine! I think I need to uninstall one before adding yet another.

    Pretty excited to see Roslyn come along integrated in a VS build.