Visual Studio 2015 Update 3 发行说明Visual Studio 2015 Update 3 Release Notes


此版本不是最新版本的 Visual Studio。This is not the latest version of Visual Studio. 若要下载最新版本,请访问 Visual Studio 2017 的当前发行说明To download the latest release, please visit the current release notes for Visual Studio 2017.

下载 Visual Studio 2015Download Visual Studio 2015

可在 上下载 Visual Studio 的早期版本。这是基于订阅的网站,但任何人均可创建一个免费的 Dev Essentials 订阅。Downloads for earlier versions of Visual Studio are available on This is a subscription-based site, but anyone can create a free Dev Essentials subscription. 请参阅 Dev Essentials 页,了解详细信息。Please see the Dev Essentials page for more information.

发布日期:2016 年 6 月 27 日Release Date: June 27, 2016

此版本中的新增功能What's New in this Release

适用于 Apache Cordova 的工具Tools for Apache Cordova

Visual Studio 2015 Update 3 包括适用于 Apache Cordova Update 10 的工具,包括以下改进。Visual Studio 2015 Update 3 includes Tools for Apache Cordova Update 10, including the improvements below. Update 10and Update 10. 有关我们工具的最新新闻,请访问 GitHub 上的开发人员博客For the latest news about our tools, visit our Developer Blog on GitHub.

  • 我们添加了对 Cordova 6.1.1 的支持,这是新项目的默认版本。We've added support for Cordova 6.1.1, the default version for new projects.
  • 我们已停用曾在 Cordova 4.x 中使用的 Cordova 插件注册表,这意味着现在要添加插件,至少需要 Cordova 5.x 或更高版本。We've retired the Cordova Plugin Registry that was used in Cordova 4.x, which means that we now require a minimum of Cordova 5.x or later to add plugins.
  • 更新了核心插件列表,现在包含了用于企业方案的插件,例如 Intune、Azure Engagement、安全性和 SQLite 本地存储。The Core Plugins list has been updated and now includes plugins for enterprise scenarios, such as Intune, Azure engagement, security, and SQLite local storage.
  • 现在你可以按 npm 包名称或按 ID 从配置设计器添加插件。You can now add plugins from the config designer either by the npm package name or by the ID.


  • 你也可以从配置设计器添加需要参数的插件。You can also add plugins that require parameters from the config designer.


开发人员分析工具 Developer Analytics Tools

我们在开发人员分析工具 v7.0.2 中添加了已下改进:We've added the following improvements in Developer Analytics Tools v7.0.2:

  • Application Insights Trends 是一个在你的应用的遥测中查找趋势的工具。Application Insights Trends, a tool for finding trends in your app's telemetry.
  • CodeLens 中的异常遥测。Exception telemetry in CodeLens.
  • 将生产遥测信息添加到诊断工具中的异常。Production telemetry information added to exceptions in Diagnostic Tools.
  • 支持将 Application Insights 从 Visual Studio 添加到 ASP.NET 核心 RC2 项目。Support for adding Application Insights to ASP.NET Core RC2 projects from Visual Studio.
  • 用于 ASP.NET 5 RC1 和 ASP.NET 核心 RC2 项目的诊断工具事件。Diagnostic Tools events for ASP.NET 5 RC1 and ASP.NET Core RC2 projects.
  • 选中详细信息筛选器、时间范围和事件时,自动刷新 Application Insights 搜索。Automatic refreshes of Application Insights Search when detail filters, time ranges, and events are selected.
  • 在搜索中从请求转到代码。Go to Code from requests in Search.
  • 改进了 HockeyApp 登录体验。Improved HockeyApp sign-in experience.

有关详细信息,请参阅 Microsoft Azure 文档中的技术发行说明For more information, see the technical release notes in the Microsoft Azure documentation.

调试和诊断 Debugging and Diagnostics

在 OneCore 设备上运行的诊断工具应用支持(包括 HoloLens 和 IOT)已添加到 Update 3 中。Diagnostic Tools support for apps running on OneCore devices, including HoloLens and IOT, has been added in Update 3.

“C++ 编辑并继续”改进:C++ Edit and Continue improvements:

  • 启用 FASTLINK 时,性能和可靠性提升。Better performance and reliability when FASTLINK is enabled.
  • 成功向不再生成陈旧代码的静态库应用代码更改。Successful application of code changes to static libraries no longer produces Stale Code.
  • 对于重新编译期间产生的类型更改误报,不再显示 C4656 警告。C4656 warnings will no longer appear for false positive type changes during recompilation.
  • 支持跨多个编译单位添加一个具有同一名称的新类型。Support for adding a new type with the same name crossing multiple compilation units.

XAML UI 调试改进:XAML UI Debugging improvements:

  • 每当应用中的焦点发生变动,实时可视化树中的全新“跟踪焦点”功能将使实时可视化树中的选中内容更新到当前具有焦点的元素。Whenever the focus changes in your app, the new Track Focus feature in the Live Visual Tree will cause selection in the Live Visual Tree to update to the currently focused element.

Visual Studio IDE Visual Studio IDE

订阅和产品密钥Subscriptions and product keys

我们在 Update 3 中解决了一些客户所反馈的问题(这些客户通过联机标识或产品密钥解锁 IDE 来使用订阅),使用的方法如下:We've addressed feedback in Update 3 from customers using subscriptions through an online identity or product keys to unlock the IDE, in the following ways:

  • 不再需要访问 来激活已分配的 Visual Studio 云订阅,并且可以在分配了订阅后立即开始使用 Visual Studio IDE。You are no longer required to visit to activate your assigned Visual Studio Cloud subscription, and can immediately start using the Visual Studio IDE as soon as the subscription is assigned.
  • 我们改进了应用产品密钥时的错误处理效果。We've improved error handling when applying a product key.
  • 所有用户帐户和授权操作现在使用 HTTPS 进行保护。All user account and licensing operations are now secured by using HTTPS.
  • 对于用于激活订阅和输入产品密钥的“帐户设置”对话框,我们进行了可访问性方面的改进。We've made accessibility improvements in the Account Settings dialog for activating a subscription and entering a product key.
  • 不再要求每隔 8 天重新进行身份验证以保持个性化帐户处于活动状态并同步漫游设置。Re-authentication every ~8 days is no longer required to keep the personalization account active and synchronizing roaming settings.

适用于通用 Windows 应用的工具 Tools for Universal Windows Apps

Visual Studio 2015 Update 3 中对用于通用 Windows 应用的工具进行了一定程度的功能提升。Visual Studio 2015 Update 3 comes with several enhancements to the Tools for Universal Windows apps. 一项重要的改进是:创建要提交到 Windows 应用商店的包时,可以使用 AAD 应用商店帐户的 Azure Active Directory 凭据进行登录。A key improvement allows you to sign in with Azure Active Directory credentials for an AAD Store account when creating a package to submit to the Windows Store. 项目一旦与 Windows 应用商店关联后,无需再进行登录便可创建包以提交到存储区。Once the project has been associated with the Windows Store, you will no longer need to sign in to create a package to submit to the Store.

适用于通用 Windows 应用的 .NET Native.NET Native for Universal Windows Apps

.NET Native 1.4 是次要服务版本,可以提高性能、解决几个用户报告的 Bug,以及改善大型应用的版本生成编译时间。.NET Native 1.4 is a minor servicing release that improves performance, addresses several customer reported bugs and improves Release build compilation times of large apps. XAML 应用程序和使用 .NET Native 1.4 的 Unity 游戏将具有更好的运行时性能。XAML applications and Unity games that use .NET Native 1.4 will have better runtime performance. 这些改进通过加速反射和本机 API 调用的运行来实现。These improvements were achieved by making both reflection and native API calls faster.

体系结构工具 Architecture Tools

我们已经解决了客户对提高性能和稳定性的反馈。We've addressed feedback from customers about improving performance and reliability.

域特定图形设计器(包括 EDMX 和 DBML)Domain Specific Graphical Designers (including EDMX and DBML)

在 Windows 10 中,如果在显示屏幕键盘的同时打开或尝试编辑大型 EDMX 或 DBML 图,则 Visual Studio 可能不再无响应。On Windows 10, Visual Studio is no longer unresponsive when you are opening or attempting to edit large EDMX or DBML diagrams while the on-screen keyboard is displayed.

代码图Code Map

  • 尝试“生成解决方案的代码图”,且解决方案包含安装程序项目 (.vdproj) 时,Visual Studio 不再无响应。Visual Studio is no longer unresponsive when you are trying to "Generate Code Map for Solution" when the solution contained installer projects (.vdproj).
  • 从代码编辑器运行代码映射命令以及在“代码图”窗口出现时立即关闭它时,Visual Studio 不再无响应。Visual Studio is no longer unresponsive when you run a code map command from the code editor and close the Code Map window as soon as it appears.

层验证Layer Validation

  • 在使用验证操作构建一个解决方案,且该方案具有一个包含层关系图的建模项目时,在构建完成后 CPU 内核将不再使用。When building a solution having a modeling project containing a Layer diagram with a Validate action, a CPU core is no longer used after the build completes.
  • 如果层关系图的父级建模项目引用了 PCL 库(如 ODP.Net),则现在可以对其进行验证。You can now validate a layer diagram when its parent modeling project is referencing PCL libraries (for instance ODP.Net).

适用于 Visual Studio 的 Node.js 工具Node.js Tools for Visual Studio

适用于 Visual Studio 的 Node.js 工具 1.2 RC 现已可供下载Node.js Tools 1.2 RC for Visual Studio is now available for download. 我们预期该版本将提供显著提升的稳定性和性能,包括减少在较早版本中出现的内存不足崩溃的问题。We expect this release to provide significantly improved stability and performance, including reducing out-of-memory crashes seen in prior releases.

其他要点包括:Other highlights include:

  • 更快、更好的 ES6 IntelliSenseFaster, better ES6 IntelliSense
  • 更可靠的调试More reliable debugging
  • 改进的单元测试体验(包括磁带支持)Improved Unit Testing experiences (including Tape support)
  • 在多个项目类型中的 .npm 命令.npm command in more project types

有关完整信息和下载,请参阅 Node.js Tools 1.2 RC release page(Node.js 工具 1.2 RC 发行页)。For full information and downloads, see the Node.js Tools 1.2 RC release page.

Web 开发人员工具 Web Developer Tools

对于 ASP.NET Web 应用程序项目,如果未勾选“启用编辑并继续”复选框,每当你停止调试时,IIS Express 进程将不再停止。For ASP.NET Web Application projects, when "Enable Edit and Continue" checkbox is unchecked, the IIS Express process will no longer stop every time you stop debugging.

Visual C++ Visual C++

增强功能(如新的检查和 c + + 编译器的警告消息以及对 C# 和 Visual Basic 代码的支持和性能改进)均包含在 Update 3 中。Enhancements, such as new checks and warning messages for the C++ Compiler, as well as support and performance improvements for C# and Visual Basic coding, were included in Update 3.

C++ 编译器C++ Compiler

  • 我们现在会检查已删除的普通复制/移动 ctor 的访问权限。We now check the access of a deleted trivial copy/move ctor. 如果不进行这项检查,我们可能会错误地调用默认的复制 ctor(其中的实现可能格式不正确),并可能导致运行时代码生成错误。Without the check, we may incorrectly call the defaulted copy ctor (in which the implementation can be ill-formed) and cause potential runtime bad code generation.
  • 现在,当复制构造函数被删除或为私有时,Std::is_convertible 将会正确检测到类类型的自我赋值。Std::is_convertible now correctly detects self-assignment of a class type when the copy-constructor is deleted or private.
  • 当弃用特性化 ATL 支持这一操作的最后阶段在 Visual Studio 2008 中启动时,我们已向编译器添加了新的弃用警告。As the last phase of completing the deprecation of attributed ATL support started in Visual Studio 2008, we've added a new deprecation warning to the compiler. 通过 Visual Studio 2015 Update 3,特性化 ATL 代码的使用将生成默认启动的 1 级警告。With Visual Studio 2015 Update 3, usages of attributed ATL code will generate an on-by-default level 1 warning. C4467C4467
  • 使用 PCH 文件时,如果在 -Yc 和 -Yu 编译之间错误地将 -I 包含目录与编译器匹配起来,将触发一个新的警告。When using PCH files, mismatched -I include directories to the compiler between -Yc and -Yu compilations will now produce a new warning. C4599C4599
  • 使用 PCH 文件时,如果在 -Yc 和 -Yu 编译之间错误地将源文件中的 #包含指令匹配起来,将触发一个新的警告。When using PCH files, mismatched #include directives in source files between -Yc and -Yu compilations will now produce a warning. C4598C4598

有关这些更改可能会如何影响你的现有代码的详细信息,请参阅 MSDN 上的 Visual C++ 移植和升级指南For more information on how these changes might impact your existing code, see Visual C++ Porting and Upgrading Guide on MSDN.

C++ 库C++ Libraries

  • 我们恢复了销毁 Update 2 中回归的一系列普通项目时的调试模式性能,与向量中类似。We've restored debug mode performance when destroying ranges of trivial objects that regressed in Update 2, like in vector.

  • 我们实现了提案 P0185 Adding [nothrow-]swappable traits 中 C++17 工作文件中的可交换特点。We've implemented the swappable traits from the C++17 working paper, from the proposal P0185 Adding [nothrow-]swappable traits. 作为推理 C++17 功能,当使用 /std:c++latest 进行编译时,这些特点(is_swappableis_swappable_withis_nothrow_swappableis_nothrow_swappable_with)仅为可视状态,而 std::swap 上的约束仅为活动状态。As a speculative C++17 feature, the traits (is_swappable, is_swappable_with, is_nothrow_swappable, and is_nothrow_swappable_with) are only visible, and the constraints on std::swap are only active, when compiling with /std:c++latest.

  • 我们从 vcruntime140.dll 和静态库删除了之前在进程启动和 dllmain 期间触发的 ETW 事件处理调用。We've removed ETW eventing calls from vcruntime140.dll and static libraries that previously fired during process startup and dllmain.

  • 我们删除了 STL 容器使用的常见机械设备中的符号名称长度(如 std::vector),从而降低了出现 C4503 警告的可能性。We've removed symbol name length in common machinery used by STL containers, such as std::vector, reducing likelihood of C4503 warnings. 例如,以下类型将不再生成警告:concurrency::concurrent_unordered_map<wstring, vector<pair<uint64_t, vector<uint8_t>>>>。For example, the following type no longer generates a warning: concurrency::concurrent_unordered_map<wstring, vector<pair<uint64_t, vector<uint8_t>>>>.

  • ATL/MFC/AMP/PPL:修复了大量与两阶段查找相关的一致性问题,如下所示:ATL/MFC/AMP/PPL: Lots of conformance fixes related to two-phase lookup, as follows:

    • _com_ptr_t 现在具有移动构造函数和移动赋值运算符。_com_ptr_t now has a move constructor and move assignment operator.

    • MFC:修复了 HMENU 值的处理问题,此前的处理方式有时会导致菜单在 64 位的应用程序上无法正确显示。MFC: Fixed handling of HMENU values that occasionally prevented menus from being properly displayed in 64-bit applications.

    • ATL/MFC:不再发出以下警告:ATL/MFC: No longer emit the following warnings:

    • 函数重写/隐藏:C4263、C4264、C4266Function overriding/hiding: C4263, C4264, C4266

    • 错误匹配异常规范:C4986Mismatching exception specification: C4986

    • /分析:C6386/analyze: C6386

    • ATL:AtlThrow 的所有变体现在均已正确标记为 __declspec(noreturn)ATL: All variations of AtlThrow are now properly marked with __declspec(noreturn). 这样可以防止发出错误的 SAL 警告。This prevents erroneous SAL warnings from being emitted.

    • ATL:修复/改进了几个 SAL 批注。ATL: Fixed/Improved several SAL annotations.

    • /std:c++latest 启用了以下新功能:P0025R1 "clamp()"、P0185R1 "is_swappable, is_nothrow_swappable" 和 P0272R1 "Non-const basic_string::data()."。/std:c++latest enables the following new features: P0025R1 "clamp()", P0185R1 "is_swappable, is_nothrow_swappable", and P0272R1 "Non-const basic_string::data().".

    • /std:c++latest 还控制以下旧功能的删除:N4190 "Removing auto_ptr, random_shuffle(), And Old Stuff"、P0004R1 "Removing Deprecated Iostreams Aliases"、LWG 2385 "function::assign allocator argument doesn't make sense",以及各种非标准功能(std::tr1 命名空间,某些仅适用 TR1 的机制,以及 std::identity 结构)的删除。/std:c++latest also controls the removal of the following old features: N4190 "Removing auto_ptr, random_shuffle(), And Old Stuff", P0004R1 "Removing Deprecated Iostreams Aliases", LWG 2385 "function::assign allocator argument doesn't make sense", and various non-Standard features (the std::tr1 namespace, some TR1-only machinery, and the std::identity struct).

    • 修复了用于 x86 设备的 atomic<int64_t>/atomic<uint64_t> 中的无提示不良 codegen。Silent bad codegen in atomic<int64_t>/atomic<uint64_t> on x86 was fixed.

    • 除非绝对必要,STL 现在会避免使用线程安全的“神奇静态对象”,从而改进了 codegen。The STL now avoids using thread-safe "magic statics" except when absolutely necessary, improving codegen.

    • 元组的完美转发构造函数现在可避免外向争用复制构造函数,由此修复了某些方案中的编译器错误。Tuple's perfect forwarding constructor now avoids out-competing the copy constructor, fixing compiler errors in certain scenarios.

  • 协同程序:Coroutines:

    • 不推荐使用后列项:__yield_value & __await 关键字。Deprecated the following: __yield_value & __await keywords. 请改用 co_await / co_yieldUse co_await / co_yield instead.
    • 向后列项添加了弃用通知:coroutine_handle 类的 to_addressfrom_promise 成员。Added deprecation notice to: to_address and from_promise members of coroutine_handle class. 使用 coroutine_handle::address() 而非 coroutine_handle::to_address()Instead of coroutine_handle::to_address(), use coroutine_handle::address().
    • 使用 coroutine_handle::from_promise(Promise &P) 而非 coroutine_handle::from_promise(Promise *P)Instead of coroutine_handle::from_promise(Promise *P), use coroutine_handle::from_promise(Promise &P).
  • 我们通过使用更主动的方式分派到 memcmp 和 memchr,改进了以下的性能:std::equalstd::lexicographical_compare,从而极大提升了某些方案中的性能。We've improved performance of the following: std::equal and std::lexicographical_compare by dispatching to memcmp and memchr more aggressively, resulting in large performance improvements in some scenarios. 例如,64 位平台上的 equal(char,char,char, char)。For example: equal(char,char,char, char) on 64 bit platforms.

    • 通过减少迭代器调试机制中簿记函数调用的数量,加大对内部版本的调试力度。debug builds significantly by reducing the number of bookkeeping function calls in our iterator debugging machinery.
    • 相较发行版本中的 Update 2,string::push_back 获得另外 40% 的改进,同时调试版本获得了更多实质性的改进。string::push_back has improved another 40% vs. Update 2 in release builds, with more substantial improvements in debug builds. (这是除 Update 2 中较大性能改进之外的改进)。(This is in addition to large performance improvements here that shipped in Update 2).
    • 已通过消除多种类型的空模板元编程支持调用(例如 _Iter_cat)跨所有标准算法,以及通过减少谓词复制的数量跨所有采用谓词的算法,对调试版本进行了改进。Debug builds across all standard algorithms have improved by eliminating several types of empty template metaprogramming support calls (for example,_Iter_cat), across all algorithms that take predicates by reducing the number of predicate copies.
    • std::mismatch_ITERATOR_DEBUG_LEVEL 1 和 2 下,它在迭代之前,在可能的情况下按范围检查第二个范围。std::mismatch under _ITERATOR_DEBUG_LEVEL 1 and 2 by range checking the second range where possible ahead of iteration.
  • 我们对其余算法(在 Update 2 中,仅少数算法与新的弃用机制挂钩)应用了针对 _SCL_INSECURE_DEPRECATE 消息的改进诊断。We've applied improved diagnostics for _SCL_INSECURE_DEPRECATE messages to the remaining algorithms (in Update 2 only a small number of algorithms were hooked into the new deprecation mechanism). 这在调试到标准算法内部时还能改善调试体验,因为不再有任何 _ITERATOR_DEBUG_LEVEL 处理器交互会声明多个标准算法的副本。This also improves the debugging experience when debugging into the standard algorithms, as there is no longer any _ITERATOR_DEBUG_LEVEL preprocessor interaction declaring multiple copies of standard algorithms. 我们还进行以下内容的修复:We have also fixed the following:

    • 我们修复了因非标准 _ITERATOR_DEBUG_ARRAY_OVERLOADS 和双范围算法之间的交互而导致无法编译某些函数(如 mismatch(iter, iter, T[]))的问题。We've fixed the inability to compile some functions like mismatch(iter, iter, T[]) due to interaction between our nonstandard _ITERATOR_DEBUG_ARRAY_OVERLOADS and dual-range algorithms.
  • 我们修复了 STL 中默认关闭的警告 C4242 的冲突。We've fixed violations of the off-by-default warning C4242 in the STL.

  • 我们修复了 Std::pop_heap 中可能发生的整数溢出 Bug。We've fixed possible integer overflow bug in std::pop_heap.

  • 我们修复了因进行插入 CLR 的 LoadLibrary 调用的同时保留了区域设置锁定而导致 /clr:pure 下可能发生的挂起现象。We've fixed potential hang under /clr:pure due to CLR-inserted LoadLibrary calls while holding the locale lock.

C++/CLI 调试C++/CLI Debugging

  • C++/CLI 表达式计算器现在支持调试器功能,如 Natvis(以前仅对纯本机应用提供支持)。The C++/CLI expression evaluator now supports debugger features, such as Natvis, that were previously only supported for pure native apps. 现在,在混合托管/本机应用中,当对象在变量窗口列出(或在数据提示内)时将进行扩展(与在类型可视化工具定义的纯本机应用中的扩展类似)。Now in a mixed managed/native app when objects are listed in a variable window (or inside a datatip), they will expand just like they do in a pure native app as defined by the type visualizers.


Clang/C2 平台工具集Clang/C2 Platform Toolset

我们已将 Clang 3.8 版本集成到 Clang/C2,并提供 64 位托管工具集。We've integrated Clang 3.8 release into Clang/C2 and provided a 64-bit hosted toolset.


我们已启用对最新 Android NDK 版本 R11C 的支持并支持升级当前项目以面向最新 NDK 这一功能。We've enabled support for the latest Android NDK version R11C and the capability to upgrade the current projects to target the latest NDK.


Visual Studio 2015 Update 3 包含 TypeScript 1.8.34Visual Studio 2015 Update 3 includes TypeScript 1.8.34. 我们已修复了内存不足的错误(通过使用 AngularJS 的一些大型 TypeScript 项目)。We've fixed an out of memory error with some large TypeScript projects that use AngularJS.

C# 和 Visual BasicC# and Visual Basic

我们在降低内存占用量和提升代码诊断性能方面投入了大量工作。We've invested in reducing memory footprint and improving the performance of code diagnostics. 这将减少在较早前版本中出现的大量的内存不足的故障。This will reduce a lot of the out-of-memory crashes seen in prior releases. 我们改进了整个解决方案上代码诊断运行的性能。We’ve improved the performance of running code diagnostics on an entire solution. 要了解有关代码诊断性能提升的详细信息,请参阅 MSDN 上的 How to: Enable and Disable Full Solution Analysis for Managed Code(如何:启用和禁用托管代码的完整解决方案分析)页。To learn more about code diagnostic performance enhancements, read the How to: Enable and Disable Full Solution Analysis for Managed Code page on MSDN.

其他改进包括:Additional improvements include the following:

  • 用于添加对 NuGet 包的引用以作为一种快速修复方式的选项:An option to add a reference to a NuGet package as a quick fix:


  • 可从“工具”>“选项”>“文本编辑器”> C# >“高级”的“使用指令”下启用此选项:You can enable this option from Tools > Options > Text Editor > C# > Advanced, under "Using Directives":


  • 我们改进了对面向 .NET 平台标准的可移植类库的支持。We've improved support for Portable class libraries targeting the .NET Platform Standard.
  • 我们向“C# GoTo 实现”和“查找所有引用”添加了性能改进。We've added performance improvements to the C# GoTo Implementation and Find All References. 可通过选择一个对象,右键单击该对象,然后从菜单中选择该对象,来体验这些改进。You can try these by selecting an object, right-clicking on it and then selecting them from the menu.
  • 当将“全部修复”操作应用于文档/项目/解决方案时,现在会显示一个进度条。When you apply a “fix all” action to document/project/solution we now display a progress bar.
  • 提升了大型解决方案中重载 C# 和 VB 项目的性能。Improved performance when reloading C# and VB projects in large solutions. 有关更多信息,请参阅:Performance considerations for large solutions(针对大型解决方案的性能注意事项)。For more information and tips, read: Performance considerations for large solutions.

团队资源管理器Team Explorer

修复了团队资源管理器中的几个 bug:Several bugs have been fixed in Team Explorer:

  • 无法查看从 Git 存储库删除的文件内容。Unable to view the contents of a file that was deleted from a Git repository.
  • 查看分支的历史记录时,当焦点是最新提交时,应禁用“转到子图标”。When viewing the history of a branch, the Go to Child icon should be disabled when the focus is the latest commit.
  • 使用 Git.exe 更改分支时,Visual Studio 可能崩溃或进入未知状态。When changing branches using Git.exe, Visual Studio may crash or get into an unknown state.
  • 在 Git 存储库中查看分支的历史记录时,记录图表中的突出显示存在问题。When viewing the history of a branch in a Git repository, the highlighting in the history graph has glitches.
  • 在团队资源管理中创建分支时,创建分支的 Alt+B 快捷键与生成菜单冲突。When creating a branch in Team Explorer, the Alt+B shortcut for Create Branch conflicts with the Build menu.
  • 在较高的内存使用情况下,当尝试对大于可用内存的对象进行解压缩时,Git 给出“找不到对象 - 没有任何匹配的松散对象 ()”的错误,而不是内存不足的错误。In a high memory usage situation, when attempting to unpack an object larger than the available memory, Git gives an error of "Object not found - no matching loose object ()" instead of an out of memory error.
  • 错误消息中拼写有误“...按顺序打开此解决方案...”。Typo in the error message "... In order the open this solution ...".
  • 查看某个分支的历史记录并右键单击历史记录中的第一个提交时将禁用“挑拣”。When viewing the history of a branch and right clicking on the first commit in history, Cherry Pick is disabled.
  • 从团队资源管理器分支页上下文菜单创建拉取请求时,使用当前分支来替代所选分支。When creating a pull request from the Team Explorer branches page context menu uses the current branch instead of the selected branch.

Xamarin for Visual StudioXamarin for Visual Studio

Visual Studio 2015 Update 3 现在包括 Xamarin 4.1。Visual Studio 2015 Update 3 now includes Xamarin 4.1. 除了大量的 Bug 修复,该版本还添加了对 tvOS 的支持,提升了 iOS 资产目录支持,改进了 XML 编辑体验,并在创建 iOS 应用时添加了 SSL/TLS 和 HttpClient 实现的选择器。In addition to a number of bug fixes, this release adds support for tvOS, improves the iOS Assets Catalog support, improves the XML editing experience, and adds selectors for SSL/TLS and HttpClient implementations when creating iOS apps. 有关更多信息,请参阅 Xamarin 发行说明For more information, see the Xamarin release notes.

Top of Page