DetailPage-MSS-KB

Microsoft small business knowledge base

Article ID: 2967191 - Last Review: August 26, 2014 - Revision: 9.0

This article lists the release notes for the Microsoft Visual Studio "14" Community Technology Previews (CTPs).

Visual Studio "14" CTPs are previews for the next major release of Visual Studio. These Visual Studio CTPs are intended to promote continuous feedback between early adopters and the Visual Studio development team. We would love to receive your input about the new product functionality and the improved experiences. Your feedback will help shape the future of Visual Studio. Together, we will improve the developer experience.

The following download links always point you to the latest CTP.

Collapse this imageExpand this image
Download
Download the latest Visual Studio "14" CTP (web) package now. (http://go.microsoft.com/fwlink/?LinkId=509824)

Collapse this imageExpand this image
Download
Download the latest Visual Studio "14" CTP (iso) package now. (http://go.microsoft.com/fwlink/?LinkId=509825)


Notes:
  • CTPs are English only.
  • CTPs are unsupported and are intended to be used for testing, trial, and feedback purposes only.
  • CTPs have not been subjected to final validation. They are not meant to be run on production workstations or servers, or used to create production code. Installing a CTP on a production server will put the server into an unsupported state.
  • Although these CTPs are intended to be installed side-by-side with earlier versions of Visual Studio, complete compatibility on every CTP is not guaranteed.

Feedback

The goal of this CTP is to collect your feedback. To report a bug, please use Connect (https://connect.microsoft.com/VisualStudio/feedback/CreateFeedbackForm.aspx?FeedbackFormConfigurationID=5303&FeedbackType=1) . You can also share your ideas and suggestions on UserVoice. (http://visualstudio.uservoice.com/forums/121579-visual-studio) Your quick thoughts can be shared by using Send-a-Smile (http://msdn.microsoft.com/en-us/library/zzszcehe.aspx) through the Visual Studio IDE.

On This Page

Visual Studio "14" CTP 3 (version 14.0.22013.1.DP) details

Collapse this imageExpand this image

Technology improvements

Collapse this imageExpand this image
The following technology improvements have been made in this release.

ASP.NET and web development
Collapse this imageExpand this image
  • ASP.NET vNext tooling features
    • Visual Studio does not store file names in the ".kproj" project file to track which files are included in the project. Files in the project directories are automatically included in the project, and files are automatically removed from the project when they are removed from the project directories.
    • Unit test integration is added, and the experience will be improved in the later releases.
    • Support for Build Configuration is added.
  • ASP.NET vNext Runtime updates
    • Visual Studio "14" CTP 3 includes alpha3 runtime packages for ASP.NET vNext (http://go.microsoft.com/fwlink/?LinkId=400692) . All the details on the specific enhancements added and issues fixed can be found in the published release notes (http://go.microsoft.com/fwlink/?LinkId=403951) on GitHub.
  • ASP.NET updates from Visual Studio 2013 Update 3
      Microsoft ASP.NET and Web Tools in Visual Studio "14" CTP 3
      • Scaffolding: Support for ASP.NET 5.2 technologies (MVC, Web API)
      • JSON editor: Auto-formatting and brace matching
      • CSS editor: Selectors level 4, drag-and-drop of fonts, images and other .css files
      • Support for Microsoft Azure WebJobs publishing. Now, you can create standard console application projects in Visual Studio solutions that can be published to Azure Websites as continuous, triggered, or scheduled WebJobs. For more information, see How to Deploy Azure WebJobs to Azure Websites (http://azure.microsoft.com/en-us/documentation/articles/websites-dotnet-deploy-webjobs/) .
      • Add support for two-factor authentication in One ASP.NET templates for MVC, Web Forms support.
      • Enable creation of ASP.NET projects by using Azure Active Directory when you sign in with MSA (Microsoft Account, formerly known as Live ID). For more information, go to here (http://go.microsoft.com/fwlink/?LinkId=458516) .

      ASP.NET MVC 5.2 (http://www.asp.net/mvc/overview/releases/whats-new-in-aspnet-mvc-52)
      • Attribute routing improvements (http://www.asp.net/mvc/overview/releases/whats-new-in-aspnet-mvc-52#AttributeRouting)
      • Feature updates (https://aspnetwebstack.codeplex.com/workitem/list/advanced?keyword=&status=All&type=Feature&priority=All&release=v5.2%20RC&assignedTo=All&component=MVC&sortField=AssignedTo&sortDirection=Ascending&page=0&reasonClosed=Fixed)
      • Bug fixes (https://aspnetwebstack.codeplex.com/workitem/list/advanced?keyword=&status=Closed&type=Issue|Task&priority=All&release=v5.2%20RC&assignedTo=All&component=MVC&sortField=AssignedTo&sortDirection=Ascending&page=0&reasonClosed=Fixed)
      • What’s New in ASP.NET MVC 5.2 (http://go.microsoft.com/fwlink/?LinkID=403009)

      ASP.NET Web API 2.2 (http://www.asp.net/web-api/overview/releases/whats-new-in-aspnet-web-api-22)
      • OData v4 support (http://www.asp.net/web-api/overview/releases/whats-new-in-aspnet-web-api-22#OData)
      • Attribute routing improvements (http://www.asp.net/web-api/overview/releases/whats-new-in-aspnet-web-api-22#ARI)
      • Web API Client support for Windows Phone 8.1 (http://www.asp.net/web-api/overview/releases/whats-new-in-aspnet-web-api-22#phone)
      • Feature updates (https://aspnetwebstack.codeplex.com/workitem/list/advanced?keyword=&status=All&type=Feature&priority=All&release=v5.2%20RC&assignedTo=All&component=Web%20API&sortField=AssignedTo&sortDirection=Ascending&page=0&reasonClosed=Fixed)
      • Bug fixes (https://aspnetwebstack.codeplex.com/workitem/list/advanced?keyword=&status=Closed&type=Issue|Task&priority=All&release=v5.2%20RC&assignedTo=All&component=Web%20API|Web%20API%20OData&sortField=AssignedTo&sortDirection=Ascending&page=0&reasonClosed=Fixed)
      • What’s New in ASP.NET Web API 2.2 (http://go.microsoft.com/fwlink/?LinkID=403010)

      ASP.NET Web Pages 3.2 (http://www.asp.net/web-pages/overview/releases/whats-new-in-aspnet-web-pages-32)
      • Minor feature update (https://aspnetwebstack.codeplex.com/workitem/list/advanced?keyword=&status=All&type=Feature&priority=All&release=v5.2%20RC&assignedTo=All&component=Web%20Pages%2FRazor&sortField=AssignedTo&sortDirection=Ascending&page=0&reasonClosed=Fixed)
      • Bug fixes (https://aspnetwebstack.codeplex.com/workitem/list/advanced?keyword=&status=Closed&type=Issue|Task&priority=All&release=v5.2%20RC&assignedTo=All&component=Web%20Pages%2FRazor&sortField=AssignedTo&sortDirection=Ascending&page=0&reasonClosed=Fixed)
      • What’s New in ASP.NET Web Pages 3.2 (http://go.microsoft.com/fwlink/?LinkID=403011)

      ASP.NET Identity
      • Added support for SignInManager. SignInManager makes it easier to add Two-Factor authentication, account lockout, and other security features when you log on. For more information about this feature, go to this blog post (http://blogs.msdn.com/b/webdev/archive/2014/08/05/announcing-rtm-of-asp-net-identity-2-1-0.aspx) .

      Microsoft ASP.NET and Web Tools 2013.3
      • Removed ASP.NET Facebook MVC template. We are now shipping the ASP.NET Facebook template as a Visual Studio Extension on the Visual Studio gallery. You can download this template from here (http://go.microsoft.com/fwlink/?LinkID=507338&clcid=0x409) .

      Entity Framework 6.1.1
      • Microsoft released EF 6.1.1 in this update. For more information, go to this blog post (http://blogs.msdn.com/b/adonet/archive/2014/06/20/ef-6-1-1-rtm-available.aspx) .

      WebDeploy 3.5 refresh
      • Microsoft released a Web Deploy 3.5 refresh in Visual Studio Update 3 to enable integration with SQL Server 2014. You can also download it from here (http://blogs.iis.net/msdeploy/archive/2013/07/09/webdeploy-3-5-rtw.aspx) .

      IIS Express 8.0 June 2014 Hotfix
      • Microsoft released an IIS Express 8.0 June 2014 Hotfix in Visual Studio Update 3. This hotfix addresses an issue in IIS Express 8.0 when you create a site and use certain character combinations in the site's folder; this causes Internet Information Services (IIS) 8.0 Express to not start. You can also download the hotfix from here (http://www.microsoft.com/en-us/download/details.aspx?id=43380) .

Collapse this imageExpand this image
Debugger
Collapse this imageExpand this image
  • You can now see how long code took to execute directly in the editor when code execution exceeds a threshold.
Collapse this imageExpand this image
Visual C++
Collapse this imageExpand this image
  • You can now refactor string literals that are littered with escape sequences into a much more easily-readable raw-string format. The supported sequences are \n (new line), \t (tab), \\ (backslash), \' (single quote), \" (double quote), and \? (question mark). To use this feature, right-click any string literal (wide or narrow), and then select Refactor->Convert To Raw String Literal to execute the operation.
  • We replaced SmartTags with LightBulbs for Create Declaration/Definition, making it easier for you to see and click on these notifications.
  • We integrated the Rename Symbol extension for Visual Studio 2013 (titled Visual C++ Refactoring on Visual Studio Gallery) into Visual Studio and added functionality such as being able to cancel the operation if it takes too long.
  • We implemented thread local storage: use the thread_local keyword to declare that an object should be stored independently for each thread.
  • Visual Studio will now attempt to simplify templates and typedefs in parameter help and quickinfo to make them easier to read.
Collapse this imageExpand this image
Visual Studio IDE
Collapse this imageExpand this image
  • In Visual Studio "14" CTP 2 we introduced a new feature called Custom Layouts to make it easy for you to save custom layouts. In CTP 3, these Custom Layouts roam: any custom layouts you create will synchronize across machines that have the CTP 3 installed when you sign into the IDE with the same account.
  • You can create an empty C#, Visual Basic, or JavaScript shared project from the File -> New Project menu. Windows Store or Windows Phone Projects that are written in C#, Visual Basic, or JavaScript, and some classic desktop projects (Console Application, Class Library, Windows Form Application, Portable Class Library, WPF) that are written in C# or Visual Basic can consume one or many of these shared projects. You can manage shared project references (added or removed) by using the Reference Manager. We will continue to expand Shared Project support for more project types and languages in future Visual Studio "14" CTPs.
  • Visual Studio supports high resolution icons in command bars, tool window toolbars (standard), and main menus when it is running greater than 100% DPI scaling.
Collapse this imageExpand this image
Collapse this imageExpand this image

Known issues

Collapse this imageExpand this image
Visual C++
Collapse this imageExpand this image
  • The new Visual C++ quickinfo may fail to simplify a template if multiple typedefs of the same type are involved. This issue will be resolved in later releases.


Collapse this imageExpand this image
Visual Studio IDE
Collapse this imageExpand this image
  • After you log on Windows, when you start or sign in to Visual Studio "14" CTP 3, you may be prompted to install the .NET Framework 3.5. This is a race condition that is triggered by an assembly that should have been marked as safe for .NET 4.5. 

    To work around this issue, use one of the following methods:
    • Install the .NET Framework 3.5.
    • Set useLegacyV2RuntimeActivationPolicy to true for the startup element in the following configuration files under "C:\Program Files (x86)\Common Files\Microsoft Shared\VsHub\1.0.0.0\"
      • Microsoft.VsHub.Server.HttpHost.exe.config
      • Microsoft.VsHub.Server.ServiceModuleHost.exe.config
      • VsHub.exe.config
    Note The Azure VMs for Visual Studio "14" CTP 3 have already had the second option applied.
Collapse this imageExpand this image
Store Apps
Collapse this imageExpand this image
  • The Push Notification Wizard completes incorrectly because of some errors. The issue will be resolved in later releases.
Collapse this imageExpand this image
Azure .NET Mobile Services
Collapse this imageExpand this image
  • In Visual Studio "14" CTP 3, Azure .NET Mobile Services are unsupported.
Collapse this imageExpand this image
LightSwitch
Collapse this imageExpand this image
  • You cannot publish a LightSwitch project after you apply Visual Studio "14" CTP 3. It is recommended that you retain a previous CTP if you need to publish your application.
  • You can upgrade the LightSwitch projects from previous versions. However, depending on your project type, you may encounter the following issues:
    • Build of upgraded Cloud Business App (CBA) or HTML-based projects may fail because it cannot find the 2.5.1 version of the client runtime.

      To work around this issue, follow these steps:
      1. Right click the LightSwitch HTML Client, and then select Manage NuGet Packages.
      2. Under the Installed packages node, select and uninstall the "Microsoft.LightSwitch.Client.JavaScript.Runtime" package. Do not uninstall any dependencies.
      3. Under the Online node, search for and install version 2.5.1.0 of the "Microsoft.LightSwitch.Client.JavaScript.Runtime" package.
    • Upgraded LightSwitch 2011 or Visual Studio 2012 Desktop-based projects may fail to load correctly at runtime or during debugging.

      NoteUpgrading LightSwitch 2011 or Visual Studio 2012 Desktop-based projects is not recommended in this CTP.
    • Upgraded Visual Studio 2012 Update 2 HTML-based projects may fail to load correctly at runtime or during debugging.

      Upgrading Visual Studio 2012 Update 2 HTML-based projects is not recommended in this CTP.
Collapse this imageExpand this image
Entity Framework
Collapse this imageExpand this image
  • When you use the Entity Framework tools, you receive the following error message:
    Method not found: 'Void Microsoft.VisualStudio.PlatformUI.DpiHelper.LogicalToDeviceUnits(System.Windows.Forms.ImageList ByRef, Microsoft.VisualStudio.PlatformUI.ImageScalingModel)'.
    To work around this issue, install an updated version of the Entity Framework 6.1.1 tools for Visual Studio "14" CTP 3 here (http://www.microsoft.com/en-us/download/details.aspx?id=44008) .
Collapse this imageExpand this image
Collapse this imageExpand this image

More information

Collapse this imageExpand this image
How to download Microsoft support files  (http://support.microsoft.com/kb/119591/ )

Updates for other products in the Visual Studio family can be found on the Microsoft download site for Visual Studio (http://www.microsoft.com/visualstudio/eng/downloads) .

Products

Collapse this imageExpand this image
This Visual Studio "14" CTP 3 (version 14.0.22013.1.DP) release includes the following products: 
  • Microsoft Visual Studio Professional "14" CTP (web (http://go.microsoft.com/fwlink/?LinkId=509824) | iso (http://go.microsoft.com/fwlink/?LinkId=509825) )
  • Remote Tools for Visual Studio "14" CTP (x86 (http://go.microsoft.com/fwlink/?LinkId=509827) | x64 (http://go.microsoft.com/fwlink/?LinkId=509828) | arm (http://go.microsoft.com/fwlink/?LinkId=509829) )
  • Microsoft Visual Studio "14" SDK CTP (exe (http://go.microsoft.com/fwlink/?LinkId=509826) )
  • Multibyte MFC Library for Visual Studio "14" CTP (exe (http://go.microsoft.com/fwlink/?LinkID=509830) )
Collapse this imageExpand this image

Requirements

Collapse this imageExpand this image

Software requirements

On Windows 8.1 and Windows Server 2012 R2, Update 2919355 (http://support.microsoft.com/kb/2919355) (also available through Windows Update) is required for the Visual Studio "14" CTPs to install successfully.

Restart requirement

You may have to restart your computer after you install this package.

Supported architectures

  • 32-bit (x86)
  • 64-bit (x64) (WOW)
  • ARM

Hardware requirements

  • 1.6 gigahertz (GHz) or faster processor
  • 1 gigabyte (GB) of RAM (1.5 GB if you are running in a virtual machine)
  • 2 GB of available hard disk space
  • 5,400 RPM hard disk drive
  • DirectX 9-capable video card that is running at a resolution of 1024 × 768 or higher
Collapse this imageExpand this image
Collapse this imageExpand this image
Collapse this imageExpand this image

Visual Studio "14" CTP 2 (version 14.0.21901.1.DP) details

Collapse this imageExpand this image

Technology improvements

Collapse this imageExpand this image
The following technology improvements have been made in this release.

ASP.NET and web development
Collapse this imageExpand this image
  • ASP.NET vNext: This release of Visual Studio supports creating and developing ASP.NET vNext applications. ASP.NET vNext is a lean and composable .NET stack for building modern web applications for both cloud and on-premises servers. It includes the following features:
    • ASP.NET MVC and Web API have been unified into a single programming model.
    • A no-compile developer experience.
    • Environment-based configuration for a seamless transition to the cloud.
    • Dependency injection out-of-the-box.
    • New cloud-optimized runtime supports true side-by-side versioning.
    • NuGet everything, even the runtime itself.
    • Run in IIS, or self-hosted in your own process.
    • All open source through the .NET Foundation (http://www.dotnetfoundation.org/) , and takes contributions.
    For more information about ASP.NET vNext in Visual Studio, go to the ASP.NET vNext (http://go.microsoft.com/fwlink/?LinkId=400692) website.
  • This release of Visual Studio also includes all the current ASP.NET and web development features that are released as parts of Visual Studio 2013 Update 2. Learn more here (http://go.microsoft.com/fwlink/?LinkId=400693) .
Collapse this imageExpand this image
Visual C++
Collapse this imageExpand this image
  • Find in Files has been updated to enable subsequent results to be added to previous results ("append mode"). Results can now also be edited or deleted.
  • Implement Pure Virtuals enables a user to quickly create definitions for a class that inherits constructs (such as abstract class, struct) containing pure virtuals. Both multiple and recursive inheritances are supported. Activate the feature through right-clicking a class definition (implement all pure virtuals) or an inherited base construct (implement pure virtuals in that base only). Double-slash comments (//) are used to delimit groups of functions implemented from individual bases.
  • Move Function Definition enables a user to move the body of a function definition to source or header/in-class definition. It must be activated through the right-click context menu on a function's signature.
  • Create Declaration/Definition has been updated with Peek Definition and other bug fixes.
Collapse this imageExpand this image
Visual Studio IDE
Collapse this imageExpand this image
  • Menu Bars will show in Title Case style instead of All Caps style.
  • Support for touch in the Visual Studio Editor is now available. This includes touch for scrolling, pinch-to-zoom, tap-and-hold for context menus, double-tap for word selection, and line selection by tapping in the margin.
  • The Configuration and Platform dropdown values for the VC Property Page dialog have been changed to remember the last user selection when closed and reopened.
  • Users can save custom layouts by clicking Save Window Layout from the Window menu. Users can apply a custom layout by clicking Apply Window Layout from the Window menu, and users can delete, rename, or reorder layouts by clicking Manage Window Layout from the Window menu. The first nine layouts also have keyboard shortcuts from Ctrl+Alt+1 to Ctrl+Alt+9.
  • In this CTP, we are rounding out Light Bulbs that are the quick and easy way to obtain helpful fixes for known issues in your code inside the Visual Studio Editor. If you have an issue in your code, placing your editor caret on the line where the issue is shown or hovering over the issue will present a light bulb that shows helpful actions you can take to resolve the problem together with a preview of the results of each action.

    This feature is publicly extensible, so Visual Studio extenders can provide their own suggested actions.
  • After you apply this CTP, you can create an empty C# and JavaScript shared project from the File > New Project menu. Phone Projects, Store Projects, and Universal Projects that are written in JavaScript and C# can consume one or many of these shared projects. Shared project references can be managed (added or removed) by using the Reference Manager. Shared Project referencing is also available for some classic desktop C# projects. The project types and languages that support Shared Projects will continue to expand in future CTPs.
  • In this CTP, Visual Studio now supports high-resolution icons in the Error List.
Collapse this imageExpand this image
Collapse this imageExpand this image

Known issues

Collapse this imageExpand this image

Installation

Client Platform
Collapse this imageExpand this image
  • Uninstalling Visual Studio "14" CTP 2 removes TypeScript from Visual Studio 2013.
Collapse this imageExpand this image
Upgrading
Collapse this imageExpand this image
  • Because of a known issue, when you install Visual Studio "14" CTP 2 (version 14.0.21901.1.DP) on the same computer that has Visual Studio "14" CTP 1 (version 14.0.21730.1.DP) installed, your Windows Store projects may fail to launch. 

    To work around this issue, repair the installation of Visual Studio "14" CTP 2 (version 14.0.21901.1.DP) after the upgrade. To avoid this issue, our safest recommendation is to uninstall Visual Studio "14" CTP 1 (version 14.0.21730.1.DP) before you install the new CTP version. This build-to-build upgrade issue has been fixed for future upgrades from Visual Studio "14" CTP 2 (version 14.0.21901.1.DP).
Collapse this imageExpand this image
Visual C++
Collapse this imageExpand this image
  • The native "Memory Usage" tool does not work when targeting Win32 (x86). Targeting x64 works as expected.
Collapse this imageExpand this image
Collapse this imageExpand this image

More information

Collapse this imageExpand this image
How to download Microsoft support files  (http://support.microsoft.com/kb/119591/ )

Updates for other products in the Visual Studio family can be found on the Microsoft download site for Visual Studio (http://www.microsoft.com/visualstudio/eng/downloads) .

Products

Collapse this imageExpand this image
This Visual Studio "14" CTP 2 (version 14.0.21901.1.DP) release includes the following products: 
  • Microsoft Visual Studio Professional "14" CTP (web (http://go.microsoft.com/fwlink/?LinkId=401041) | iso (http://go.microsoft.com/fwlink/?LinkId=401042) )
  • Remote Tools for Visual Studio "14" CTP (x86 (http://go.microsoft.com/fwlink/?LinkId=401046) | x64 (http://go.microsoft.com/fwlink/?LinkId=401045) | arm (http://go.microsoft.com/fwlink/?LinkId=401044) )
  • Microsoft Visual Studio "14" SDK CTP (exe (http://go.microsoft.com/fwlink/?LinkId=401043) )
Collapse this imageExpand this image

Requirements

Collapse this imageExpand this image

Software requirements

On Windows 8.1 and Windows Server 2012 R2, Update 2919355 (http://support.microsoft.com/kb/2919355) (also available through Windows Update) is required for Visual Studio "14" 14.0.21901.1 DP to install successfully.

Restart requirement

You may have to restart your computer after you install this package.

Supported architectures

  • 32-bit (x86)
  • 64-bit (x64) (WOW)
  • ARM

Hardware requirements

  • 1.6 gigahertz (GHz) or faster processor
  • 1 gigabyte (GB) of RAM (1.5 GB if you are running in a virtual machine)
  • 2 GB of available hard disk space
  • 5,400 RPM hard disk drive
  • DirectX 9-capable video card that is running at a resolution of 1024 × 768 or higher
Collapse this imageExpand this image
Collapse this imageExpand this image
Collapse this imageExpand this image

Visual Studio "14" CTP 1 (version 14.0.21730.1.DP) details

Collapse this imageExpand this image

Technology improvements

Collapse this imageExpand this image
The following technology improvements have been made in this release.

ASP.NET and web development
Collapse this imageExpand this image
  • ASP.NET vNext: This release of Visual Studio supports creating and developing ASP.NET vNext applications. ASP.NET vNext is a lean and composable .NET stack for building modern web applications for both cloud and on-premises servers. It includes the following features:
    • ASP.NET MVC and Web API have been unified into a single programming model.
    • A no-compile developer experience.
    • Dependency injection out-of-the-box.
    • Side-by-side: Deploy the runtime and framework by using your application.
    • NuGet everything, even the runtime itself.
    • All open source is on the .NET Foundation, and takes contributions.
    For more information about ASP.NET vNext in Visual Studio, go to the ASP.NET vNext (http://go.microsoft.com/fwlink/?LinkId=400692) website.
  • This release of Visual Studio also includes all the current ASP.NET and web development features that are released as parts of Visual Studio 2013 Update 2. Learn more here (http://go.microsoft.com/fwlink/?LinkId=400693) .
Collapse this imageExpand this image
Managed languages
Collapse this imageExpand this image
  • The core IDE and editing experiences for C# and Visual Basic have been replaced with new experiences that are built on the .NET Compiler Platform "Roslyn." Generally, the experience should be unchanged. However, there are numerous small improvements.
  • C# refactoring support has been completely revamped. There are two new core refactorings: Inline Temporary Variable and Introduce Explaining Variable. Additionally, refactoring support for Visual Basic has been added for the first time.
  • You can use specific code-aware guidance for the Microsoft platforms and NuGet packages that you're targeting to obtain live code analysis and automatic fixes as you type.
Collapse this imageExpand this image
Visual C++
Collapse this imageExpand this image
  • Generalized lambda capture: You can assign the result of evaluating an expression to a variable in the capture clause of a lambda. This allows an instance of a move-only type to be captured by value.
  • User-defined literals in the language and standard library: You can append numeric and string literals with meaningful suffixes to give them suitable semantics. The compiler transforms these suffixes into calls to appropriate UDL-operator functions. The <chrono>, <string>, and <complex> headers now provide literal operators for convenience. For example, "1729ms" means std::chrono::milliseconds(1729), "meow"s means std::string("meow"), and 3.14i means std::complex<double>(0.0, 3.14).
  • Completed noexcept: You can check whether an expression will throw an exception by using the noexcept operator. For example, noexcept(func()) will return "true" if func was specified as noexcept.
  • Inline namespaces: You can specify a nested namespace as "inline" to make its contents accessed from its parent namespace.
  • Thread-safe "magic" statics: Static local variables are initialized in a thread-safe way, removing the need for manual synchronization. Be aware that usage of these variables other than initialization is still not protected. Thread safety can be disabled by using /Zc:threadSafeInit- to avoid a dependency on the CRT.
  • Unrestricted unions: You can define unions that contain types with non-trivial constructors. Constructors for such unions have to be manually defined.
  • Finally, all new C++ 11 and C++ 14 language features that are released in the November 2013 compiler CTP for Visual Studio 2013 are also included in this preview. For more information about these features, read this (http://blogs.msdn.com/b/vcblog/archive/2013/11/18/announcing-the-visual-c-compiler-november-2013-ctp.aspx) announcement. Briefly, these include the following:
    • __func__, extended sizeof, implicit move generation, ref-qualifiers ("&" and "&&" for member functions), alignof and alignas, and inheriting constructors.
    • auto function return type deduction, decltype(auto), and generic lambdas with a limitation of not using [=]/[&] default capture together with generic lambdas. This will be enabled also for generic lambdas in a future release.
    • Resumable functions and awaitproposed for the C++ Concurrency Technical Specification.
  • Null forward iterators: The Standard Library's forward iterators (and stronger) now guarantee that value-initialized iterators compare as equal. This makes it possible to pass an empty range without a parent container. Be aware that generally, value-initialized iterators still cannot be compared to iterators from a parent container.
  • quoted(): These manipulators let iostreams preserve strings that contain spaces.
  • Heterogeneous associative lookup: When it is Enabled by special comparators (such as the less<> and greater<> transparent operator functors), the ordered associative containers gain templated lookup functions. This lets them work with objects that are comparable to keys, without actually constructing keys.
  • integer_sequence: Compile-time integer sequences are now supported to make template metaprogramming easier.
  • exchange(): This small utility function makes it convenient to assign a new value to an object and retrieve the old value.
  • get<T>(): This lets a tuple element be accessed by its type (when unique) instead of by its index.
  • Dual-range equal(), is_permutation(), mismatch(): C++98's "range-and-a-half" algorithms that are taking (first1, last1, first2) are difficult to use correctly. While they are still provided, C++14 has added overloads taking (first1, last1, first2, last2) which are significantly easier and safer to use.
  • tuple_element_t: This alias template is added for convenience and consistency with the type traits alias templates.
  • Filesystem "V3" Technical Specification (TS): The interface and implementation of <filesystem> are overhauled to follow this TS, which is likely to be incorporated into C++17.
  • Library Issues: 24 resolutions have been implemented (for example, is_final, make_reverse_iterator()), not including the resolutions that were already implemented in Visual C++ 2013. Notice that a library issue is a bug report for the Standard. It can be resolved by fixing a specification problem or even adding a small feature.
  • <chrono> fixes: The clocks are rewritten to be conformant and precise.
  • Minimal allocator fixes: Several library components (including basic_string and std::function) did not work with user-defined allocators implementing C++11's minimal allocator interface, instead requiring C++03's verbose allocator interface. All occurrences of this problem are fixed.
  • C99 library features: Most of the remaining C99 library features are implemented.
    • snprintf is implemented.
    • The printf and scanf families of functions now support the new C99 format string improvements.
    • The strtod and scanf families of functions now support hexadecimal floating-point.
    • Library conformance is better improved by software updates and adjustments.
  • __restrict: The __restrict keyword is now supported on reference types in addition to pointer types.
  • Improved diagnostics: The compiler will now emit warnings about suspicious code that previously would not have resulted in warnings. For example, shadowed variables will now cause warnings. Warnings have also been made clearer.
  • The /Wv flag: You can use /Wv:XX.YY.ZZZZ to disable warnings that are introduced after compiler version XX.YY.ZZZZ. Notice that the emitted warnings may still differ from those emitted by the specified version.
  • Compiler software updates: We have fixed more than 400 bugs in the compiler. 179 of these were submitted by users through Microsoft Connect.
  • Refactored C Runtime (CRT): This CTP contains the first preview of the substantially refactored CRT.
    • msvcr140.dll no longer exists. It is replaced by a trio of DLLs: vcruntime140.dll, appcrt140.dll, and desktopcrt140.dll.
  • stdio performance: Many performance improvements are made in the stdio library, notably in the sprintf and sscanf families of functions.
  • Object file size reductions: Working together with compiler fixes, the STL's headers are changed to significantly reduce the sizes of object files and static libraries (that is after compilation but before linking. The sizes of linked EXEs/DLLs are unaffected). For example, when you compile a source file that includes all C and C++ Standard Library headers and does nothing else with them, for x86 with /MD /O2, Visual C++ 2013 generated a 731 KB object file. This is improved to be less than 1 KB.
  • Debug checking fixes: The STL's debug checks rejected null pointers that are passed as iterators, even when the Standard guaranteed that they should work (for example, merging two [null, null) ranges to a null output). Every algorithm is inspected and fixed.
  • Create declaration or definition: You can quickly create a function’s declaration or definition in relation to its neighbors. To do this, right-click the declaration or definition, or use SmartTags.
  • Debugger visualizers: Natvis debugger visualization files can be added to a Visual C++ project for easy management and source control integration. Natvis files that are added to a project will take evaluation precedence over visualizers outside the project.
  • Native memory diagnostics:
    • You can start a memory diagnostic session (Alt+F2) that monitors the live memory usage of your native application. This supports Windows Desktop.
    • You can capture heap snapshots of the running process in memory to see the types and instances for native allocations.
    • You can view the difference in memory allocations between two memory snapshots.
    • You can dive into the memory contents of a process snapshot by using the debugger for deeper analysis of the heap.
For the latest information about Visual C++, go to the Visual C++ team blog (http://blogs.msdn.com/b/vcblog) .
Collapse this imageExpand this image
Collapse this imageExpand this image

Known issues

Collapse this imageExpand this image

Functionality

Collapse this imageExpand this image

Visual C++
Collapse this imageExpand this image
  • Expression evaluation fails during native memory diagnostics when the Just My Code setting is turned on. Turning off this setting will allow expression evaluation to work correctly.
  • New Visual C++ language features in this release do not have full IntelliSense support in the Visual Studio editor.
  • The noexcept operator may fail in scenarios that involve complex templates.
  • Currently, user-defined literals may generate incorrect code under /CLR. Extremely large literals are not yet supported.
  • Code Analysis is not supported in this release of the compiler. If you try to build by using /analyze, the compiler will issue a warning, and will ignore the flag.
  • Building Windows Phone 8.1 apps by using Visual C++ is not yet supported.
  • Windows Store 8.1 applications that are written in Visual C++ and are built by using this preview compiler will not be validated by the Windows App Certification Kit, and these applications will rely on the Desktop DLLs instead of the "_app" versions of the DLLs that are used exclusively by Store applications. This will be fixed in future releases.
Collapse this imageExpand this image
General
Collapse this imageExpand this image
  • In this Visual Studio "14" CTP, the JavaScript Console and DOM Explorer diagnostic tools do not attach to either Windows Phone devices or the emulator. The tools have a blank display, and they are not functional. These tools cannot be used for debugging JavaScript/HTML in either phone applications or websites by using the Internet Explorer browser of the phone.
  • Because of a known issue, creating or opening Light Switch or Cloud Business App projects is not supported in Visual Studio "14" CTP 1. The team is working on a fix to resolve the issue.
  • When you includes SQLCLR C# code files to in SQL Server Database projects, Visual Studio may crash. To work around this issue, change the project to use Visual Basic by following these steps:
    • Right-click the SQL Server project, and then select Properties.
    • Select the SQLCLR tab.
    • In the Language list, select Visual Basic.
    • Save your project.
  • When you create a Database Unit Test from the Project node in SQL Server Object Explorer, you may receive the following error message:
    Could not load file or assembly 'Microsoft.SqlServer.Dac.dll' or one of its dependencies. The system cannot find the file specified.
    To work around this issue, load a database unit test project that was previously created in Visual Studio 2013.
  • This Visual Studio "14" CTP includes the Azure Mobile Services tooling features shipped as part of Visual Studio 2013 Update 2. However, the Push Notification Wizard, Services Manager, and Publishing to Mobile Services features do not work yet. This functionality will be addressed in the next Visual Studio "14" CTP release.
Collapse this imageExpand this image
ASP.NET and Web Development
Collapse this imageExpand this image
  • ASP.NET vNext cloud-optimized scenarios are limited to Windows 8 or a later version of Windows.
  • Debugging ASP.NET vNext applications targeting the cloud-optimized framework is not supported in this release.
Collapse this imageExpand this image
Collapse this imageExpand this image

Installation

Collapse this imageExpand this image
Installing Visual Studio "14" CTP 1 (version 14.0.21730.1.DP) side-by-side with Visual Studio 2013
Collapse this imageExpand this image
There are known issues when you install Visual Studio "14" CTP 1 (version 14.0.21730.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 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.

There is an installation block in this Visual Studio "14" CTP that will prevent installation on a computer on which an earlier version of Visual Studio is already installed. To disable the block (which will put the computer in a not-recommended state), add a new value to the registry at the "HKLM\SOFTWARE\Microsoft\DevDiv\vs\Servicing" location ("HKLM\SOFTWARE\Wow6432Node\Microsoft\DevDiv\vs\Servicing" on a 64-bit edition of Windows). The value name should be BlockerOverride, and the value type and value data can be anything.
Collapse this imageExpand this image
Collapse this imageExpand this image

Breaking changes

Collapse this imageExpand this image
Visual C++
Collapse this imageExpand this image
  • Improvements to the compiler’s error reporting may result in warnings that differ in order and specifics from those reported by earlier versions of the compiler.
  • User-defined literals are a new syntactic form, and may prevent some existing macros from being expanded. For example, "foo"_bar will be treated as a user-defined literal, even if _bar was defined as a macro.
  • The concatenation of adjacent wide or raw string literals (L"Hello"L"World") will require a space to be inserted (L"Hello" L"World") because the prefix for the second string is now treated as a user-defined literal suffix.
  • /CLR:pure and /CLR:safe are deprecated. The compiler will warn you about the use of these flags.
  • /CLR:OldSyntax, /Wp64, and /Zg flags have been removed.
Collapse this imageExpand this image
Collapse this imageExpand this image
Collapse this imageExpand this image

More information

Collapse this imageExpand this image
How to download Microsoft support files  (http://support.microsoft.com/kb/119591/ )

Updates for other products in the Visual Studio family can be found on the Microsoft download site for Visual Studio (http://www.microsoft.com/visualstudio/eng/downloads) .

Products

Collapse this imageExpand this image
This Visual Studio "14" CTP 1 (version 14.0.21730.1.DP) release includes the following products: 
  • Microsoft Visual Studio Professional "14" CTP (web (http://go.microsoft.com/fwlink/?LinkId=399011) | iso (http://go.microsoft.com/fwlink/?LinkId=399010) )
  • Remote Tools for Visual Studio "14" CTP (x86 (http://go.microsoft.com/fwlink/?LinkId=399015) | x64 (http://go.microsoft.com/fwlink/?LinkId=399014) | arm (http://go.microsoft.com/fwlink/?LinkId=399013) )
  • Microsoft Visual Studio "14" SDK CTP (exe (http://go.microsoft.com/fwlink/?LinkId=399012) )
Collapse this imageExpand this image

Requirements

Collapse this imageExpand this image

Software requirement

This software cannot be installed on a computer that has an earlier version of Visual Studio installed.

Restart requirement

You may have to restart your computer after you install this package.

Supported architectures

  • 32-bit (x86)
  • 64-bit (x64) (WOW)
  • ARM

Hardware requirements

  • 1.6 gigahertz (GHz) or faster processor
  • 1 gigabyte (GB) of RAM (1.5 GB if you are running in a virtual machine)
  • 2 GB of available hard disk space
  • 5,400 RPM hard disk drive
  • DirectX 9-capable video card that is running at a resolution of 1024 × 768 or higher
Collapse this imageExpand this image
Collapse this imageExpand this image
Collapse this imageExpand this image
Keywords: 
kbsurveynew kbexpertiseadvanced atdownload KB2967191
Share
Additional support options
Ask The Microsoft Small Business Support Community
Contact Microsoft Small Business Support
Find Microsoft Small Business Support Certified Partner
Find a Microsoft Store For In-Person Small Business Support