Visual Studio 2013 Update 5 (2013.5) RTMVisual Studio 2013 Update 5 (2013.5) RTM

于 2015 年 7 月 20 日发布Released on July 20, 2015

本文包含 Visual Studio 2013 和 Team Foundation Server 2013 Update 5 交付厂商版 (RTM) 的存档版本信息。This article contains archived release information for Visual Studio 2013 and Team Foundation Server 2013 Update 5 Release to Manufacturing (RTM).

**下载:**可以从下载页下载旧版 Visual Studio 2013。Download: You can download Visual Studio 2013 from the download page for older versions.

此更新是面向 Visual Studio 2013 的一系列累积技术改进和 Bug 修补程序。This update is a cumulative series of technology improvements and bug fixes for Visual Studio 2013. 定期更新使我们能够更为频繁地增强和扩展 Visual Studio 和 Team Foundation Server,以支持用于构建和管理现代应用的最新软件开发创新。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.

**注:**仅当前这一更新支持 Visual Studio 2013,也即 Visual Studio 2013 Service Pack。Note: Support for Visual Studio 2013 is only provided on this current update, which is considered the Visual Studio 2013 Service Pack. 此更新发布一年后,将提供对 Visual Studio 2013 RTM 版本(发布于 2013 年 11 月)的支持,且支持时间仅为一年。The Visual Studio 2013 RTM version, released in November of 2013, will only be supported for one year after the release of this update. 有关详细信息,请参阅 Microsoft 支持生命周期策略For more information, see the Microsoft Support Lifecycle Policy.

**另请注意:**用于 Apache Cordova 的工具的所有早期版本与 Update 5 不兼容。Also note: All prior releases of the Tools for Apache Cordova are incompatible with Update 5. 如果以前安装了用于 Apache Cordova 的工具 CTP 扩展,则必须先将此扩展卸载,才能安装 Visual Studio 2013 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. 如果需要 Apache Cordova 支持,我们建议你试用 Visual Studio 2015If you require Apache Cordova support, we encourage you to try Visual Studio 2015.

Visual Studio 2013 Update 5 中的新增功能What's new in Visual Studio 2013 Update 5

从全球范围的 Azure 数据中心进行基于云的负载测试Cloud-based load testing from Azure datacenters worldwide

使用 Visual Studio Team Foundation Service 设置运行负载测试所需的基础结构变得更加轻松:现在,你可以从全球范围的任何一个支持的 Azure 数据中心进行基于云的负载测试。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

现在可以使用 Visual Studio Online 或 Visual Studio Team Foundation Server 2015 中的 @currentIteration 令牌在 Visual Studio 中运行查询。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. 执行 get 或 check-in 将自动更正工作区映射,以便其使用新的团队项目名称。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 修复Bug Fixes

调试器Debugger

  • 现在支持在 9.3 版硬件上捕获深度缓冲区。Capturing depth buffers on version 9.3 hardware is now supported. 这为在 Windows Phone 上运行的基于 Unity 的图形调试应用程序提供了支持。This enables support for graphics debugging Unity-based applications that run on Windows Phone.

Visual Studio IDEVisual 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.
  • 生成需要 WinRT 注册的 Windows 应用商店应用程序时,在运行时将不再收到 System.TypeLoadException 异常。When you build a Windows Store application that requires WinRT registrations, you no longer receive the System.TypeLoadException exception at runtime.
  • 假设已将默认浏览器设置为 Windows 10 Insider Preview 中的 Spartan。Assume that you have set your default browser to Spartan on Windows 10 Insider Preview. 当在关键字或工具窗口上按 F1 时,可能会发现所有联机帮助电话失效,并无法获得任何联机帮助内容。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.
  • 如果以前曾连接到其他集合,除非重新启动 Visual Studio,否则无法分支。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 ServerTeam Foundation Server

  • 尝试使用团队资源管理器打开 SharePoint 文档时,名字包含太多 Unicode 字符的 SharePoint 文档不再出现打开错误的现象。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.
  • 在 Team Foundation Server 2013 Update 4 中,处于利益干系人许可证级别时,不能使用 Feedback Client 提交反馈。In Team Foundation Server 2013 Update 4, you cannot submit feedback by using Feedback Client when you are at the stakeholder license level. 然而在 Team Foundation Server 2013 Update 5 中,处于利益干系人许可证级别时,可使用 Feedback Client 提交反馈。However, in Team Foundation Server 2013 Update 5, you can submit feedback by using Feedback Client when you are at the stakeholder license level.
  • 当与 Web 访问中的另一用户同时更改工作项时,将不再遇到以下问题: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 ").
  • 在具有以前删除的子文件夹的循环重命名文件夹中,tf merge 命令不再冻结在 prc_PendMerge 中的无限循环中。The tf merge command no longer freezes in an infinite loop in prc_PendMerge for cyclically renamed folders that have previously deleted subfolders.
  • 作为 Git 用户,现在可针对托管在 TFS 实例上的 Git repo 执行浅表克隆注释标签。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.
  • 具有在白天保存时间外输入的“日期时间”字段值的工作项不再错误地显示在 Web 访问中。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.
  • 使用 TFS 备份工具还原数据库备份时,如果将 SQL Server 设置为其他位置,日志文件 (.ldf) 和数据文件 (.mdf) 将不再恢复到同一位置。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. 将该文件替换为错误文件后,可重新映射 Git 命令,以执行在凭据下运行的任意命令。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. 这种情况下,可能会将错误文件引入 Git 存储库。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.
  • 在 Web 访问中使用 TFS 时,我们改进了性能。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.
  • 如果具有可以防止 COM 在 CLR 启动期间注册的工具(如 Fusion logging),现在可禁用拉取请求,使作业代理正常运行。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.

当尝试从 Visual Studio 记录 Web 性能测试时,Internet Explorer 的 WebTest 记录器插件不会加载。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 CategoriesHKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\Discardable\PostSetup\Component Categories
  • HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\Discardable\PostSetup\Component Categories64HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\Discardable\PostSetup\Component Categories64

单元测试Unit Testing

当从早期版本升级到 Visual Studio 2013 Update 5 时,可能会发现将无法生成现有的单元测试应用程序 (Windows Phone) Visual C# 项目。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. 若要解决此问题,请修复 Visual Studio 2013 Update 5 安装。To work around this issue, repair the Visual Studio 2013 Update 5 installation.