Visual Studio 2013 Update 5 (2013.5) RTM

Last Update: 11/8/2017

Released on July 20, 2015

This article contains archived release information for Visual Studio 2013 and Team Foundation Server 2013 Update 5 Release to Manufacturing (RTM).

Download: You can download Visual Studio 2013 from the download page for older versions.

This update is a cumulative series of technology improvements and bug fixes for Visual Studio 2013. Periodic updates enable us to enhance and expand both Visual Studio and Team Foundation Server more frequently to support the latest software development innovations for building and managing modern apps.

Note: Support for Visual Studio 2013 is only provided on this current update, which is considered the Visual Studio 2013 Service Pack. The Visual Studio 2013 RTM version, released in November of 2013, will only be supported for one year after the release of this update. For more information, see the Microsoft Support Lifecycle Policy.

Also note: All prior releases of the Tools for Apache Cordova are incompatible with Update 5. If you have previously installed a Tools for Apache Cordova CTP extension, you must uninstall that extension before installing Visual Studio 2013 Update 5. If you require Apache Cordova support, we encourage you to try Visual Studio 2015.

What's new in Visual Studio 2013 Update 5

Cloud-based load testing from Azure datacenters worldwide

Setting up the infrastructure required to run load testing by using the Visual Studio Team Foundation Service just got easier: Now, you can perform cloud-based load testing from any of the supported Azure datacenters around the world.

Learn more about choosing a location for your load test.

Current iteration query token

You now can run queries in Visual Studio with the @currentIteration token on Visual Studio Online or Visual Studio Team Foundation Server 2015.

Learn more about the current iteration query token.

Team Project Rename support for Local Workspaces

We've included the ability to update local workspaces after a team project is renamed. Performing a get or check-in will automatically correct the workspace mapping so that it uses the new team project name.

Learn more about renaming a team project.

Bug Fixes

Debugger

  • Capturing depth buffers on version 9.3 hardware is now supported. This enables support for graphics debugging Unity-based applications that run on Windows Phone.

Visual Studio IDE

  • A critical notification in the Notification Hub may indicate that you must obtain or renew a developer license. If you dismiss this notice, and then you open another project, the critical notification appears again.
  • When you build a Windows Store application that requires WinRT registrations, you no longer receive the System.TypeLoadException exception at runtime.
  • Assume that you have set your default browser to Spartan on Windows 10 Insider Preview. When you press F1 on a keyword or a tool window, you may found all online help calls now fail and you cannot get to any online help content.
  • When you have been previously connected to another collection, you could not branch unless Visual Studio is restarted. With this Update this issue no longer exists.
  • With this update, you will no longer see an unhelpful message after attempting to check in a set of pending changes to a team project that was previously renamed.
  • Some edits are no longer lost in your server workspace for pending changes in the client.

Team Foundation Server

  • SharePoint documents that have names that contains too many Unicode characters no longer open incorrectly when you try to open them by using Team Explorer.
  • In Team Foundation Server 2013 Update 4, you cannot submit feedback by using Feedback Client when you are at the stakeholder license level. However, in Team Foundation Server 2013 Update 5, you can submit feedback by using Feedback Client when you are at the stakeholder license level.
  • When you change a work item simultaneously with another user in Web Access, you no longer experience one of the following issues:
    • A work item is saved successfully. However, if you changed the State field and you set the Reason field to a non-default value, the Reason field value is reverted to the default.
    • A work item is not saved and you receive a "Field 'State' cannot be empty" error message.
  • You are no longer blocked from using the warehouse when you have data that is identical except for differences in white space (for example, "Debug" and "Debug ").
  • The tf merge command no longer freezes in an infinite loop in prc_PendMerge for cyclically renamed folders that have previously deleted subfolders.
  • As a Git user, you can now perform a shallow clone of an annotate tag against a Git repo that is hosted on a TFS instance.
  • Work Items that have DateTime field values that are entered outside of the current daylight saving time period no longer appear incorrectly in Web Access.
  • When you restore database backups by using TFS backup tool, both the log file (.ldf) and data file (.mdf) are no longer restored to same location if SQL Server is set for different locations.
  • New performance improvements are made for reports such as "Build success over time," "Burndown dashboard," "Burndown and burn rate," and "Stories overview."
  • When you download changes in a remote repository, your configuration file is no longer replaced by a specially crafted file. Your configuration file resides outside the repository. By replacing this file with a bad file, the Git commands could be remapped in order to execute arbitrary commands that run under your credentials. In this situation, a bad file could be introduced to the Git repository.
  • If you have permission to view events, you can now receive team notifications if the creator of the team subscription does not have permission to view those events.
  • We have improved the performance when you use TFS in Web Access.
  • Pinned charts are now better displayed. The legend is no longer hidden and there is a better alignment of the charts.
  • Certain rules on work items that are related to their attachments and work item links now run correctly.
  • If you have a tool that prevents COM from registration during CLR startup (like Fusion logging), you can now disable pull requests in order to allow the Job Agent to run normally.

Known Issues

General

[NOTE!] Follow the steps in this section carefully. Serious problems might occur if you modify the registry incorrectly. Before you modify it, back up the registry for restoration in case problems occur.

The WebTest recorder plug-in for Internet Explorer does not load when it tries to record a web performance test from Visual Studio. To work around this issue, delete the following registry keys:

  • HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\Discardable\PostSetup\Component Categories
  • HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\Discardable\PostSetup\Component Categories64

Unit Testing

When you upgrade to Visual Studio 2013 Update 5 from an earlier version, you may found the existing Unit Test Application (Windows Phone) Visual C# projects will not build. To work around this issue, repair the Visual Studio 2013 Update 5 installation.