Visual Studio 2017 15.6 版-Preview 版本資訊Visual Studio 2017 version 15.6 - Preview Release Notes

02/23/2018

注意

這不是 Visual Studio 的最新版本。This is not the latest version of Visual Studio. 若要查看 Visual Studio 2019 最新版本的資訊，請瀏覽目前的版本資訊 (機器翻譯) 頁面。To see information on the latest version, Visual Studio 2019, please visit the current Release Notes page.

意見反應與建議Feedback & Suggestions

請提供您的意見！We’d love to hear from you! 若有任何問題，請透過安裝程式或 Visual Studio IDE 本身右上角的回報問題選項來通知我們。For issues, let us know via the Report a Problem option in the upper right-hand corner of either the installer or the Visual Studio IDE itself. 必須提供The Feedback Icon 圖示位在右上角。icon is located in the upper right-hand corner. 您可以在 Visual Studio 開發人員社群 (英文) 追蹤您的問題，也可以在那裡詢問問題和尋找解答。You can track your issues in the Visual Studio Developer Community, where you can ask questions and find answers. 我們的即時聊天支援。our Live Chat support.

提示

需要立即的專業人員支援？Need professional support right now? 請查看可用的支援選項。See available support options.

發行記錄Release History

2018年2月23日--Visual Studio 15.6 版 Preview 6February 23, 2018 -- Visual Studio version 15.6 Preview 6
2018年2月14日--Visual Studio 15.6 版 Preview 5February 14, 2018 -- Visual Studio version 15.6 Preview 5
2018年2月7日--Visual Studio 15.6 版 Preview 4-- 閱讀 Preview 4 的 blog 文章！February 7, 2018 -- Visual Studio version 15.6 Preview 4 -- Read the Preview 4 blog post!
2018年1月25日--Visual Studio 15.6 版 Preview 3January 25, 2018 -- Visual Studio version 15.6 Preview 3
2018年1月10日--Visual Studio 15.6 版 Preview 2-- 閱讀 Preview 2 的 blog 文章！January 10, 2018 -- Visual Studio version 15.6 Preview 2 -- Read the Preview 2 blog post!
2017年12月14日--Visual Studio 15.6 版 Preview 1。1December 14, 2017 -- Visual Studio version 15.6 Preview 1.1
2017年12月7日--Visual Studio 15.6 版 Preview 1-- 閱讀 Preview 1 的 blog 文章！December 7, 2017 -- Visual Studio version 15.6 Preview 1 -- Read the Preview 1 blog post!

提示

您可以在 Visual Studio 2017 發行節奏文件中深入了解版本發佈的方式以及如何識別不同的版本。You can learn more about how we ship our releases and how to identify different versions in the Visual Studio 2017 Release Rhythm document.

已知問題Known Issues

查看 Visual Studio 2017 15.6 版中所有現有的已知問題和可用的因應措施。 See all existing known issues and available workarounds in Visual Studio 2017 version 15.6.

發行日期：2018年2月23日-Visual Studio 2017 15.6 版 Preview 6Release Date: February 23, 2018 - Visual Studio 2017 version 15.6 Preview 6

本版修正的前幾個主要問題Top Issues Fixed in this Release

這些是此版本中已解決的客戶回報問題。These are the customer-reported issues addressed in this release. 如果您要尋找 15.6 Preview 中已修正的特定客戶回報問題，請造訪開發人員社群。If you are looking for a specific customer-reported issue that has been fixed in 15.6 Preview, visit the Developer Community.

發行日期：2018年2月14日-Visual Studio 2017 15.6 版 Preview 5Release Date: February 14, 2018 - Visual Studio 2017 version 15.6 Preview 5

本版更新摘要Summary of Updates in this Release

Windows 10 Insider PREVIEW SDK現在可以安裝為選用元件。The Windows 10 Insider Preview SDK can now be installed as an optional component.
6.1 Service Fabric 版本的 Service Fabric 工具現在已可供使用。Service Fabric Tooling for the 6.1 Service Fabric release is now available.

本版修正的前幾個主要問題Top Issues Fixed in this Release

本版新功能What's New in this Release

通用 Windows 平台開發人員工具Tools for Universal Windows Platform Developers

Windows 10 Insider Preview SDK （組建17095）現在可以安裝為包含通用 Windows 平臺開發工作負載的選擇性元件。The Windows 10 Insider Preview SDK, Build 17095, can now be installed as an optional component with the Universal Windows Platform development workload.

發行日期：2018年2月7日-Visual Studio 2017 15.6 版 Preview 4Release Date: February 7, 2018 - Visual Studio 2017 version 15.6 Preview 4

本版更新摘要Summary of Updates in this Release

我們已簡化更新程序；您可以透過通知直接執行安裝程式。We streamlined the update process so the notification takes you directly to the Installer.
我們在鍵盤對應中，新增了 Edit.Duplicate 的快速鍵。We added a new shortcut for Edit.Duplicate in the keyboard mapping.
效能分析工具的 CPU 使用量工具可以顯示非同步程式碼的邏輯呼叫堆疊。The Performance Profiler's CPU Usage Tool can display logical call stacks for asynchronous code.
您現在可以按一下 Team explorer 中的 [持續傳遞] 磚，以設定應用程式的自動化組建和部署。You can now click on "Continuous Delivery" tile in Team explorer to configure automated build and deployments for your application.
在完整連結案例中產生 C++ 對應檔的額外負荷已降低。C++ Mapfile generation overhead is reduced in full linking scenarios.
其他 f # 工具和編譯器更新現在已可供使用，包括以 F # 和 .NET Core SDK 專案進行檔案排序的完整支援。Additional F# tooling and compiler updates are now available, including full support for file ordering with F# and .NET Core SDK projects.

本版修正的前幾個主要問題Top Issues Fixed in this Release

這些是此版本中已解決的客戶回報問題。These are the customer-reported issues addressed in this release. 如果您要尋找 15.6 Preview 4 中已修正的特定客戶回報問題，請造訪開發人員社群。If you are looking for a specific customer-reported issue that has been fixed in 15.6 Preview 4, visit the Developer Community.

本版新功能What's New in this Release

IDE 設定IDE Setup

我們已簡化更新程序；您可以透過 Visual Studio 中的更新通知直接執行安裝程式，而不需透過 [延伸模組和更新]。We've streamlined the update process by having the update notification in Visual Studio take you directly to the installer, instead of Extensions and Updates.
已更新「ASP.NET 與網頁程式開發」和「.NET Core 跨平台開發」的工作負載，以包括「網頁程式開發的雲端工具」。The workloads "ASP.NET and web development" and ".NET Core cross-platform development" have been updated to include "Cloud tools for web development". 此元件包含從 Visual Studio 內取用 Azure Functions 所需的所有專案。This component comprises of everything needed to consume Azure Functions from within Visual Studio.

注意

從 15.6 Preview 3 更新至 Preview 4 或更高版本時，電腦可能會自動重新啟動，而不通知使用者或與其進行確認。When updating from 15.6 Preview 3 to Preview 4 or greater, the computer may restart automatically without notifying or confirming with the user.

IDE 快速鍵IDE Shortcut

我們在預設的鍵盤對應中，新增 Ctrl+D 作為 Edit.Duplicate 的快速鍵。We added Ctrl+D as the shortcut for Edit.Duplicate in the default keyboard mapping. 先前的弦 (Ctrl + E、V) 仍可運作，且適用于所有鍵盤對應配置The previous chord (Ctrl+E, V) still works, and is available in all keyboard mapping schemes

效能Performance

UI 回應性通知UI Responsiveness Notifications

為了讓您一目了然延伸模組對效能和可靠性的影響，Visual Studio 會執行即時分析，以判斷延伸模組是否可能是造成無法回應的原因。In order to provide more transparency around extensions' impact on performance and reliability, Visual Studio performs real-time analysis to determine whether an extension is likely to have caused unresponsiveness. 如果 Visual Studio 判定某個延伸模組是停止回應的原因，即會顯示通知以讓使用者停用可疑的延伸模組或隱藏該延伸模組的後續通知 (圖 1)。If an extension is determined to have caused the hang, Visual Studio will display a notification which allows the user to disable the suspect extension or suppress future notifications for that extension (Figure 1).

*(圖 1) UI 回應性通知，以及停用擴充功能或隱藏未來通知的選項(Figure 1) UI Responsiveness notification with option to disable the extension or suppress future notifications*

.NET Core 方案載入.NET Core Solution Load

在此預覽中，我們著重于 .NET Core，並根據我們的實驗室測量，客戶平均預期會有20% 的解決方案載入時間。In this Preview, we focused on .NET Core and according to our lab measurements, customers can expect 20% faster solution load times on average.

偵錯和診斷Debugging and Diagnostics

CPU 使用量工具CPU Usage Tool

[CPU 使用量] 工具可以顯示非同步程式碼的邏輯呼叫堆疊 (也稱為「非同步呼叫堆疊拼接」 ) 。The CPU Usage tool can display logical call stacks for asynchronous code (aka 'Async Call Stack Stitching').

若要查看邏輯呼叫堆疊 (亦即「拼接的呼叫堆疊」)，請開啟 CPU 使用量工具 [篩選] 下拉式功能表的 [Stitch Async Code] (拼接非同步程式碼) 設定。To see logical call stacks (i.e. 'stitched call stacks'), turn on the "Stitch Async Code" setting in the Filter drop-down menu of the CPU Usage tool.
系統會將代表父函式或工作執行的非同步程式碼顯示為 [呼叫樹狀圖] 檢視和 [呼叫端/被呼叫端] 檢視中的子系。Asynchronous code running on behalf of a parent function or Task will appear as a child in the Call Tree and Caller/Callee views.
這項變更可讓您更輕鬆巡覽非同步程式碼，並了解其效能特性。This change makes it easier to navigate asynchronous code and understand its performance characteristics.

注意

這項功能可能需要很長的時間來產生某些非同步程式碼模式的邏輯呼叫堆疊。This feature can take a long time to produce the logical call stacks for some async code patterns. 您可以視需要取消分析，並關閉設定。You can cancel the analysis and turn off the setting if necessary. 上述行為只有在使用 ALT-F2 效能分析工具啟動頁面進行事後剖析分析期間，才可以使用。This behavior is only available during post-mortem style profiling using the ALT-F2 Performance Profiler launch page. 在偵錯期間使用 CPU 使用量工具時，不會顯示邏輯呼叫堆疊。When the CPU Usage tool is used during debugging, it does not shows logical call stacks.

*(圖 2) 具有作用中之呼叫堆疊的邏輯呼叫堆疊樹狀結構(Figure 2) Logical Call Stack Tree with Call Stack Stitching in effect*

.NET 生產力.NET Productivity

Visual Studio Web ToolsVisual Studio Web Tools

針對 .NET Core 專案，方案總管有一項稱為「檔案巢狀」的新功能，其可讓使用者控制相關檔案在方案總管中的呈現方式。Solution Explorer has a new capability for .NET Core projects called "file nesting", which allows users to control how related files appear in Solution Explorer.
已更新專案的發行體驗。The project publishing experience has been updated.
在 [新增專案] 對話方塊中：In the New Project dialog:
- 讓您挑選 .NET Framework 版本的下拉式清單已移至對話底部，因此不會再作為範本的篩選準則。the drop-down that let's you pick a version of .NET Framework has been moved to the bottom of the dialog and no longer acts as a filter for the template.
- 已將 "Web" 節點的「網站」子節點更名為「舊版本」。for the node "Web", the sub-node "Web Site" has been renamed to "Previous Versions".
WebForms 和 MVC 5 專案的偵錯下拉式功能表：The debug drop-down for WebForms and MVC 5 projects:
- 現在可讓使用者選取 Azure App Service 部署應用程式的快照偵錯工具。now allows users to select the Snapshot Debugger for Azure App Service deployed apps.
- 已更新為具有與 ASP.NET Core 專案相同的瀏覽器選取手勢。has been updated to have the same browser selection gesture as ASP.NET Core projects.

設定持續傳遞工具Configure Continuous Delivery Tools

針對原始檔控制下的方案，您現在可以按一下 Team Explorer 中的 [持續傳遞] 磚，以設定應用程式的自動化組建和部署。For solutions under source control, you can now click on the “Continuous Delivery” tile in Team Explorer to configure automated build and deployments for your application.

C++C++

在完整連結案例中產生對應檔的額外負荷已降低。Mapfile generation overhead is reduced in full linking scenarios. 不過，我們仍建議使用 PDB 檔案，而非對應檔。We still recommend using PDB files instead of mapfiles.

F # 編譯器和工具改進F# Compiler and Tooling Improvements

Preview 4 針對 F # 和 .NET Core SDK 專案的多目標提供了完整的檔案排序和初始支援，以及 F # 編譯器的一些重大修正。Preview 4 introduces full support for file ordering and initial support for multi-targeting with F# and .NET Core SDK projects, and also some critical fixes for the F# compiler.

編譯器與核心程式庫變更Compiler and Core Library Changes

已修正 F# 程式碼中所定義的 System.Tuple 類型迴歸不再支援 .Item1/.Item2/etc. 的問題。A regression in System.Tuple types defined in F# code no longer supporting .Item1/.Item2/etc. has been fixed. 因為這些元組類型現在是100% 與 F # 元組語法同義，所以在使用這些屬性時，我們會引進警告。Because these tuple types are now 100% synonymous with F# tuple syntax, we introduce a warning when using these properties. 如需詳細資料，請參閱連結的提取要求。See the linked pull request for more details.
>gustavo Leon已修正以靜態方式解析的型別參數之推斷順序中的兩個回歸和另一個 bug 修正。Two regressions and another bug fix in inference order for Statically Resolved Type Parameters have been fixed by Gustavo Leon.
針對 .NET Standard 的 FSharp.Core，已啟用 F# 類型的 IsSerializable 屬性。The IsSerializable property for F# types in FSharp.Core for .NET Standard has been enabled. 現在，Option 和 Async 等 F# 類型可針對 .NET Standard 和 .NET Core 序列化。F# types such as Option and Async are now serializable for .NET Standard and .NET Core.
Fsharp.core 套件已更新為版本4.3.3，並包含此版本和 Preview 3 的所有變更。The FSharp.Core package has been updated to version 4.3.3 and includes all changes for this release and Preview 3.

F# 工具的改善F# Tooling Improvements

現在已實行以 F #/.NET Core SDK 為基礎之專案的多目標支援。Support for multi-targeting of F#/.NET Core SDK-based projects is now implemented.
執行以 .NET Core SDK 為基礎之專案的檔案順序，包括新增以上/下方、資料夾支援，以及 Visual Studio UI 更新，而不需要重載專案。File ordering for .NET Core SDK-based projects is implemented, including Add Above/Below, folder support, and the Visual Studio UI updating without needing to reload a project.
Bug 修正和效能改善 (來源：Eugene Auduchinok 和 Microsoft)。Bug fixes and performance improvements, by Eugene Auduchinok and Microsoft.
現在，以 #if INTERACTIVE 包圍的程式碼不需要類型檢查即可支援 IDE 功能 (來源：Eugene Auduchinok)。Code surrounded by #if INTERACTIVE defines now support IDE features which do not require type checking, by Eugene Auduchinok.
Loïc Denuzière已修正舊版 F #/ASP.NET ( .NET Framework) 專案的空白「新檔案」視窗修正不慎回復。An inadvertent reversion of a fix for empty "New file" window on older F#/ASP.NET (.NET Framework) projects has been fixed by Loïc Denuzière.

F # 基礎結構和 OSS 存放庫改善F# infrastructure and OSS repo improvements

F# 編譯器 SDK 現在內含附屬組件和 FSharp.Core.resources.dll。Satellite assemblies and FSharp.Core.resources.dll are now included in the F# compiler SDK.
如果元件資訊未變更，則編譯器現在無法在 Visual F# 程式碼基底中重建本身。The compiler is now prevented from rebuilding itself in the Visual F# codebase if assembly info has not changed.
針對 FSharpSymbolUse，實作了 ToString() 以便在偵錯編輯器工具時更輕鬆查看所有符號使用結果 (來源：Eugene Auduchinok)。ToString() is implemented for FSharpSymbolUse to make it easier to look at all symbol use results when debugging editor tooling, by Eugene Auduchinok.

發行日期：2018年1月25日-Visual Studio 2017 15.6 版 Preview 3Release Date: January 25, 2018 - Visual Studio 2017 version 15.6 Preview 3

本版更新摘要Summary of Updates in this Release

Visual Studio Build Tools 現在支援 TypeScript 和 Node.js。Visual Studio Build Tools now supports TypeScript and Node.js.
ClickOnce 工具現在支援使用 CNG 憑證來簽署應用程式和部署資訊清單檔案。ClickOnce Tools now supports signing application and deployment manifests file with CNG certificate.
您現在可以從 ASP.NET 應用程式的 Debug 目標下拉式清單中啟動快照集調試程式。Snapshot Debugging can now be started from the Debug Target dropdown for ASP.NET applications.
我們已新增 Visual Studio 安裝程式的安裝進度詳細資料。We've added installation progress details on Visual Studio Installer.
C++ 編譯器可透過已改善的最佳化，讓您的程式碼執行速度更快。The C++ compiler optimizes your code to run faster through improved optimizations.
在此版本中，我們已改進 F # 語言和工具的錯誤報表和效能。We made improvements to error reporting and performance for F# language and tools in this release.

本版修正的前幾個主要問題Top Issues Fixed in this Release

本版新功能What's New in this Release

Visual Studio Build ToolsVisual Studio Build Tools

Visual Studio Build Tools 可讓您建立組建伺服器，而不需要安裝所有 Visual Studio。The Visual Studio Build Tools allow you to create build servers without installing all of Visual Studio. 對於傳統型專案，安裝程式已經可以支援 C++、ASP.NET 和 .NET Core。The installer already supports C++, ASP.NET, and .NET Core for Desktop projects. 為了回應客戶的要求，我們會持續強化 Visual Studio Build Tools 以支援其他專案類型。In response to customer requests, we are enhancing the Visual Studio Build Tools to support additional project types. 在此版本中，我們新增對 TypeScript 和 Node.js 專案的支援。In this release we have added support for TypeScript and Node.js projects. 我們預計會在未來版本中新增對更多專案類型的支援。We expect to add support for more project types in future releases. 這是此預覽版本 Visual Studio Build Tools 的下載位置。This is the download location for the Visual Studio Build Tools for this Preview release.

Visual Studio ClickOnce ToolsVisual Studio ClickOnce Tools

ClickOnce 是一種部署技術，可讓您建立自行更新的 Windows 應用程式，並以最少的使用者互動來安裝和執行這些應用程式。ClickOnce is a deployment technology that enables you to create self-updating Windows-based applications that can be installed and run with minimal user interaction. 它會使用憑證以驗證應用程式發行者的真偽，並會簽署應用程式和部署資訊清單，以證明檔案未遭竄改。It uses certificates to verify the authenticity of the application's publisher, and to sign the application and deployment manifests to prove that the files have not been tampered with. 在這個版本中，我們已新增支援使用 Cryptography Next Generation (CNG) 憑證，簽署應用程式和部署資訊清單。In this release we have added support for signing the application and deployment manifests with Cryptography Next Generation (CNG) certificate.

診斷和偵錯工具Diagnostics and Debugging

快照集偵錯工具Snapshot Debugger

如果您正在使用 Azure App Service 中執行的 ASP.NET 應用程式，而且想要嘗試快照點或記錄點，您現在可以在 [偵錯工具目標] 下拉式清單中選取 [快照偵錯工具 (Azure App Service) ] (圖 1)。If you are working on an ASP.NET application running in Azure App Service, and would like to try out Snappoints or Logpoints, you can now do so by selecting "Snapshot Debugger (Azure App Service)" in the Debug Target dropdown (Figure 1).

*(圖 1) 開始 ASP.NET 應用程式的快照偵錯工具(Figure 1) Start Snapshot Debugger for ASP.NET application*

安裝Installation

使用新的安裝詳細資料 ([圖 2])，您可以看到下載大小、完成的下載百分比和下載的速率。With new installation details (Figure 2), you can see the download size, download percentage completed and the rate of the download. 您也可以查看正在安裝的套件總數以及剩餘的數目。You can also see total number of packages being installed and how many are remaining.

注意： 如果您暫停安裝並于稍後繼續，則進度會套用至要下載及安裝的內容，且不會從上一個計數開始。Note: If you pause the installation and later resume, the progress applies to what’s left to be downloaded and installed, and does not start from the previous count.

Visual C++ 的改善Visual C++ Improvements

C++ 小組進行了下列重大的編譯時間改善：The C++ team has made significant compile-time improvements:
- 編譯器可透過預先遞增迴圈已改善的最佳化，以及 LTCG 中常數全域資料已改善的識別和傳播，讓您的程式碼執行速度更快。The compiler optimizes your code to run faster through improved optimizations of pre-incremented loops and improved identification and propagation of constant global data in LTCG.
- 相較於 15.5，編譯時間更短。Compile times are shorter compared to 15.5. 編譯器前端大部分的輸入速度都提升 3% 到 5% 之間。The compiler front-end is between 3-5% faster on most inputs. 由於核心最佳化演算法的額外負荷已降低，編譯器最佳化工具速度可提升 3%。The compiler optimizer is 3% faster due to reduced overhead of core optimization algorithms. 此外，資料結構已重新架構，因此大型 LTCG 編譯速度會加快 10%。Additionally, large LTCG compilations are 10% faster due to re-architected data structures.
C++ 連結器的改善：Improvements to the C++ linker:
- 使用 /debug： fastlink pdb 進行大型方案的偵錯工具更健全。Debugging large solutions with /Debug:fastlink PDBs is more robust. PDB 的變更可降低延遲，並將 VS 偵錯工具中的堆積記憶體耗用量減少 30%。Changes in the PDB lead to reduced latency and a 30% reduction in heap memory consumption in the VS Debugger.
ARM64 已啟用並完全支援 Profile-Guided Optimization (特性指引最佳化)。Profile-Guided Optimization is enabled and fully supported on ARM64.

F# 語言和工具的改善F# Language and Tooling Improvements

這一版的 F# 和工具引進了許多改善。A lot of improvements went into F# and its tools for this release. 就像往常一樣，來自于此社區的重大貢獻也在這裡。As always, significant contributions from the community came together here.

F # 編譯器和核心程式庫改善F# compiler and core library improvements

Bug 修正和效能改善 (來源：ncave、Vasily Kirichenko 和 Microsoft)。Bug fixes and Perf improvements, by ncave, Vasily Kirichenko, and Microsoft.
F# 集合現在實作 IReadonlyList 和 IReadonlyDictionary (來源：Saul Rennison。F# collections now implement IReadonlyList and IReadonlyDictionary, by Saul Rennison.
NativePtr.ByRefmjmckp新增的支援。NativePtr.ByRef support added by mjmckp.
Async.StartImmediateAsTaskOnur Gumus所新增的支援。Async.StartImmediateAsTask support added by Onur Gumus.
新增支援 Seq.transpose、Array.transpose、List.transpose (來源：Patrick McDonald)。Seq.transpose, Array.transpose, List.transpose support added by Patrick McDonald.

F # 工具改進F# tooling improvements

>vasily (英文 kirichenko) 和>eugene Auduchinok的錯誤報表增強功能。Error reporting improvements by Vasily Kirichenko and Eugene Auduchinok.
>vasily (英文 kirichenko) 、 >eugene Auduchinok、 Daniel Wedelich和 Microsoft 的效能改進。Performance improvements by Vasily Kirichenko, Eugene Auduchinok, Daniel Wedelich, and Microsoft.
使用 >vasily (英文 kirichenko) 和 Microsoft 修正的許多 bug，更精確的自動完成。More precise autocompletion with numerous bugs fixed by Vasily Kirichenko and Microsoft.
未開啟之命名空間中的靜態成員，可透過 >vasily (英文 kirichenko) 完成。Static members in unopened namespaces are available in completion by Vasily Kirichenko.
命名空間符號會出現在 [檔反白顯示] 中，並依 >vasily (英文 Kirichenko) 尋找所有參考。Namespace symbols appear in Document Highlight and Find All References by Vasily Kirichenko.
結構化指導方針程式碼已提供給其他編輯器使用 (VSCode、VS for Mac、) >eugene Auduchinok的附件。Structured Guidelines code has been made available for other editors (VSCode, VS for Mac, Rider) Eugene Auduchinok.
>eugene Auduchinok的 F # 函式有更好的折迭和結構化指導方針。Better collapsing and structured guidelines for F# constructors by Eugene Auduchinok.
現在支援 F # 中的共用檔案和以 .NET Core SDK 為基礎的專案。Shared files in F# and .NET Core SDK-based projects are now supported.
>vasily (英文 kirichenko) 的「簡化名稱分析器」中已不再簡化 Open 語句。Open statements are no longer simplified in the Simplify Names analyzer by Vasily Kirichenko.
sbyte byte >vasily (英文 kirichenko) 現在支援在 QuickInfo 中顯示和 IL 欄位。Display of sbyte and byte IL fields in QuickInfo is now supported by Vasily Kirichenko.
>vasily (英文 kirichenko) 不會再于使用未呼叫 F # 函數或方法上觸發未使用的宣告程式碼修正。Unused declaration code fix is no longer triggered on uncalled F# functions or methods by Vasily Kirichenko.
F #/.NET Framework 專案現在可以參考 .NET Standard 專案。.NET Standard projects can now be referenced by F#/.NET Framework projects.
Nobre現在支援在 .NET Framework 專案中的資料夾拖放功能。Drag and Drop across folders in .NET Framework projects is now supported by Paulo Nobre.
現在可以切換未使用的宣告分析器和程式碼修正。Unused declarations analyzer and code fix is now able to be toggled.

F # 基礎結構改進F# infrastructure improvements

已實作版本控制更新 RFC。Versioning update RFC has been implemented.
所有用於編譯器和工具中的當地語系化檔案現在都可在 GitHub 上取得，而且能夠接受社區投稿。All localization files used in the compiler and tools are now available on GitHub, and are able to accept community contributions.
您現在可以在一小時內從4個以上的小時內產生夜間組建。Nightly builds can now be produced in an hour, down from 4+ hours.
我們已移除對開放原始碼參與者的孤行的相依性。We removed our dependency on the Widows 10 SDK for open source contributors.

若要查看 VS 15.6 Preview 3 的變更完整記錄，請參閱我們的標記。To see the full log of changes from VS 15.6 Preview 3, see our tag.

發行日期：2018年1月10日-Visual Studio 2017 15.6 版 Preview 2Release Date: January 10, 2018 - Visual Studio 2017 version 15.6 Preview 2

本版更新摘要Summary of Updates in this Release

非系統管理員現在可以建立 VS 版面配置。Non-administrators can now create a VS layout.
我們藉由將設計階段組建優化來改善解決方案載入。We improved solution load by optimizing design time build.
[CPU 使用量] 工具現在會顯示具有邏輯「呼叫堆疊拼接」的 async/await 程式碼。The CPU Usage tool now displays async/await code with logical 'Call Stack Stitching'.
流覽至反向組譯來源以進行 .net 程式碼流覽的初始執行。Initial implementation of Navigate to decompiled sources for .NET code navigation.
設定持續傳遞的全新增強功能包含支援 TFVC、透過 SSH 的 Git 驗證，以及容器化專案。New enhancements for Configure Continuous Delivery include support for TFVC, Git authentication over SSH, and containerized projects.
內嵌 ARM GCC 支援現在提供偵錯工具選項。Debug options are now available for Embedded ARM GCC support.
我們已在 c # 編譯器的 CoreCLR 上新增強名稱簽署。We added strong name signing on CoreCLR for C# compiler.
Visual Studio Tools for Xamarin 具有許多針對 iOS 和 Android 開發人員的全新生產力更新。Visual Studio Tools for Xamarin has lots of new productivity updates for iOS and Android developers.
測試 Explorer現在會有階層視圖，而且即時測試探索預設為開啟。The Test Explorer now has a hierarchy view and real time test discovery is on by default.

本版修正的前幾個主要問題Top Issues Fixed in this Release

本版新功能What's New in this Release

安裝和設定Installation and Setup

在此版本中，不具系統管理權限的使用者可以建立 VS 配置；如此一來，非系統管理員即可建立離線的網路安裝。With this release, users without administration rights will be able to create a VS layout, which will allow non-administrators to create an offline network install.
第一次安裝 Visual Studio 或透過網站進行更新時，您會發現 Visual Studio 安裝程式提供了全新且更一目了然的安裝體驗。When you install Visual Studio for the first time or update it from the web, you will see a new, more transparent setup experience for the Visual Studio Installer. 在幕後，沒有任何變更，但全新的體驗會顯示 ([ 圖 3 ]) 的逐步解說。Under the hood, nothing has changed – but the new experience shows you step-by-step what's happening (Figure 3).

*(圖 3) 改進 Visual Studio 安裝程式的透明度設定(Figure 3) Improved transparency setup for Visual Studio Installer*

效能Performance

在15.6 中，我們持續改善方案載入效能，特別是針對設計階段組建結果快取的案例。In 15.6, we continued improving solution load performance, specifically for the scenario when design time build results are cached. 當電腦已開啟方案時，大型 C# 和 Visual Basic 方案的載入速度會比之前快兩倍。Large C# and Visual Basic solutions will load twice as fast as before when a solution has already been opened on a machine.

偵錯和診斷Debugging and Diagnostics

CPU 使用量工具CPU Usage Tool

[CPU 使用量] 工具現在會顯示非同步程式碼的邏輯呼叫堆疊 (也稱為「非同步呼叫堆疊拼接」 ) ([圖 4])。The CPU Usage tool now displays logical call stacks for asynchronous code (aka 'Async Call Stack Stitching') (Figure 4).

系統會將代表父函式或工作執行的非同步程式碼顯示為 [呼叫樹狀圖] 檢視和 [呼叫端/被呼叫端] 檢視中的子系。Asynchronous code running on behalf of a parent function or Task will appear as a child in the Call Tree and Caller/Callee views.
這項變更可讓您更輕鬆巡覽非同步程式碼，並了解其效能特性。This change makes it easier to navigate asynchronous code and understand its performance characteristics.
若要查看實際的呼叫堆疊 (沒有「正在進行」 ) ，請關閉 [CPU 使用量] 工具的 [篩選] 下拉式功能表中的 [拼接非同步程式碼] 設定。To see actual call stacks (without 'stitching'), turn off the "Stitch Async Code" setting in Filter drop-down menu of the CPU Usage tool.

注意

只有在使用 ALT-F2 Profiler 啟動頁面的事後剖析後樣式分析期間，才可使用此行為。This behavior is only available during post-mortem style profiling using the ALT-F2 Profiler launch page. 在偵錯期間使用 CPU 使用量工具時，不會顯示邏輯呼叫堆疊。When the CPU Usage tool is used during debugging, it does not shows logical call stacks.

*(圖 4) 呼叫堆疊拼接的範例(Figure 4) Example of Call Stack Stitching*

.NET 生產力功能.NET Productivity Features

在 15.6 Preview 2 中，我們已新增巡覽至反向組譯原始碼的功能。In 15.6 Preview 2, we’ve added the ability to navigate to decompiled sources. 啟用時，在任何參考的類型或成員上叫用「移至定義」或「查看定義」時，會顯示其定義與透過 ILSpy 反向組譯來重新建構的方法主體。When enabled, invoking Go To Definition or Peek Definition on any referenced type or member will show its definition with reconstructed method bodies via ILSpy decompilation. 若要開啟此功能，請移至 [ 工具 > 選項 > 文字編輯器] > c # > Advanced > 啟用 反向組譯來源的流覽 (圖 5)。To turn on this feature, go to Tools > Options > Text Editor > C# > Advanced > Enable navigation to decompiled sources (Figure 5).

我們也新增了幾個 .NET EditorConfig 選項： dotnet_prefer_inferred_tuple_names 和 dotnet_prefer_inferred_anonymous_type_member_names。We also added a couple more .NET EditorConfig options: dotnet_prefer_inferred_tuple_names and dotnet_prefer_inferred_anonymous_type_member_names. 若要查看所有 .NET 程式碼慣例選項，請參閱 EditorConfig 的 .NET 編碼慣例設定。To see all .NET coding convention options, check out .NET coding convention settings for EditorConfig.

設定持續傳遞工具Configure Continuous Delivery Tools

我們已新增 TFVC 的支援做為原始檔控制提供者：您現在可以在 VSTS TFVC team 專案的原始檔控制下設定解決方案的持續傳遞， (圖 6)。We added support for TFVC as a source control provider: You can now configure continuous delivery for solutions under source control in a VSTS TFVC team project (Figure 6).

*(圖 6) 為 VSTS TFVC 專案中的專案設定持續傳遞(Figure 6) Configure Continuous Delivery for projects in a VSTS TFVC project*

我們新增了透過 SSH 的 Git 驗證支援：您現在可以在已啟用 SSH 驗證的 VSTS 或 GitHub Git 存放庫中，于原始檔控制下設定解決方案的持續傳遞。We added support for Git authentication over SSH: you can now configure continuous delivery for solutions under source control in a VSTS or GitHub Git repo with SSH AUTH enabled.
我們引進了容器化專案的支援：您現在可以設定解決方案的持續傳遞，其 ASP.NET Core 專案和 docker 支援以 Linux 上的 Azure App Service (用於容器的 Web App) (圖 7) 為目標。We introduced support for containerized projects: you can now configure continuous delivery for solutions with ASP.NET Core projects and docker support targeting Azure App Service on Linux (Web App for Containers) (Figure 7). [設定持續傳遞] 對話方塊預設會在 Linux 上建立新的 Azure App Service (用於容器的 Web App) 與 Azure Container Registry (如果您的 Azure 訂用帳戶尚未具備的話)。The Configure Continuous Delivery dialog will default to create a new Azure App Service on Linux (Web App for Containers), and an Azure Container Registry if one doesn’t already exist under your Azure Subscription.

*(圖 7) 為 Linux 上的 App Service 設定持續傳遞至 Azure 對話方塊(Figure 7) Configure Continuous Delivery to Azure dialog for App Service on Linux*

Visual C++ 的改善Visual C++ Improvements

進一步實作 C++17 標準程式庫，包括每個 C++17 標準的 stable_sort、分割、平行內嵌 vector::emplace_back 和 <memory_resource> 等 API。Further progress toward implementing the C++17 Standard Library, including APIs such as stable_sort, partition, inline vector::emplace_back in parallel, and <memory_resource>, per C++17 standards.
使用 Boost.Test 項目範本，輕鬆地將 Boost 單元測試新增至專案。Easily add Boost unit tests to your project with Boost.Test item templates. 現在，您的提升單元測試也會使用提升動態連結程式庫。Your Boost unit tests now also use the Boost dynamic library.
CTest、Google Test 和提升。 CMake 專案中的測試測試會自動探索並列在測試瀏覽器中。CTest, Google Test, and Boost.Test tests in CMake projects are automatically discovered and listed in the Test Explorer.
如果 Include 檔案存在於工作區根目錄之下，即使其未明確新增至 Include 路徑，系統仍會針對 C++ 的 [開啟資料夾] 自動探索遺漏的 Include 檔案。Missing include files are automatically discovered for C++ Open Folder if they exist under the workspace root, even if they are not explicitly added to the include path.
內嵌 ARM GCC 支援現在提供偵錯工具選項。Debug options are now available for Embedded ARM GCC support. 以滑鼠右鍵按一下您的二進位檔，選擇 [Debug and 啟動設定]，然後選取 [C/c + + Debug 微控制器]。Right click your binary, choose Debug and Launch Settings, and then select C/C++ Debug microcontroller.
C++ Core Checker 延伸模組，可偵測是否使用超出範圍存留期的間接取值。A C++ Core Checker extension to detect use of indirections with a lifetime that is out of scope.
5 項關於整數溢位的全新檢查強制執行規則，以及來自 C++ Core Guidelines 的其他規則。5 new checks enforcing rules around integer overflow, and additional rules from the C++ Core Guidelines.
編輯器會將非作用中組態的 IntelliSense 錯誤顯示為紫色波浪線。IntelliSense errors for inactive configurations will be shown as purple squiggles in the editor. 要處理的設定數目可在 [工具] > 選項中進行設定。The number of configurations to process is configurable in Tools > Options.
支援執行單一檔案的程式碼分析 (或是您透過方案總管選擇的檔案)；已清除 [建置] 功能表和 [分析] 功能表。Support for running single file Code Analysis (or on your selection of files from the Solution Explorer); cleaned up the Build and Analyze menus. 「執行程式碼分析」不會再執行產生程式碼的作業，因此可以加快分析執行速度。"Run Code Analysis" no longer runs code generation, which speeds up analysis runs.

C# 編譯器C# Compiler

C# 編譯器現在支援：The C# compiler now supports:

CoreCLR 上的編譯器伺服器，適用于組建輸送量效能Compiler server on CoreCLR, for build throughput performance
CoreCLR ( /keyfile 選項、所有作業系統) 的強式名稱簽署Strong name signing on CoreCLR (/keyfile option, all OSes)

除了許多錯誤（ bug）修正和一項重大變更 (請參閱執行中斷性變更清單) ，在7.2 語言功能中進行兩種次要語言變更：In addition to numerous bug fixes and one breaking change (see running list of breaking changes), two minor language changes where made to the 7.2 language features:

多載的系結器 in (在 GitHub 上查看此主題的詳細資訊) Tie-breaker for in overloads (see more on this topic on GitHub)
在 ref this ref 擴充方法中放寬順序， (在 GitHub 上查看此主題的詳細資訊) Relax ordering of ref and this in ref extension methods (see more on this topic on GitHub)

適用于 Xamarin 的 Visual Studio ToolsVisual Studio Tools for Xamarin

這個版本包含 Xamarin.iOS 11.8 和 Xamarin.Android 8.2。This release includes Xamarin.iOS 11.8 and Xamarin.Android 8.2.

使用 iOS 模擬器的即時 XAML 預覽Live XAML Previewing with the iOS Simulator

Xamarin Live Player 讓開發人員可以直接在 iOS 和 Android 裝置上使用 Visual Studio，以持續部署、測試應用程式及對其偵錯。The Xamarin Live Player enables developers to continuously deploy, test, and debug their apps using just Visual Studio and an iOS or Android device. Visual Studio 2017 15.5 版已新增支援，可讓開發人員直接在 Android 模擬器中預覽即時的 XAML 變更，而不需要重新編譯或重新部署。Visual Studio 2017 version 15.5 added support to enable developers to preview real-time XAML changes directly in the Android emulator without requiring a recompile or redeploy. 此版本將這項功能引進適用於 Windows 的遠端 iOS 模擬器。This release brings this functionality to the Remoted iOS Simulator for Windows.

若要使用這項功能，請使用內容功能表、鍵盤快速鍵，或每個 XAML 檔案頂端的橫幅，從 [部署目標] 下拉式清單中選取 iOS 模擬器和 [即時執行目前的視圖]。To use this feature, select an iOS simulator from the deployment targets dropdown and “Live Run Current View” using the context menu, keyboard shortcut, or the banner at the top of each XAML file.

測試總管Test Explorer

全新階層架構檢視New Hierarchy View

Visual Studio 中的測試 Explorer 現在具有階層視圖 ([圖 8]) 依專案、命名空間和類別來組織您的測試。The Test Explorer in Visual Studio now has a hierarchy view (Figure 8) that organizes your tests by Project, Namespace, and then Class. 針對 Visual Studio 2017 15.6 Preview 2，階層視圖將位於功能旗標後方，但未來的預覽預設會開啟。For Visual Studio 2017 15.6 Preview 2, the hierarchy view will be behind a feature flag, but for future previews it will be on by default. 開啟功能旗標之後，就可以使用位於 [群組依據] 按鈕旁邊的 [測試瀏覽器] 視窗頂端的 [階層] 按鈕，來開啟和關閉此視圖。With the feature flag turned on, this view can be toggled on and off using the hierarchy button located at the top of the Test Explorer window next to the Group by button.

*(圖 8) Test Explorer 階層架構視圖(Figure 8) Test Explorer Hierarchy View*

您可以透過開發人員命令提示字元開啟此功能旗標，或安裝功能旗標延伸 ([圖 9])。You can turn on this feature flag through the developer command prompt or install the Feature Flags extension (Figure 9).

*(圖 9) 功能旗標延伸(Figure 9) Feature Flags extension*

如果您想要透過 Visual Studio 開發人員命令提示字元開啟功能旗標，請在變更安裝 Visual Studio 的路徑之後，執行下列命令：If you’d like to turn on the feature flag through the Visual Studio developer command prompt, run the command below after changing the path to where Visual Studio is installed:

vsregedit set “C:\Program Files (x86)\Microsoft Visual Studio\Preview\Enterprise” HKLM FeatureFlags\TestingTools\UnitTesting\HierarchyView Value dword 1

注意

您可以使用相同的命令關閉旗標，方法是使用0，而不是 dword 後面的1。You can turn off the flag with the same command by using a 0 instead of a 1 after dword.

這項功能不僅讓您可以更容易巡覽測試，還可以輕鬆針對測試提供回饋意見。This feature not only makes navigating your tests much easier, but also gives better feedback on tests at a glance.

如果階層中的「父節點」(專案、命名空間和類別) 至少有一個失敗的測試，則會顯示測試失敗的圖示。The “parent nodes” in the hierarchy (Project, Namespace, and Class) display a failing test icon if they contain at least one failing test.
父節點後面也會接著一個數字，以摘要這個群組包含多少個測試。Parent nodes are also followed by a number summarizing how many tests the grouping contains. 父節點右側顯示的持續時間 (以毫秒為單位) 為該群組內執行測試所花費的總時間。The duration in milliseconds shown to the right of a parent node is the total time that tests within that group took to execute.

將階層視圖新增至測試瀏覽器已在許多想要的清單中，我們很高興知道它如何影響您的工作流程。Adding a hierarchy view to the Test Explorer has been at the top of many wish lists and we are excited to hear feedback on how it affects your workflow. 這項實行中有一個明顯的設計決策，是為了避免在階層中使用傳統群組。One noticeable design decision in this implementation is to prevent the use of traditional groupings within the hierarchy. 每個類別內的測試都會依結果排序，然後依名稱排序。Tests within each class are sorted by outcome and then by name. 這表示失敗的測試會出現在每個類別的最上方。This means that failing tests will appear at the top of each class. 更具可設定的階層，讓使用者可以選擇他們想要的順序 (例如專案、類別，以及持續時間) 都很理想。A more configurable hierarchy where users can choose the ordering they wish (such as Project, Class, then Duration) would be ideal. 我們對此設計有興趣聽取意見反應。We are interested in hearing feedback on this design.

即時測試探索Real Time Test Discovery

即時測試探索是新的 Visual Studio 功能，可使用 Roslyn 分析器來探勘測試並即時填入測試瀏覽器，而不需要建立您的專案。Real time test discovery is a new Visual Studio feature that uses a Roslyn analyzer to discover tests and populate the test explorer in real time without requiring you to build your project. 這項功能是在功能旗標後方的 Visual Studio 2017 15.5 Preview 2 中引進，而且現在預設會在15.6 中開啟！This feature was introduced in Visual Studio 2017 15.5 Preview 2 behind a feature flag and is now on by default in 15.6! 這不僅能大幅加快測試探索的速度，也會讓 test explorer 與程式碼變更（例如新增或移除測試）保持同步。This not only makes test discovery significantly faster, it also keeps the test explorer in sync with code changes such as adding or removing tests. 由於即時探索是由 Roslyn 編譯器所支援，因此僅適用于 c # 和 Visual Basic 專案。Since real time discovery is powered by the Roslyn compiler it is only available for C# and Visual Basic projects.

自動 macOS 佈建Automatic macOS Provisioning

在 Windows 上使用 Visual Studio 建置 iOS 應用程式變得更容易了！Building iOS apps with Visual Studio on Windows just got easier. 此版本新增了自動 macOS 佈建這項全新功能。This release adds a brand new feature called automatic macOS provisioning. 您不需要手動維護 Mac 組建電腦，只需要連接到 Mac，我們即會處理繁重的工作 (使用正確的 Xamarin.iOS 和 Mono 位元安裝和設定組建電腦)，且所有作業都透過 Visual Studio 進行。Rather than needing to manually maintain a Mac build machine, all you need to do is connect to the Mac, and we will handle the heavy lifting of installing and configuring your build machine with the correct Xamarin.iOS and Mono bits, all from Visual Studio.

iOS WiFi 部署iOS WiFi Deployment

遠端 ios模擬器（可讓開發人員完全在 Windows 上的 Visual Studio 中測試及偵測 iOS 應用程式），現在可供15.5 版) 的所有 Visual Studio (版本使用，包括免費的社區版本！The Remoted iOS Simulator, which allows developers to test and debug iOS apps entirely in Visual Studio on Windows, is now available to all editions of Visual Studio (as of version 15.5), including the free Community Edition! 模擬器支援位置模擬、旋轉、手勢等功能，甚至包括 Mac 的 iOS 模擬器不支援的多點觸控功能。The simulator supports functionality like location simulation, rotation, gestures, and even includes functionality that the iOS simulator on Mac does not, like multi-touch. 開發人員在 Windows 上建置 iOS 應用程式時，這可賦予其絕佳的模擬器體驗，那裝置呢？This provides a great simulator experience for developers building iOS apps on Windows, but what about devices? 使用 Visual Studio 2017 15.6 版，您現在可以使用 WiFi 部署在網路上部署 iOS 應用程式–無需纜線！With Visual Studio 2017 version 15.6, you can now deploy your iOS apps over the network with WiFi deployment – no cables required! 在 Xcode 中設定無線裝置之後，Visual Studio 即會顯示該裝置，就像一般部署目標一樣。After setting up a wireless device in Xcode, it shows up in Visual Studio just like a normal deploy target.

發行日期：2017年12月14日-Visual Studio 2017 版 15.6 Preview 1。1Release Date: December 14, 2017 - Visual Studio 2017 version 15.6 Preview 1.1

本版修正的前幾個主要問題Top Issues Fixed in this Release

這些是在此版本中解決的客戶回報問題：These are the customer-reported issues addressed in this release:

發行日期：2017年12月7日-Visual Studio 2017 15.6 版 Preview 1Release Date: December 7, 2017 - Visual Studio 2017 version 15.6 Preview 1

本版更新摘要Summary of Updates in this Release

Python 不再需要完成 DB，Anaconda 使用者現在有 conda 的支援。Python no longer requires a completion DB, and Anaconda users now have support for conda.
Team Explorer 支援 Git 標記，並簽出 Visual Studio Team Services 提取要求分支。Team Explorer supports Git tags, and checking out Visual Studio Team Services pull request branches.
您現在可以暫停安裝並于稍後繼續。You can now pause your installation and resume at a later time.
部分 Visual Studio 可執行檔的檔案版本現可看出次要版本。File versions for a number of Visual Studio executables now reflect the minor release.
[CPU 使用量] 工具現在會根據特定程式程式碼的 CPU 耗用量，顯示原始程式列的醒目提示。The CPU Usage tool now displays source line highlighting based on the CPU consumption of specific lines of code.
您現在可以使用 Visual Studio 帳戶來存取 Azure 資源（例如 Key Vault ）。You can now access Azure resources such as Key Vault using your Visual Studio accounts.
偵錯工具現在支援在傾印的偵錯工具中透過 >setthreaddescription api 設定的執行緒名稱。The debugger now supports thread names set via SetThreadDescription APIs in dump debugging.

本版修正的前幾個主要問題Top Issues Fixed in this Release

這些是在此版本中解決的客戶回報問題：These are the customer-reported issues addressed in this release:

本版新功能What's New in this Release

Visual C++ 的改善Visual C++ Improvements

支援 C++17 保證的複製省略。Support for C++17 guaranteed copy elision.
從 [新增專案] 對話方塊建立 CMake 專案。Create CMake projects from the Add New Project dialog.
內建支援適用於 Android 開發的 Android NDK r15c。Built-in support for Android NDK r15c for Android development.

PythonPython

在此版本中，我們已移除完成資料庫的需求，以取得安裝套件的 IntelliSense (圖 10)。For this release, we have removed the need for a completion database in order to get IntelliSense on installed packages (Figure 10). 這表示，現在您只要幾秒鐘就可以取得 numpy 和 pandas 等熱門套件的完成項，而不需在安裝好套件後苦等四小時。This means that instead of waiting up to four hours after installing a package, you will now get completions in just a few seconds for popular packages such as numpy and pandas.

*(圖 10) pandas 套件的 Python 完成項(Figure 10) Python completions for the pandas package*

我們已新增可自訂檔字串使用的色彩（當它們用於類別或函式時），以及在呼叫程式庫時偵測到的正則運算式模式 re (圖 11)。We have added the ability to customize the color used for doc-strings, when they are used in a class or function, and also regular expression patterns detected as part of a call into the re library (Figure 11). 這些變更可能會在 [工具]、[字型和色彩]、[Python 檔] 和 [Python 正則運算式] 下變更。These may be changed under Tools, Fonts and Colors, "Python Documentation" and "Python Regular Expression".

*([圖 11] 中反白顯示的檔-字串和正則運算式的) 範例(Figure 11) Example of highlighted doc-string and regular expression*

最後，針對 Anaconda 使用者，我們正在實驗 Conda 的偵測和整合。Finally, for Anaconda users, we are experimenting with detection and integration of conda. 啟用時，您的 Conda 環境會自動出現在 Visual Studio 中；我們也會使用 Conda 而非 pip 來管理套件。When enabled, your conda environments will appear within Visual Studio automatically, and we will use conda rather than pip to manage packages. 如需詳細資訊，請參閱 What's new for Python in Visual Studio 15.6 (Visual Studio 15.6 的 Python 新功能) 部落格文章。See the what's new for Python in Visual Studio 15.6 blog post for more information.

Team ExplorerTeam Explorer

我們已新增更多對 Git 標記的支援。We have added more support for Git tags. 在 [標記] 頁面上，您可以查看存放庫中的所有標記。On the Tags page, you can view all of the tags in your repo. 您可以建立、刪除和推送標記 (這是我們在 UserVoice) 最常要求的功能之一，您也可以從標記建立新的分支。You can create, delete, and push tags (which was one of our most requested features on UserVoice), and you can also create a new branch from a tag.

針對 Visual Studio Team Services 使用者，您現在可以查看提取要求分支。For Visual Studio Team Services users, you can now check out pull request branches. 這項功能可讓您更輕鬆檢閱提取要求、測試變更，並建置程式碼。This feature makes it easier to review pull requests, test changes, and build your code.

安裝程式Setup

我們已新增支援以暫停 (圖 12) 您的安裝，並繼續 (圖 13) 稍後進行。We've added support to pause (Figure 12) your installation and resume (Figure 13) it at a later time.

*(圖 12) 暫停您的安裝(Figure 12) Pause your installation*

*(圖 13) 繼續安裝(Figure 13) Resume your installation*

擴充性Extensibility

許多 Visual Studio 可執行檔的檔案版本– devenv.exe、blend.exe、wdexpress.exe 和 vsga.exe –現在會反映次要版本，例如 15.6. *。File versions for a number of Visual Studio executables – devenv.exe, blend.exe, wdexpress.exe, and vsga.exe – now reflect the minor release, for example 15.6.*.

注意

這不會影響任何功能，但如果外部程式碼會依賴可執行檔版本號碼，則可能要更新該程式碼。This does not affect any functionalities, but external code relying on executable file version numbers may need to be updated.

偵錯和診斷Debugging and Diagnostics

CPU 使用量工具CPU Usage Tool

[CPU 使用量] 工具 (在 [診斷工具] 視窗和 ALT-F2 效能分析工具中進行 F5 錯時可用) 現在會根據特定程式程式碼的 CPU 耗用量來顯示原始程式列醒目提示 (圖 14)。The CPU Usage tool (available during F5 Debugging in the Diagnostic Tools window and in the ALT-F2 Performance Profiler) now displays source line highlighting based on the CPU consumption of specific lines of code (Figure 14).

當您檢視 CPU 使用量工具的 [呼叫樹狀圖] 檢視或 [呼叫端/被呼叫端] 檢視時，會顯示所選取函式的來源以及該函式上每個原始程式碼所指出的 CPU 耗用量。When you view the Call Tree or Caller/Callee views of the CPU Usage tool, the source for the selected function is displayed with CPU consumption indicated on each source line of the function.
如果函式的 CPU 效能是個考量，您就可以趁這時具體判斷函式的哪些原始程式碼要為函式執行時的 CPU 耗用量負責。If CPU performance of a function is a concern, now you can determine specifically what source lines of the function are responsible for the CPU consumption when the function was executing.

注意

此功能需要在產生的 PDB 中包含來源資訊 (由專案設定來控制)。This feature requires that source information be included in the generated PDB which is controlled by the project settings. 如果專案的 PDB 不含來源資訊，就無法顯示程式碼屬性或原始程式檔。Projects for which PDBs do not have source information will be unable to display either the line attribution or the source file.

*(圖 14) CPU 使用量工具與原始程式列反白顯示(Figure 14) CPU Usage tool with source line highlighting*

支援執行緒名稱Thread Name Support

根據使用者的意見反應，偵錯工具現在可以在傾印的偵錯工具中顯示透過 >setthreaddescription api 所設定的執行緒名稱。Per user feedback, the debugger is now able to display thread names that are set via SetThreadDescription APIs in dump debugging. 這項功能需要在 Windows 10 Fall Creators Update 或更新版本組建上收集傾印。This feature requires dumps to be collected on Windows 10 Fall Creators Update or later builds.

Key VaultKey Vault

我們已新增 15.6 Preview 1 的 Azure 服務驗證延伸模組。We've added the Azure Services Authentication Extension in-box for 15.6 Preview 1. 針對使用 Microsoft.Azure.Services.AppAuthentication 程式庫的專案，其可讓它們使用 Visual Studio 帳戶來存取 Azure 資源 (例如 Key Vault)。This will allow projects that use the Microsoft.Azure.Services.AppAuthentication library to access Azure resources such as Key Vault using their Visual Studio accounts.

部落格Blogs

善用開發人員工具部落格網站中提供的深入解析及建議。 Take advantage of the insights and recommendations available in the Developer Tools Blogs site.

開發人員工具部落格讓您能夠隨時取得最新版本，並包含各類功能的深入探討文章。The Developer Tools Blogs keep you up-to-date on all new releases and include deep dive posts on a broad range of features. 若要深入了解 .NET 世界，請前往 DotNet 部落格。For insights into the .NET world, check out the DotNet Blog. 您可以在各語言區域小組部落格找到詳細的專業知識—例如 C#、VB、C++ 及 F#—而這只是冰山一角。You can find detailed expertise in each language area team blog — C#, VB, C++ and, F# — to name a few.

Visual Studio 2017 版本資訊歷程記錄 Visual Studio 2017 Release Notes History

如需舊版 Visual Studio 2017 的詳細資訊，請參閱 Visual Studio 2017 版本資訊歷程記錄頁面。For more information relating to past versions of Visual Studio 2017, see the Visual Studio 2017 Release Notes History page.

頁首 Top of Page