Visual Studio “14” CTP 3 Released

Visual Studio “14” CTP 3 Released

Rate This
  • Comments 58

Today we released Visual Studio “14” CTP 3 and an early build of the .NET Framework vNext. Get it from the Microsoft Download Center or from MSDN subscriber downloads or save some setup time and use a ready-to-use VM in Azure. You’ll find a complete list of new features and fixes in the Visual Studio “14” release notes. Some highlights in this release include:

  • ASP.NET and Web Development vNext Updates. This CTP includes all the Visual Studio 2013 Update 3 web tooling improvement and ASP.NET vNext alpha 3 runtime packages. It has improved tooling support for ASP.NET vNext, such as support for build configuration and support for unit tests, and it no longer includes content and compile items inside “.kproj” file. ASP.NET vNext includes an updated version of the RyuJIT JIT compiler. For details, please read the full post on the .NET Web Development Tools blog.
  • .NET Native Updates. .NET Native is now integrated into Visual Studio “14.” It includes initial support for calling WCF services within .NET Native apps and the associated Add Service Reference experience in Visual Studio.
  • PerfTips in the Debugger. In CTP 3 you can see how long your code took to execute as you hit breakpoints and step through code with the debugger. Simply look at the end of the current line when you are stopped in the debugger to see the performance tooltip. For more information read the dedicated post on PerfTips on diagnostics blog.

PerfTips

  • Visual C++ Enhancements. In this CTP, we continue enhancing our C/C++ standard conformance support in addition to overall C++ user productivity improvements. In the standards area, the compiler now supports the thread_local storage specifier, which allows objects to be stored separately for each thread. In the productivity area, Light Bulbs replace Smart Tags to show fixes to issues. Light Bulbs are both more discoverable and also offer a preview of the action before you take it. In addition, you can now refactor to convert string literals littered with escape sequences into a much more easily-readable raw-string format. We have also integrated the Rename Symbol extension for Visual Studio 2013 into the product. To learn more these features, check the Visual C++ team blog.
  • Roaming Custom Layouts. In CTP 2 we introduced Custom Layouts, which enable you to save and apply your tool window layout customizations. In CTP 3 Visual Studio will now roam these customizations across machines that have CTP 3 installed if you signed into the IDE with the same account.
  • Shared Projects. With CTP 3, you can create an empty C#, VB, and JavaScript shared project from the “File > New Project” menu. Windows Store/Phone Projects written in C#/VB/JavaScript, as well as some classic desktop projects (Console Application, Class Library, Windows Form Application, Portable Class Library, WPF) written in C#/VB can consume one or many of these shared projects.
  • High Resolution Icons. In this CTP, Visual Studio supports high resolution icons in command bars, tool window toolbars (standard) and main menus when running above 100% DPI scaling.

Other Developer Releases

Along with Visual Studio “14” CTP 3 I also want to call attention to some related released that we recently announced:

We’re looking forward to your feedback on this CTP. Please post your suggestions on UserVoice, log bugs you find on our Connect site and send us a smile or frown from inside the IDE.

Thanks,

John

image 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.

Leave a Comment
  • Please add 7 and 4 and type the answer here:
  • Post
  • Good job on frequent updates.  Hope to see an updated/supported C#/VB Interactive Window and scripting APIs soon.

  • Wow, that was fast. Can we hope for mainstream support for Roslyn in VS late this year?

  • You guys are making great progress. Loving the new rapid release work style you are using as well! Keep the previews coming!

  • I have a few comments re: the Bing developer assistant.  I love the capabilities -- extremely useful for unfamiliar frameworks!

    However, I am concerned about it querying Bing each time I press ".".  Is there an option to restrict this in some way as to prevent proprietary/sensitive aspects of our code from being sent as a query?  I don't see one but I may well be missing it.

    It would be useful, and possibly even necessary, to have the ability to restrict these searches to smaller scopes -- e.g. .NET framework APIs only, any APIs from outside your solution, APIs from assemblies not marked with a certain company, etc.  There would not likely be any information out on Bing pertaining to most solution's code anyway.

  • I cannot believe how fast this is coming out. Microsoft is really making good on their promise to deliver a faster development cycle.

  • @Vitor

    Thanks for your interest! We're really excited to get these out to you at a more rapid cadence. As you probably know, the new C# and VB compilers and IDEs developed as part of the Roslyn project are included in Visual Studio "14" as announced a few months ago at this year's //build. At the moment, we can't disclose a final release date but we love being able to get these out to you so quickly to see our progress.

    Thanks!

    Dustin Campbell

    Visual Studio Managed Languages

  • Hi James

    Thank you for your feedback!!  

    >> Is there an option to restrict this in some way as to prevent proprietary/sensitive aspects of our code from being sent as a query? It would be useful, and possibly even necessary, to have the ability to restrict these searches to smaller scopes -- e.g. .NET framework APIs only, any APIs from outside your solution, APIs from assemblies not marked with a certain company, etc.  There would not likely be any information out on Bing pertaining to most solution's code anyway.

    In the current design, you can collapse the 'code sample' panel in the intellisense window.  The plugin will remember your choice, and it will not issue any bing code search requests, until you expand the 'code sample' panel next time.

    We also got some similar suggestions from MVPs who want to ignore some APIs for code sample search by easily adding those APIs to a 'blacklist' using a shortcut key.   I love your suggestion too.  We are considering adding these features.

    We have lots of other new cool features to be added to the plugin in the following months.  Please keep using the plugin and give us feedback (bingdevassistant@microsoft.com).  We will try to make a new release every month to fulfill your amazing ideas. :)

    Thanks

    Scott (MSFT)

  • Can it be safely used with VS 2013 side-by-side?

    Awesome release, thank you! :)

  • I wonder it too if this release can be used side-by-side with 2013. At least the statement not to do so has been removed from release notes.

  • @ Kim Tranjan, Asgard,

    This CTP should work side by side with Visual Studio 2013, Visual Studio 2012, and Visual Studio 2010. That said, please note that this is a CTP release and not supported in production.

    Radhika  Tadinada [MSFT]

  • I'm very interested in the faster development cycle for ASP.NET MVC, and this is the first CTP of 14 I'm trying. I still feel it is taking a long time to recompile after changes. Things like changing a string in the controller of the sample app still takes about 5-10 seconds to refresh the page in an 8-core i7 with 8gb ram.

    Is that "background compilation" thing enabled in this version? Or is that only for some specific scenarios with Azure?

  • Ok, I guess I got it. The fact is that you need to use "k10" target, and it still takes some time to compile. The fact is that it can do it automatically without rebuilding, but the compilation time is still there.

  • I am concerned about the change to no longer have the files listed in the project file.  This was how Web Site projects worked, and was a huge problem for us.

    If this is the case, how do you handle the temporary removal of a file from a project? This happens a lot when I am working on some new feature (i.e. new, incomplete files), and a bug comes along that needs immediate fixing.  I then like to remove the new files from the project (so they don't break the build), and then fix the bug.

    If now everything is based on the file system, how much more work will it be to temporarily remove, and then readd a file. Do we have to move it to another directory, remember to move it back, etc.  This is much more painful then the current process.

  • When will the XNA projects templates get updated for Visual Studio 2014 - on the release or one of the upcoming service packs?

    Thank you!

    visualstudio.uservoice.com/.../3725445-xna-5

  • You should mention that C# 6.0 features are being added into the CTPs as they are released:  roslyn.codeplex.com/.../552378

Page 1 of 4 (58 items) 1234