Article ID: 2933779 - View products that this article applies to.
Expand all | Collapse all

On This Page

Introduction

Microsoft released Visual Studio 2013 Update 3 Release Candidate (RC) on July 2, 2014. Visual Studio 2013 Update 3 RC includes the latest software updates, feature additions, and bug fixes.

More information about Visual Studio product updates is also available on the Visual Studio website.

How to obtain Visual Studio 2013 Update 3 RC

Visual Studio 2013 updates are cumulative releases. The following download links always point you to the latest update:If you do not have Visual Studio 2013 (original release version) and run one of these downloads, both Visual Studio 2013 and Update 3 RC are installed.

You can also view the full list of Visual Studio 2013 Updates.

Virus-free claim

Collapse this imageExpand this image
assets folding start collapsed
Microsoft scanned this file for viruses. Microsoft used the most current virus-detection software that was available on the date that the file was posted. The file is stored on security-enhanced servers that help prevent any unauthorized changes to the file.
Collapse this imageExpand this image
assets folding end collapsed

How to install Visual Studio 2013 Update 3 RC

For installation guidance for Visual Studio products, see the following articles:

How to install Visual Studio

How to install Team Foundation Server and Visual Studio ALM

How to install Release Management for Visual Studio 2013
Important This update applies to Visual Studio and Team Foundation Server (TFS). Visual Studio and TFS installation mechanics are different. The Visual Studio update is installed on top of whatever is already installed on the computer. The TFS update is a full layout that replaces whatever is installed on the computer. Before you apply the TFS update, make sure that you have a full backup of your current databases. If the TFS update installation fails, you cannot restart the update or roll back to the earlier version of TFS without performing a restore.

The Release Management update is a full layout that includes the latest feature additions and bug fixes for Release Management for Visual Studio 2013. Before you try to apply the Release Management update, make sure that you have a full backup of your current databases and RSA crypto key (see this blog post for RSA crypto keys export instructions). If the Release Management update installation fails, you will be unable to restart the update or roll back to the earlier version of Release Management without performing a restore operation.

The following upgrade paths apply to this release.

Supported upgrades
  • Release Management for Visual Studio 2013 to Release Management for Visual Studio 2013 Update 3 RC
  • Release Management for Visual Studio 2013 Update 1 to Release Management for Visual Studio 2013 Update 3 RC
  • Release Management for Visual Studio 2013 Update 2 to Release Management for Visual Studio 2013 Update 3 RC

New technology improvements in Visual Studio 2013 Update 3 RC

Technology improvements

The following technology improvements were made in this release.

CodeLens
Collapse this imageExpand this image
assets folding start collapsed
  • CodeLens jobs that are running on the Team Foundation Server job agent have been optimized for performance specifically when you process branching and merging changesets. 
  • Team Foundation Server Administrators can now use the TFSConfig CodeIndex /ListLargeFiles command to identify large files. These files can be added to the ignore list and therefore reduce the time that is spent in CodeLens jobs.
  • When you work with source control in Git and work items in TFS, you can view the CodeLens work items indicators for Git to obtain information about the work items associated with a method, property, or class.
  • The Git collaboration indicators may take some time to show-up if big repositories contain many changes. The progress in computing the information for the indicators is now reported. 
Collapse this imageExpand this image
assets folding end collapsed
Debugger
Collapse this imageExpand this image
assets folding start collapsed
  • If you have more than one monitor, Visual Studio will remember which monitor a Windows Store application was last run on.
  • You can debug x86 applications that are built by .NET native.
  • When you analyze managed memory dump files, you can go to Definition and Find All References for the selected type. 
  • You can debug the dump files from .NET Native applications by using Visual Studio debugger.
Collapse this imageExpand this image
assets folding end collapsed
Team Foundation Server
Collapse this imageExpand this image
assets folding start collapsed
  • You can select to show or hide the In Progress items in the backlog.
  • You can traverse the group hierarchy when you administer group management or security.
Collapse this imageExpand this image
assets folding end collapsed
General
Collapse this imageExpand this image
assets folding start collapsed
  • The Application Insights Tools for Visual Studio are now included in Visual Studio 2013 Update 3 RC. This initial integration as part of RC includes some software updates and performance improvements.
  • The Application Insights Tools for Visual Studio includes improved Application Monitoring Setup.
  • Application Insights account setup now creates accounts in the new preview portal on Azure, and does not create or require a Visual Studio Online account.
  • Support SHA256 certificates on the .NET Framework 4.0 in ClickOnce:

    You can use SHA 256 code-signing certificates even for applications that target the .NET Framework 4.0 or an earlier version. Before this update, the .NET Framework 4.5 had to be present on the client computer when a SHA 256 code-signing certificate was used for desktop applications published with ClickOnce or Visual Studio Tools for Office add-ins. If you have used SHA 256 code-signing certificates in the past, and have seen errors such as "The application is improperly formatted," "The manifest may not be valid," "Manifest XML signature is not valid," or "SignatureDescription could not be created for the signature algorithm supplied," this update resolves the problem for re-published and newly-published applications.
  • Autohosting is no longer an option for SharePoint:

    The Autohosted option is removed from the SharePoint application creation experience, because the Office 365 Autohosted Apps Preview program ended on June 30. New autohosted applications for SharePoint are no longer accepted by the SharePoint store. Existing autohosted apps are not affected, and apps that are currently running in the service will not be shut down. For more information about the update on the Autohosted Apps Preview program, go to the following website:
    Update on Autohosted Apps Preview program
Collapse this imageExpand this image
assets folding end collapsed
IntelliTrace
Collapse this imageExpand this image
assets folding start collapsed
  • You can skip straight to the details of performance events that are exported from Application Insights to IntelliTrace.
Collapse this imageExpand this image
assets folding end collapsed
Profiler
Collapse this imageExpand this image
assets folding start collapsed
  • The Performance and Diagnostics hub can open profiling sessions (.diagsession files) that were exported from the F12 tools in the latest developer preview of Internet Explorer 11.
  • Windows Presentation Foundation (WPF) and Win32 applications are supported by the new Memory Usage Tool in the Performance and Diagnostics hub. For more information about how to use the tool to troubleshoot issues in native and managed memory, go to the following blog post:
    Diagnosing memory issues with the new Memory Usage Tool in Visual Studio
  • The CPU Usage tool in the Performance and Diagnostics hub now enables you to move from a function name in the Call Tree to the line of source code where that function is defined so that you can easily see the code that is using CPU in your application.
Collapse this imageExpand this image
assets folding end collapsed
Release Management
Collapse this imageExpand this image
assets folding start collapsed
  • You can use Windows PowerShell or the Windows PowerShell Desired State Configuration (DSC) feature to deploy and manage configuration data. Additionally, you can deploy to the following environments without having to set up Microsoft Deployment Agent:
    • Microsoft Azure environments
    • On-premises environments (standard environments)
  • You can use Release Management to trigger deployments to Chef-managed environments.  
  • You can use Release Management to track work items changes in a release.
Collapse this imageExpand this image
assets folding end collapsed
Testing Tools
Collapse this imageExpand this image
assets folding start collapsed
  • You can add custom fields and custom work flows for test plans and test suites.
  • You can use Manage Test Suites permission for granting access to test suites.
  • You can track changes to test plans and test suites by using work item history.

    For more information about these features, see the following Visual Studio Developer Tools blog article:
    Test Plan and Test Suite Customization with TFS2013 Update3
  • Cloud-based load testing with Application Insights

    You do not have to use resources and set up your own computers to do load testing on your website. You can use cloud-based load testing to provide virtual machines that generate the load of many users accessing your web site at the same time. When you run your load tests for your application by using Visual Studio Online, you can use Application Insights to retrieve performance data. By correlating load and performance data together, you can access more insight into any performance issues that you find.

    By using Visual Studio 2013 Update 3, you are no longer limited to a small set of Application counters that will be monitored together with the load run. Now you can select any performance counters from Application Insights that you want to view with your load run. Obtain the performance counters by using the following option:

    Collapse this imageExpand this image
    Step1

    And now you can select the application counters that you want to view during the load run.

    Collapse this imageExpand this image
    Step2


    These counters start appearing in the graphs when you do the load run.
    Collapse this imageExpand this image
    Step3
Collapse this imageExpand this image
assets folding end collapsed
Visual Studio IDE
Collapse this imageExpand this image
assets folding start collapsed
  • CodeLens authors and changes indicators are now available for Git repositories.
  • In Code Map, links are styled by using colors, and they are displayed in the improved Legend.
  • Debugger Map automatically zooms to the call stack entry of interest and preserves user's zoom preferences.
  • You can drag binaries from the Windows file explorer to a code map, and then start exploring binaries by using Code Map.
  • IntelliSense support for RequireJS modules in JavaScript language service.
Collapse this imageExpand this image
assets folding end collapsed
Visual C++
Collapse this imageExpand this image
assets folding start collapsed
  • Support is enabled for the /d2Zi+ internal compiler switch that provides better debugging information for Optimized builds (non- /Od builds).
  • You can now configure capture options in the Graphics Diagnostics page by clicking Tools and then clicking Options.
  • When you analyze frames in Graphics Diagnostics session, the frames will be opened in a separate environment that is Visual Studio Graphics Analyzer.
  • You can edit shader code and apply changes to the VSGLOG file that contains the captured frame to view the effect without having to rerun the application.
Collapse this imageExpand this image
assets folding end collapsed
Web platform and Tools
Collapse this imageExpand this image
assets folding start collapsed
    Microsoft ASP.NET and Web Tools 2013.3
    • Scaffolding: Support for ASP.NET 5.2 technologies (MVC, Web API)
    • JSON editor: Auto-formatting and brace matching
    • CSS editor: Selectors level 4 and drag-and-drop of fonts, images and other .css files

    ASP.NET MVC 5.2 RC
    • Attribute routing improvements
    • Feature updates
    • Bug fixes

    ASP.NET Web API 2.2 RC
    • OData v4 support
    • Attribute routing improvements
    • Web API Client support for Windows Phone 8.1
    • Feature updates
    • Bug fixes

    ASP.NET Web Pages 3.2 RC
    • Minor feature update
    • Bug fixes

    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.

    Microsoft OWIN Components
    • You can download the latest version of Microsoft OWIN Components from the NuGet gallery. For more information about the roadmap and features, go to this website.

    ASP.NET SignalR
    • You can download the latest version of SignalR from the NuGet gallery. For more information about the latest release, go to this website.

    Entity Framework 6.1.1
    • Microsoft released EF 6.1.1 in this update. For more information, go to this blog post.

    WebDeploy 3.5 refresh
    • We 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.

Collapse this imageExpand this image
assets folding end collapsed

Fixed issues

Debugger
Collapse this imageExpand this image
assets folding start collapsed
  • Visual Studio 2013 64-bit debugger (Msvsmon.exe) crashes on breakpoint when an array is too large.
  • Build fails because the PDB file is locked in Visual Studio 2013.
  • Visual Studio "14" cannot open a test project that is created in Visual Studio 2013 when the .suo file of the project contains parallel or tasks windows settings.
  • Exceptions or Visual Studio error when you remotely debug a project by using DataSet, DataTable Visualizer, or WPF Tree Visualizer.
  • When you view the content of dte.Debugger.CurrentStackFrame.Locals by using Visual Studio 2013, the output window does not obey the specified formatting but always displays the returned value in Hexadecimal characters.
Collapse this imageExpand this image
assets folding end collapsed
Team Foundation Server
Collapse this imageExpand this image
assets folding start collapsed
  • You may experience a time-out issue when you save work items in TFS 2013.
  • In high DPI, work item editor icons are scaled incorrectly. .
  • The Team Foundation Server Excel Add-in may become disabled when you click Reporting in Excel 2013.
  • The Team Foundation Server metadata cache may grow large with work item open, update, or query operations.
  • You may receive the following error message when you create a new Code Review Request:
    Could not save work item 0: Microsoft.TeamFoundation.WorkItemTracking.Client.ValidationException: TF237165: Team Foundation could not update the work item because of a validation error on the server. This may happen because the work item type has been modified or destroyed, or you do not have permission to update the work item.
  • Team Project creation may fail, and you receive the following error message:
    processColumnCallback was already added to this payload
  • Concurrent builds of the same Git repository may fail.
  • When large build drops are being deleted, build machines cannot process builds.
  • TfsBuildServiceHost.exe may crash because of a failure to delete build drops.
  • Build warnings in build logs may become so large that they can not be rendered in Visual Studio. You have to turn off warning logging in Visual Studio.
  • When you use the UpgradeTemplate, builds do not associate commits with work items.
  • When you queue a build in Team Foundation Server Web Access, the MSBuild arguments field in the queue dialog box is always empty, even when arguments are specified on the definition.
  • When you have a build definition set up to monitor a branch under Git source control, and you unpublish or delete a remote branch, the unpublish or delete operation triggers a build that will fail.
  • Assume that you have upgraded from SQL Server 2008 R2 to SQL Server 2012. When you try to configure Scheduled Backups by using SQL Server Reporting Services, a failure occurs in the Scheduled Backups wizard.
  • Decrease in performance for work item tracking when you use SQL Server 2014.
  • Connection problems after an upgrade when you use Kerberos authentication.
  • Team Foundation Server upgrade may fail if you do not run remapdbs before the upgrade.
  • Going to the job history page (_oi/_jobMonitoring#_a=history) fails.
  • Scheduled Backups may report an incorrect status. Jobs that succeed may show as failed and jobs in progress may report success.
  • When you upgrade from earlier versions of Team Foundation Server, you may see errors in the event log that the FileContent Migration failed.
  • You cannot create new Team Project Collections when you enable the AlwaysOn Availability Groups feature in SQL Server.
  • Scheduled Backups may report an incorrect status. Jobs that succeed may be displayed as failed and jobs in progress may report success.
  • An error occurs after you complete the form and then click OK when you run tf shelve or tf checkin. The data in the dialog box is lost.
  • Using the default database retention policy may cause database space to run out.
  • Scheduled builds may run an hour early after daylight saving time.
  • Team Foundation Server upgrade may fail because the job agent does not stop.
  • When you leave a Code Review page and return to it later, you may receive a "Field 'Area Path' cannot be empty" error message even if the Area Path is entered.
  • You cannot access shelvesets that are owned by users who have a forward slash (/) in their display names.
  • Errors occur during creation of a website project when Git is the active source control provider.
  • Pending Changes produced by tf merge may be incorrect because of duplicate rename sources.
  • You cannot import or export Git settings.
Collapse this imageExpand this image
assets folding end collapsed
Visual C++
Collapse this imageExpand this image
assets folding start collapsed
  • "Error C2893: Failed to specialize function" when you use a using declaration in a Visual C++ project in Visual Studio 2013.
  • The compiler crashes when you compile the code that contains templated or namespaced default arguments in Visual Studio 2013.
  • The compiler crashes when casting function pointer defined by variadic template in Visual Studio 2013.
  • The compiler crashes when you explicitly call variadic cast operator in a Visual C++ project in Visual Studio 2013.
  • Variadic templates fail on dependent types that begin with "::" when you compile a Visual C++ project.
  • Reduces some CX binaries size in Visual Studio 2013.
  • Error C1001 in Visual C++ compiler when you use variadic templates intensively.
Collapse this imageExpand this image
assets folding end collapsed
Visual Studio IDE
Collapse this imageExpand this image
assets folding start collapsed
  • You can disable the All Caps option on the menu bar on the Tools > Options > Environment > General page. This setting automatically roams across all computers where you are signed in.
Collapse this imageExpand this image
assets folding end collapsed
Web Platform and Tools
Collapse this imageExpand this image
assets folding start collapsed
  • Razor syntax checking within Javascript block works incorrectly in Visual Studio 2012 Update 3.
  • View in browser does not load the correct URL for MVC pages when you use Azure Emulator.
Collapse this imageExpand this image
assets folding end collapsed

Known issues

Testing Tools
Collapse this imageExpand this image
assets folding start collapsed
  • If the SQL Server that is used by TFS 2013 Update 3 is running on TRK Windows Server, Test Management Warehouse Sync Job fails. This makes Test Management reports unusable.

    To work around this issue, use SQL Server that is running on an ENU Windows Server or wait for the TFS 2013 Update 3 RTW release. If you have already installed or upgraded to TFS 2013 Update 3 and you are encountering this issue, contact Microsoft Customer Service and Support (CSS) for help.  
Collapse this imageExpand this image
assets folding end collapsed
Visual Studio IDE
Collapse this imageExpand this image
assets folding start collapsed
  • In Visual Studio 2013 Ultimate Update 3 RC localized (non en-us) drops, when you try to request a Code Map or a Dependency Graph for the solution, the directed graph is not produced.
Collapse this imageExpand this image
assets folding end collapsed
Web Platform and Tools
Collapse this imageExpand this image
assets folding start collapsed
  • After you repair Visual Studio Update 3, or install another SKU of Visual Studio together with Visual Studio Update 3 in the computer, ASP.NET and Web Tools will be removed.

    To bring ASP.NET and Web Tools back, uninstall Visual Studio Update 3, repair Visual Studio RTM, and then reinstall the Visual Studio Update 3.
Collapse this imageExpand this image
assets folding end collapsed
Release Management
Collapse this imageExpand this image
assets folding start collapsed
  • The "Change summary" view to see the user stories and bugs is supported only for ENU version of TFS.
  • The vNext release pipeline differs from the Deployment Agent-based release pipeline. The vNext release pipeline has the following feature differences:
    • Extending the target stage, tags-based deployment, and manual intervention are not supported yet.
    • Stages in vNext release paths must be of either the Azure environment or the on-premises (standard) environment type. A given release path cannot have both kinds of environment.
Collapse this imageExpand this image
assets folding end collapsed

More information

How to download Microsoft support files

Updates for other products in the Visual Studio family can be found on the Microsoft download site for Visual Studio.

Requirements

Collapse this imageExpand this image
assets folding start collapsed

Restart requirement

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

Supported languages

Visual Studio 2013 Update 3 RC provides updates for the following versions:
  • Chinese (Simplified)
  • Chinese (Traditional)
  • Czech
  • English
  • French
  • German
  • Italian
  • Japanese
  • Korean
  • Russian
  • Polish
  • Portuguese (Brazil)
  • Spanish
  • Turkish

Supported operating systems

For more information about supported operating systems, go to the following Microsoft website:
Platform compatibility and system requirements for Visual Studio 2013

Supported architectures

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

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)
  • 1 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

Software requirements

To apply this update, you must have one of the supported Visual Studio 2013 programs that are listed in the "Applies to" section installed.

Support for Visual Studio 2013 Update 3 RC

Informal community support for Visual Studio 2013 Update 3 RC is available through the Microsoft Developer Network (MSDN) forums.
Collapse this imageExpand this image
assets folding end collapsed

Properties

Article ID: 2933779 - Last Review: July 2, 2014 - Revision: 7.1
Applies to
  • Microsoft Visual Studio Ultimate 2013
  • Microsoft Visual Studio Professional 2013
  • Microsoft Visual Studio Premium 2013
  • Microsoft Visual Studio Express 2013 for Web
  • Microsoft Visual Studio Express 2013 for Windows
  • Microsoft Visual Studio Express 2013 for Windows Desktop
Keywords: 
kbfix kbsurveynew kbexpertiseadvanced atdownload KB2933779

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com