Visual Studio Icon Visual Studio 2017 15.7 版版本資訊Visual Studio 2017 version 15.7 Release Notes


| 開發人員社群 | 系統需求 | 相容性 | 可散發程式碼 | 授權條款 | 部落格 | 已知問題 || Developer Community | System Requirements | Compatibility | Distributable Code | License Terms | Blogs | Known Issues |


注意

如果您是從非英文語言版本的頁面存取此頁面,並想查看最新的內容,請瀏覽此版本資訊頁面的英文版本。If you are accessing this page from a non-English language version, and want to see the most up-to-date content, please visit this Release Notes page in English. 若要變更此頁面的語言,請按一下You can change the language of this page by clicking the 頁尾中的 圖示並選取所要使用的語言。 icon in the page footer and selecting your desired language.


按一下按鈕以下載最新版的 Visual Studio 2017。Click a button to download the latest version of Visual Studio 2017. 如需安裝和更新 Visual Studio 2017 的指示,請參閱將 Visual Studio 2017 更新至最新版本For instructions on installing and updating Visual Studio 2017, see Update Visual Studio 2017 to the most recent release. 此外,請參閱如何離線安裝上的指示。Also, see instructions on how to install offline.


15.7 中的新功能What's New in 15.7

Visual Studio 部落格是 Visual Studio 工程小組提供產品見解的官方來源。The Visual Studio Blog is the official source of product insight from the Visual Studio Engineering Team. 您可以在下列文章找到有關 Visual Studio 15.7 版的深入資訊:You can find in-depth information about the Visual Studio 15.7 releases in the following posts:

Visual Studio 2017 15.7 版發行Visual Studio 2017 version 15.7 Releases

Visual Studio 2017 15.7 版公告Visual Studio 2017 version 15.7 Announcements

15.7 中值得注意的新功能Summary of Notable New Features in 15.7


15.7 中修正的常見問題Top Issues Fixed in 15.7

這些是 15.7 中已解決的客戶回報問題:These are the customer-reported issues addressed in 15.7:

查看 Visual Studio 2017 15.7 版中修正的所有客戶回報問題。See all customer-reported issues fixed in Visual Studio 2017 version 15.7.

The Developer Community Portal


15.7 新功能的詳細資料Details of What's New in 15.7

Release Notes Icon Visual Studio 2017 15.7.0 版Visual Studio 2017 version 15.7.0

於 2018 年 5 月 7 日發行released on May 07, 2018

15.7 的新功能New Features in 15.7

效能Performance

  • 在此版本中,我們改善了 C# 和 VB 專案的解決方案載入時間,平均減少了 20%。In this release, we improved solution load time for C# and VB projects by an average of 20%.
  • 在大型 .NET Core 專案中,我們減少載入 IntelliSense 的時間 25%。In large .NET Core projects, we reduced the time to load IntelliSense by 25%.
  • 在 Git 中切換分支時,不需要重新載入方案和專案即已移除強制回應進度對話方塊。When switching branches in Git, the modal progress dialog has been removed when solutions and projects do not need to be reloaded.

安裝 Visual StudioInstalling Visual Studio

  • 更新對話方塊提供您更新的詳細資料,例如新增功能、下載大小和最新更新版本。The update dialog provides more details about your update, such as what's new, the download size, and the latest update version.
  • 已改善儲存體驗:在您 更新 Visual Studio 之前,會_先_在本機儲存所有暫止的變更,再開始更新。Improved save experience: Before you update Visual Studio, all pending changes will be saved locally first -- before starting the update. 更新對話方塊將會顯示 [Save All & Update] (全部儲存並更新) 按鈕,而非 [立即更新]。The update dialog, will show a Save All & Update button instead of Update Now.
  • 我們已將下載快取、共用元件、一些 SDK 和工具移至不同磁碟機,來減少系統磁碟機上的安裝使用量 (圖 1)We reduced the installation footprint on the system drive by moving the download cache, shared components, some SDKs, and tools to different drives (Figure 1).
Install Locations
(圖 1) 選擇安裝位置(Figure 1) Choose install locations

您有三個位置可以管理,而這些位置只能透過第一次安裝來設定:There are three locations you can manage, and these locations can only be set with your very first installation:

  • Visual Studio 核心產品: 這個位置供專屬於您選取的 Visual Studio 安裝版本檔案使用。Visual Studio core product: This location is for files that are specific to the version of Visual Studio you selected to install.
  • 下載快取: 安裝檔案和資訊清單將會下載至此位置。Download cache: Installation files and manifests will be downloaded to this location. 如果您取消核取此核取方塊來決定不保留下載快取,則請在安裝完成之後移除檔案。If you decide not to keep the download cache by unchecking the check box, the files will be removed after installation completes.
  • 共用元件、工具和 SDK: 此位置適用於並存 Visual Studio 安裝所共用的檔案。Shared components, tools, and SDKs: This location is for files that are shared by side-by-side Visual Studio installations.

注意

若工具和 SDK 對於其安裝位置有不同的規則,就不會安裝到這部磁碟機。Tools and SDKs that have different rules as to where they are installed, won’t be installed to this drive. 會優先採用工具/SDK 特定規則。The tool/SDK specific rules take precedence.

注意

使用者可以停用套件快取,以及設定位置。Users can disable the package cache and set the location.

Visual Studio IDEVisual Studio IDE

指出哪一個長時間執行的作業讓 Visual Studio 忙碌的對話方塊視窗 (圖 2) 現在是可存取的螢幕助讀程式 (例如 NVDA、朗讀程式等等)。The dialog window (Figure 2) that indicates which long running operation is keeping Visual Studio busy, is now screen reader accessible (for example, NVDA, Narrator, etc.). Visual Studio 顯示對話方塊時,螢幕助讀程式會播放音訊提示,指出新資訊會顯示在螢幕上。When the dialog is shown by Visual Studio, the screen reader plays an audio cue indicating new information is visible on the screen. 在朗讀程式中叫用 [變更檢視] 命令,使用者即可閱讀對話方塊的內容,或與可用的 [取消] 按鈕互動。Users can read the contents of the dialog or interact with the Cancel button when available by invoking the Change View command in Narrator.

Wait dialog
(圖 2) 載入中的對話方塊視窗,螢幕助讀程式現已可使用(Figure 2) Loading dialog window, now screen reader accessible

注意

如需完整朗讀程式支援,您必須使用 Windows 10 Redstone 4 (RS4) 組建。For full Narrator support, you must be using Windows 10 Redstone 4 (RS4) builds.

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

  • 此版本包含 PDB 檔案中本機資訊洩漏弱點的修正,如 CVE-2018-1037 中所述。This release contains a fix for a local information disclosure vulnerability in PDB files as described in CVE-2018-1037.
  • C5045 是新的編譯器診斷,可讓您查看編譯器已插入 Spectre 降低的程式碼模式。C5045 is a new compiler diagnostic that lets you see code patterns where the compiler would have inserted a Spectre mitigation.
  • Visual Studio 的配套 CMake 安裝已經從 3.10 升級至 3.11。Visual Studio's bundled CMake installation has been upgraded from 3.10 to 3.11.
  • CMake 專案支援 C++ 程式碼的靜態分析 (例如 VCXProj)。CMake projects support static analysis of C++ code, such as VCXProj.
  • MSVC 支援 C++17 功能 P0426R1 "constexpr for std::char_traits",以讓 std::string_view much 在編譯時間更為實用。MSVC supports the C++17 feature P0426R1 "constexpr for std::char_traits," which makes std::string_view much more usable at compile time.
  • 在每個單元測試上方使用 CodeLens 執行、偵錯和檢視測試狀態 (圖 3)Use CodeLens above each of your unit tests to Run, Debug, and view Test Status (Figure 3).
Use CodeLens above each of your unit tests
(圖 3) 在每個單元測試上方使用 CodeLens(Figure 3) Use CodeLens above each of your unit tests
  • 我們更新了 C++ 的 Visual Studio iOS 開發工具,可搭配 Xcode 9 使用。We updated the Visual Studio iOS development tools for C++ to work with Xcode 9.
  • 我們已將 /analyze:ruleset 選項新增至 cl.exe,根據規則集組態篩選來減少 C++ Code Analysis 工具中的訊息。We added /analyze:ruleset option to cl.exe for filtering down warnings in the C++ Code Analysis tools based on ruleset configuration. 這會導致獨立叫用編譯器與 IDE 之間的一致體驗,並且透過只執行規則集中所提及的規則來改善效能。This results in a consistent experience between standalone invocations of the compiler and the IDE and improves performance by running only the rules mentioned in ruleset.
  • 繼承建構函式的運作方式現在與繼承任何其他基底類別成員相同。Inheriting a constructor now works the same as inheriting any other base class member. 先前,做法是宣告委派給原始的新建構函式;運用這項變更,衍生類別中會出現基底類別建構函式,就像它們是衍生類別建構函式一樣,進而改善 C++ 中的一致性。Previously, this worked by declaring a new constructor that delegates to the original; with this change, base class constructors are visible in a derived class as if they were derived class constructors, improving consistency in C++.
  • 設計成採用任何型別作為非型別參數的範本,現在可以使用範本參數清單中的 auto 關鍵字。Templates that are designed to take any type as a non-type parameter can now use the auto keyword in the template parameter list. 這允許具現化使用任何型別,而不需要在具現化時判斷和提供範本參數型別。This allows instantiations to use any type instead of needing to determine and supply the type of template parameter at the point of instantiation.
  • 現在支援 std::launderstd::launder is now supported.
  • 在幾乎所有情況下,兩階段名稱查閱都會正確地運作。Two-phase name lookup operates correctly in almost all cases. 未來的更新會修正一些邊緣情況 (例如多載運算子的非依存函式呼叫)。Some edge cases, such as non-dependent function calls to overloaded operators, will be fixed in a future update.
  • MSVC 編譯器工具組符合 C++ 17 標準。The MSVC compiler toolset conforms with the C++ 17 Standard. 使用 /Zc:__cplusplus 參數編譯時,__cplusplus 巨集的值會反映正確的標準版本號碼。When compiling with the /Zc:__cplusplus switch, the value of the __cplusplus macro reflects the correct Standard version numbers.
  • Visual C++ 執行階段支援針對 Spectre 變體 1 的弱點降低。The Visual C++ Runtime supports mitigations for the Spectre variant 1 vulnerability. 工具組包含降低和非降低版本的 DLL。The toolset includes mitigated and non-mitigated versions of the DLLs. 在 [程式碼產生] 屬性頁中啟用「Spectre 降低」功能也會連結至降低版本的 DLL。Enabling the Spectre Mitigation feature in the Code Generation property page will also cause linking to the mitigated version of the DLL. Visual C++ 小組部落格提供 Spectre 降低的詳細資訊More information about Spectre mitigations is available on the Visual C++ Team Blog.
  • 在非最佳化組建 (/Od) 中啟用 Spectre 降低的編譯器支援。Enabled compiler support for Spectre mitigations in non-optimized builds (/Od).
  • 現在預設會啟用 /Zf 參數,以在使用多個編譯處理序時更快速地產生 PDB。The /Zf switch is now enabled by default, which enables faster PDB generation when using multiple compilation processes.
  • 我們大幅改善了 /await 的程式碼產生。We significantly improved the code generation for /await. 我們已重新實作程式碼產生器中的協同程式來改善可靠性,並修正大量的 Bug。We re-implemented coroutines in the code generator to improve reliability, fixing the vast majority of bugs.
  • CMake 目標檢視提供一種替代方式,在 [方案總管] 中檢視 CMake 專案來源;與資料夾型檢視不同,它會將程式碼組織為個別 CMake 目標 (圖 4)The CMake Targets View provides an alternative way to view a CMake project's source in the Solution Explorer; instead of a folder-based view, it organizes the code into individual CMake targets (Figure 4). 組織類似 CMake "Visual Studio" 產生器所建立之專案和方案檔的組織。The organization is similar to the organization of the Project and Solution files created by the CMake "Visual Studio" generator.
CMake Targets View
(圖 4) CMake 目標檢視(Figure 4) CMake Targets View
  • 透過 CMake 功能表,或以滑鼠右鍵按一下方案總管中的原始程式檔,即可個別建置 CMake 專案所屬的原始程式檔 (.cpp)。Source files (.cpp) belonging to CMake projects can be built individually via the CMake menu or by right-clicking on a source file in the Solution Explorer.
  • 導致標記剖析錯誤的未知巨集現在會加上綠色波浪線底線。Unknown macros that cause tag-parsing errors are now underlined with green squiggles. 提供快速動作,以自動將巨集新增至 C++ Hint 檔案來解決此問題。A quick action is available to automatically add the macro to a C++ Hint file to resolve the issue. 按一下 [專案] 功能表上的 [Display Tag Parser Errors ] (顯示標記剖析器錯誤),即可列出解決方案或資料夾中的所有標記剖析錯誤。All tag-parsing errors in the Solution or folder can be listed by clicking Display Tag Parser Errors on the Project menu.
  • 在 [開啟資料夾] 中,使用快速動作將標頭新增至 CppProperties.json include 路徑。Add headers to the CppProperties.json include path with quick actions in Open Folder.
  • 現在會自動下載 Linux 和 Unix 這類系統的標題,以供 Windows 上的 IntelliSense 使用。Headers from Linux and Unix-like systems are now automatically downloaded for use by IntelliSense on Windows. 這些也用來提供 Linux 原生平台開發的增強 IntelliSense 體驗。These are also used to provide an enhanced IntelliSense experience for Linux native Platform development.
  • 我們已新增五個新規則來強制執行 C++ Core Guidelines 中有關使用 Guidelines Support Library 的項目。We added five new rules enforcing items from the C++ Core Guidelines regarding use of the Guidelines Support Library.
  • 我們允許彙總型別中的公用基底類別,因此它們是使用彙總初始化語法進行初始化,而不需要撰寫未定案建構函式。We allow public base classes in aggregate types, so that they can be initialized using aggregate initialization syntax without writing boilerplate constructors. 在以括弧括住的初始設定式清單中,會先初始化基底,後面接著資料成員。In the braced initializer list, bases are initialized first, followed by data members.
  • 將函式的樣板引數推斷延伸至範本類別的建構函式;當您建構類別範本時,不再需要指定引數。Extend template argument deduction for functions to constructors of template classes; when you construct a class template, it is no longer necessary to specify the arguments.
  • C++17 已變更限定性條件轉換的定義。C++17 has changed the definition of qualification conversions. 先前,這些在多層級指標與混合指標之間是允許的,因此通常可以在第一個層級以外的層級新增限定詞;不過,這不會同樣地套用至陣列。Previously, these were permitted between multi-level pointers and mixed pointers, such that qualifiers could often be added at levels other than the first; however, this did not similarly apply to arrays.
  • 針對先前遺留給編譯器實作詳細資料 (例如,成員存取、指派和陣列索引) 的主要 C++ 運算子,精簡運算式評估順序Refined the expression evaluation order for major C++ operators that were previously left to compiler implementation detail, for example, member access, assignment, and array index.
  • 擴充 using 宣告以支援 variadic 基底類別成員的套件擴充語意,然後用於衍生類別內。Expand the using declaration to support pack expansion semantics for variadic base class members, which can then be used inside the derived class.
  • 我們現在已完成運算式 SFINAE 的完整實作,並且已進行對應的「標準範本程式庫」變更。We are now complete with the full implementation of Expression SFINAE, and made the corresponding Standard Template Library changes.
  • 我們已實作符合 ISO C++17 標準的平行演算法。We implemented parallel algorithms conforming to the ISO C++17 standard. 如需詳細資訊,請參閱位於 [VSInstallDir]\VC\Tools\MSVC\<ver>\include\yvals.h 的原始程式檔。See the source file located at [VSInstallDir]\VC\Tools\MSVC\<ver>\include\yvals.h for additional details.
  • 在 /std:c++17 模式中,警告層級 C4834 (「捨棄屬性為 'nodiscard' 之函式的傳回值」) 已從 W3 增加至 W1。In /std:c++17 mode, the warning level of C4834 ("discarding return value of function with 'nodiscard' attribute") is increased from W3 to W1. 此外,編譯器現在可以推斷以 auto 宣告之非型別範本引數的型別。In addition, the compiler can now deduce the type of a non-type template argument that is declared with auto.
  • 使用 /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.
  • C++ Core Check 現在是原生程式碼分析之預設工具組的一部分。C++ Core Check is now part of the default toolset for native code analysis. 只要對專案執行程式碼分析,除了預設建議規則之外,還會從 C++ Core Check 啟用規則子集。Whenever code analysis is executed over a project, a subset of rules is enabled from C++ Core Check in addition to default recommended rules.
  • 我們已新增 Linux 專案的平行編譯支援,這可能會大幅改善建置時間。We added parallel compilation support for Linux projects, which may significantly improve build times. 這可以透過 [屬性頁] > [C/C++] > [Max Number of Parallel Compilation Jobs] (平行編譯作業數目上限) 予以啟用。This can be enabled via Property Pages > C/C++ > Max Number of Parallel Compilation Jobs.
  • 已新增 [公用專案 Include 目錄] Linux 專案屬性來改善 Linux 方案中專案對專案參考之 Include 的使用。The "Public Project Include Directories" Linux project property has been added to improve consumption of includes from project-to-project references in Linux solutions.
  • 我們已新增 IDE 中 C++ 開發人員的 ClangFormat 支援We added ClangFormat support for C++ developers in the IDE. 與 EditorConfig 類似,您可以使用 ClangFormat 在您鍵入時自動設定程式碼的樣式和格式,在某種意義上,可以在您的開發小組之間強制執行。Similar to EditorConfig, you can use ClangFormat to automatically style and format your code as you type, in a way that can be enforced across your development team.

C# 編譯器C# Compiler

除了錯誤修正之外,此版本還提供下列 C# 7.3 功能:In addition to bug fixes, this release brings the following C# 7.3 features:

PythonPython

  • 您可以滑鼠右鍵按一下專案,並選取 [Python] > [MyPy],以在專案上執行 MyPy。You can run MyPy on a project by right-clicking on the project and selecting Python > MyPy. MyPy 將根據型別提示來檢查程式碼,而且任何偵測到的型別錯誤都會顯示在錯誤清單中。MyPy will check your code against type hints, and any type errors detected will be shown in the error list.
  • 您可以建立和使用 Conda 環境,以及使用 pip 或 Conda 管理 Conda 環境的套件。You can create and use Conda environments as well as manage packages for your Conda environments using pip or Conda.
  • Anaconda 5.1.0 版現在可以從 Visual Studio 安裝程式提供,而且預設會在選取資料科學工作負載時安裝。Anaconda version 5.1.0 is now available from the Visual Studio Installer and is installed by default when the Data Science workload is selected.
  • 我們已根據熱門開放原始碼 pydevd 偵錯工具新增 Python 偵錯工具 ptvsd 4.0 版本的選擇加入。We added an opt-in to the ptvsd 4.0 version of the Python debugger based on the popular open source pydevd debugger. 「選擇加入」可提升應用程式掃描的效能偵錯速度,啟用方式是選取 [工具] > [選項] > [Python] > [實驗性] 中的 [Use experimental debugger] (使用實驗性偵錯工具)。The opt-in offers faster debugging performance for applicationscan and can be enabled by checking Use experimental debugger from Tools > Options > Python > Experimental.
  • 如需使用偵錯工具、Conda、MyPy 和型別提示的詳細資訊,請參閱 Visual Studio 15.7 中的 Python 部落格文章Check out the Python in Visual Studio 15.7 blog post for more on using the debugger, Conda, MyPy, and type hints.

Visual Studio Tools for XamarinVisual Studio Tools for Xamarin

這個版本包含 Xamarin.Android 8.3Xamarin.iOS 11.10This release includes Xamarin.Android 8.3 and Xamarin.iOS 11.10.

自動 Android SDK 管理Automatic Android SDK Management

載入 Xamarin.Android 專案時,Visual Studio 可以判斷電腦是否遺漏專案所使用的 Android API 層級,並且在背景自動安裝它。When a Xamarin.Android project is loaded, Visual Studio can determine if the Android API level used by the project is missing from your machine and automatically install it for you in the background. 若要啟用此功能,請移至 [工具] > [選項] > [Xamarin] > [Android 設定] > [自動安裝 Android SDK]。To enable this feature, go to Tools > Options > Xamarin > Android Settings > Auto Install Android SDKs.

改善的 XAML IntelliSenseImproved XAML IntelliSense

使用 Visual Studio 2017 15.7 版的 Xamarin.Forms 開發人員將會注意到大幅改善的 IntelliSense 體驗 (圖 5)Xamarin.Forms developers using Visual Studio 2017 version 15.7 will notice a vastly improved IntelliSense experience (Figure 5). Xamarin.Forms XAML 編輯體驗現在採用提供 WPF 和 UWP 的相同 IntelliSense 引擎技術。The Xamarin.Forms XAML editing experience is now powered by the same IntelliSense engine that powers WPF and UWP. 這會啟用開發人員的許多增強功能,包含改善的比對、燈泡建議、程式碼瀏覽、進行 lint、資源完成和標記延伸完成。This brings many enhancements to developers, including improved matching, light bulb suggestions, code navigation, linting, resource completion, and markup extension completion.

Xamarin.Forms XAML editing experience
(圖 5) Xamarin.Forms XAML 編輯體驗(Figure 5) Xamarin.Forms XAML editing experience

條件式 XAML 的工具增強功能Tooling Enhancements for Conditional XAML

XAML 編輯器提供 IntelliSense 來編寫條件式 XAMLThe XAML editor provides IntelliSense for authoring conditional XAML. 使用不存在於您應用程式之目標最小版本的型別時,XAML 編輯器現在不僅會發出警告,還會提供數個選項進行修正。When using a type that is not present in the target min version of your app, the XAML editor now not only warns, but also, provides several options to fix it.

自動 iOS 佈建Automatic iOS Provisioning

我們已進行 iOS 裝置佈建,讓開發更為簡單 (圖 6)We made iOS device provisioning for development easier (Figure 6). 在 Visual Studio 2017 15.7 版中,具有流暢的體驗可要求開發憑證、產生簽章金鑰、在開發人員中心內新增裝置,並建立佈建設定檔,而且只要按一下按鈕就可以完成所有這些作業。In Visual Studio 2017 version 15.7, there's a streamlined experience to request a development certificate, generate a signing key, add a device in the Developer Center, and create a provisioning profile, all with a single button click. 所有難度較高的 iOS 裝置佈建都會在 30 秒內為您處理。All the heavy lifting of provisioning an iOS device is handled for you in less than 30 seconds.

iOS & Android Project Templates
(圖 6) 使用自動 iOS 佈建功能,讓佈建 iOS 應用程式更為簡單。(Figure 6) Provisioning iOS apps got easier with our automatic iOS provisioning feature.

Android SDK 管理Android SDK Management

找出哪些針對進行行動裝置開發所安裝的 Android SDK 最為耗時。Figuring out what Android SDKs to install for mobile development can be time consuming. Visual Studio 2017 15.7 版新增可管理 Android SDK 安裝的 Android SDK 管理員。Visual Studio 2017 version 15.7 adds a new Android SDK manager that takes the guesswork out of managing Android SDK installations. 開啟未安裝 SDK 的專案來建置專案之後,會出現提示,協助您下載必要 SDK。After opening a project for which you don’t have SDKs installed to build it, a notice will appear to help you download the required SDKs. 按一下 [Download & Install] (下載並安裝) 並接受相關的授權合約之後,會自動在背景中為您安裝正確的 SDK。After clicking Download & Instal and accepting the relevant license agreement, the correct SDKs will automatically be installed in the background for you.

新的 iOS & Android 專案範本New iOS & Android Project Templates

無論您是新的或經驗豐富的 Xamarin 開發人員,專案範本都是應用程式建置旅程的重要部分。Whether you’re a new or seasoned Xamarin developer, project templates are an important part of the app building journey. 您應該可以輕鬆地找到它們,而且它們可讓您成功進行 (圖 7)They should be easy to find and set you up for success from the start (Figure 7). 在此版本中,我們已完成重建 iOS 和 Android 原生專案範本,以取得較佳的探索能力並支援新式瀏覽模式 (例如飛出視窗或底部索引標籤)。In this release, we completely rebuilt our iOS and Android native project templates for better discoverability and support for modern navigation patterns like flyout or bottom tabs.

iOS & Android Project Templates
(圖 7) 輕鬆地找到並設定 iOS & Android 專案範本(Figure 7) Easy to find and set your iOS & Android Project Templates

安裝的改善Improvements to Installation

Visual Studio 安裝程式隨附於已更新的 Android SDK 組態 (包含 Android API 27 和 Android SDK Tools 26)。The Visual Studio Installer ships with an updated Android SDK configuration, including Android API 27 and Android SDK Tools 26. 這包含快速開機支援,以在五秒內啟動 Android 模擬器。This includes support for quick boot, which enables your Android emulator to boot in less than five seconds.

此外,我們已包含 Android Device Manager 作為使用 .NET 工作負載進行 Mobile 開發的一部分,輕鬆地建立、編輯和刪除模擬器。Additionally, we include the Android Device Manager as part of the Mobile development with .NET workload to easily create, edit, and delete emulators.

.NET 生產力改善.NET Productivity Improvements

  • 使用「快速動作和重構」 (Ctrl+.) 以:Use Quick Actions and Refactorings (Ctrl+.) to:
    • for 轉換成 foreach,反之亦然。Convert for-to-foreach, and vice versa.
    • 將私用欄位設為 readonlyMake private fields readonly.
  • LINQ 查詢子句和解構現在支援 [移至定義] (F12)。Go To Definition (F12) is now supported for LINQ query clauses and deconstructions.
  • 使用 Ctrl+.Use Ctrl+. 切換 var 與明確型別,不論您的程式碼樣式喜好設定為何。to toggle between var and the explicit type, regardless of your code style preferences.
  • [快速諮詢] 會顯示 Lambda 和區域函式的擷取,讓您可以查看哪些變數是在範圍內。Quick Info shows captures on lambdas and local functions, so you can see what variables are in scope.
  • 「變更簽章」重構 (在簽章上按 Ctrl+.Change Signature refactoring (Ctrl+. ) 作用於區域函式。on signature) works on local functions.
  • 您可以就地編輯 .NET Core 專案檔,以開啟包含資料夾、還原索引標籤,並且完整支援其他編輯器功能。You can edit .NET Core project files in-place, so opening containing folder, restoring tabs, and other Editor features are fully supported. IDE 變更 (例如新增連結的檔案) 將會與編輯器中的未儲存變更合併。IDE changes, such as adding a linked file, will be merged with unsaved changes in the editor.

測試Testing

  • Live Unit Testing 可使用內嵌 pdb 以及指定 /deterministic 的 pdb。Live Unit Testing works with embedded pdbs and pdbs specifying /deterministic.
  • 我們為使用參考組件的專案新增了 Live Unit Testing 支援。We added Live Unit Testing support for projects that use reference assemblies.
  • 測試清單編輯器在測試執行期間有更多回應圖示。The Test Explorer has more responsive icons during test runs. 進行測試回合時,目前執行中測試的旁邊會出現進度環,暫止執行的測試則會出現時鐘圖示。When a test run is in progress, a progress ring appears next to tests that are currently executing, and a clock icon appears for tests that are pending execution.

Web 工具Web Tools

  • ASP.NET Web 應用程式專案範本已經更新成較新版本的相依套件。The ASP.NET Web Application project templates have been refreshed to newer versions of the dependent packages.
  • 您可在 Linux 上將非容器化應用程式發佈至 Azure App Service。You can publish your non-containerized applications to Azure App Service on Linux.
  • 連結以在 Cloud Explorer 的 [發行摘要] 頁面中開啟 Azure App Service。Link to open your Azure App Service in Cloud Explorer from the Publish Summary page.
  • 您可取得發佈 .NET Core 架構相依和獨立應用程式的支援。You have support for publishing .NET Core framework dependent and self-contained applications.
  • 將 F# 應用程式的支援發行至 App Service 和資料夾。Publish support for F# applications to App Service and folder.
  • 我們已新增直接在 IIS Express 處理序中裝載 ASP.NET Core 應用程式的支援。We added support for hosing ASP.NET Core applications directly in the IIS Express process.
  • 您可以建立儲存體帳戶,並提供在發佈至新的 Azure App Service 時,要儲存在 App Service 設定中的連接字串名稱。You can create a storage account and provide a connection string name to be stored in App Service settings when publishing to a new Azure App Service.
  • 我們已在偵錯期間改善 Kestrel HTTPs 支援。We improved Kestrel HTTPs support during debugging.
  • ASP.NET Core 應用程式支援專案屬性 [應用程式 URL] 欄位中有多個分號分隔的值。ASP.NET Core applications support multiple semi-colon separated values in the "App URL" field under project properties. 此欄位中出現多個 URL 時,會使用第一個 URL 來啟動瀏覽器。When multiple URLs are present in this field, the first one is used to launch the browser.
  • 透過命令列 (即將提供 GUI 支援) 提供稱為「身分識別」的新框架,以將身分識別管理 UI 新增至 ASP.NET Core 2.1 應用程式。New scaffolder called "Identity" is available via the command line (GUI support coming soon), which adds identity management UI to your ASP.NET Core 2.1 applications.
  • ASP.NET 和 ASP.NET Core 專案可以設定 "Key Vault" 連線服務,來建立 Azure Key Vault,並在 IDE 內建立它與其 Web 應用程式的關聯。ASP.NET and ASP.NET Core projects can create and associate Azure Key Vaults with their web applications within the IDE by configuring the "Key Vault" Connected Service.
  • ASP.NET 或 ASP.NET Core 應用程式與 Azure Key Vault 相依時,如果應用程式無法使用 [工具] > [選項] > [Azure 服務驗證] 下選取的帳戶,在執行階段從開發人員的電腦存取該 Key Vault,則會在錯誤清單中出現錯誤。When an ASP.NET or ASP.NET Core application depends on Azure Key Vault, an error appears in the error list if the app is unable to access that Key Vault at runtime from the developer’s machine given the account selected under Tools > Options > Azure Service Authentication. 這會縮短探索和更正權限或帳戶問題的時間,並避免在執行階段發生應用程式失敗。This shortens the time to discover and correct the permission or account issue and avoid an application failure at runtime.
  • Web 應用程式使用所選取 ASAL 使用者帳戶沒有存取權的 KeyVault 時,[錯誤清單] 中現在會出現警告。When your web app consumes a KeyVault to which your selected ASAL user account has no access, a warning will now appear in the Error List.

Visual Studio 2017 Build ToolsVisual Studio 2017 Build Tools

Azure、UWP 和其他工作負載支援Support for Azure, UWP, and Other Workloads

Visual Studio 2017 Build Tools 支援大部分 Visual Studio 專案的命令列組建。Visual Studio 2017 Build Tools support command-line builds for most Visual Studio projects. 支援的專案包含:ASP.NET、Azure、C++ Desktop、ClickOnce、容器、.NET Core、.NET Desktop、Node.js、Office 和 SharePoint、Python、TypeScript、Unit Tests、UWP、WCF 以及 Xamarin。Supported projects include: ASP.NET, Azure, C++ desktop, ClickOnce, containers, .NET Core, .NET Desktop, Node.js, Office and SharePoint, Python, TypeScript, Unit Tests, UWP, WCF, and Xamarin. 我們預期未來版本會新增 SQL 的支援。We expect to add support for SQL in a future release. Visual Studio Build Tools 現在也支援在容器內安裝Visual Studio Build Tools now also support installing into a container. 您可以從 Visual Studio 下載下載 Visual Studio Build Tools。You can download Visual Studio Build Tools from Visual Studio Downloads. 您可在 Visual Studio Build Tools 2017 元件目錄中找到一組工作負載與元件識別碼,來自訂您的容器映像。A list of workload and component IDs with which you can tailor your container image can be found in the Visual Studio Build Tools 2017 component directory.

注意

Build Tools 需要 Visual Studio 2017 的授權。Build Tools requires a license to Visual Studio 2017.

Visual Studio 2017 Build Tools 中的 UWP 支援UWP Support in Visual Studio 2017 Build Tools

Visual Studio Build Tools 可讓您建立組建伺服器,而不需要安裝完整的 Visual Studio。Visual Studio Build Tools allow you to create build servers without installing all of Visual Studio. 為了回應客戶的要求,我們會持續強化 Visual Studio Build Tools 以支援其他專案類型。In response to customer requests, we enhanced Visual Studio Build Tools to support additional project types. 這些專案類型包含 UWP 工具,為 ASP.NET、Azure、C++ Desktop、ClickOnce、容器、.NET Core、.NET Desktop、Node.js、Office 和 SharePoint、Python、TypeScript、Unit Tests、UWP、WCF 以及 Xamarin 提供支援。These project types include UWP tools, bringing the supported project list ASP.NET, Azure, C++ desktop, ClickOnce, containers, .NET Core, .NET Desktop, Node.js, Office and SharePoint, Python, TypeScript, Unit Tests, UWP, WCF, and Xamarin. 我們預期未來版本會新增 SQL 的支援。We expect to add support for SQL in a future release.

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

  • 具有 XAML 設計工具最新更新的 Blend 提供視覺狀態管理和動畫工具。Visual State Management and Animation tooling is available in Blend with the latest updates to the XAML Designer. 所有 UWP 開發人員都可以存取這些工具。All UWP developers have access to these tools. 此外,XAML 的編輯與繼續可支援編輯視覺效果狀態和動畫。In addition, XAML Edit & Continue supports editing Visual States and Animations.
  • Windows Machine Learning automatic code generation (Windows Machine Learning 自動程式碼產生) 支援允許將 ONNX 模型檔案新增為專案中的現有項目,來產生 WinML 包裝函式類別。Windows Machine Learning automatic code generation support allows WinML wrapper classes to be generated by adding your ONNX model files as an existing item in the project.
  • Windows 10 April 2018 Update SDK (組建 17134) 是 Visual Studio 中通用 Windows 平台開發工作負載的預設 SDK。The Windows 10 April 2018 Update SDK (Build 17134) is the default SDK for the Universal Windows Platform development workload in Visual Studio.
  • 您可以使用 C# 和新的「選擇性程式碼套件」專案範本,在選擇性套件中建立具有程式碼執行的相關集合You can create related sets with code execution in optional packages using C# and the new Optional Code Package project template.
  • 使用新的「套件配置」項目範本,您可輕鬆地建構一般套件搭售方案With the new 'Package Layout' item template, you can easily construct flat package bundles.

APPX 套件中的 AppInstaller 支援AppInstaller Support in APPX Packages

通用 Windows 平台允許使用稱為「側載」的機制,在不使用 Microsoft Store 的情況下散發應用程式。The Universal Windows Platform allows distributing applications without the Microsoft Store by using a mechanism called “sideloading”. 此版本可讓您產生 appinstaller 檔案,以從 APPX 型部署取得自動更新。This release allows you to generate the appinstaller file to get automatic updates from your APPX based deployments. 深入了解基礎技術Learn more about the underlying technology.

NuGetNuGet

  • 此版本提供根據 packages.config 將現有專案移轉至 PackageReference 的預設支援。This release provides out of the box support for migrating existing projects based on packages.config to PackageReference.

  • 我們已新增 NuGet 套件簽章支援。We added support for NuGet package signatures. 安裝或還原簽署套件時會先驗證數位簽章,再擷取套件內容。Installing or restoring signed packages validates the digital signature before extracting the packages content. 如果簽章驗證失敗 (例如,內容已遭竄改、憑證無效等等),則會因 [錯誤清單] 中顯示的組建錯誤而封鎖作業。If the signature validation fails (for example, the content has been tampered with, invalid certificate, etc.) the operation will be blocked with a build error that is shown in the Error List.

TypeScript 和 JavaScriptTypeScript and JavaScript

TypeScript 2.8 RC 現在隨附於 Visual Studio 2017 15.7 版。TypeScript 2.8 RC is now included in Visual Studio 2017 version 15.7.
此版本提供下列改善:This release brings the following improvements:

  • jsconfig.json 支援,此檔案可以協助控制您的編輯器選項,就像 tsconfig.json 一樣。Support for jsconfig.json, a file that can help control your editor options much like tsconfig.json.
  • 透過關閉未開啟檔案的型別檢查來減少資源使用量的選項。An option to reduce resource usage by turning off type-checking for unopened files.
    • 這是 [工具] > [選項] > [TextEditor] > [JavaScript/TypeScript] > [專案] 下方的 [Only report diagnostics for files opened in the editor] /(僅限編輯器中已開啟檔案的報表診斷/) 選項。This is the only report diagnostics for files opened in the editor option under Tools > Options > TextEditor > JavaScript/TypeScript > Project.
  • TypeScript 和 JavaScript 使用者的新編輯功能New editing features for both TypeScript and JavaScript users:
    • 在檔案內套用所有快速修正。Applying all quick fixes within a file.
    • 組織匯入。Organize imports.
    • 類別中的 this. 以及 JSX 中的大括弧的完成。Completions for this. in classes and braces in JSX.
  • TypeScript 2.8 功能:TypeScript 2.8 features:
    • 條件式型別 (A extends B ? C : D)。Conditional types (A extends B ? C : D).
    • 新的 lib.d.ts 條件式型別協助程式,例如 NonNullableReturnTypeExtractExcludeNew lib.d.ts conditional type helpers such as NonNullable, ReturnType, Extract, and Exclude.
    • 已對應型別中修飾詞的細微控制。Granular control on modifiers in mapped types.
    • 使用新 // @jsx pragma 之檔案內 JSX Factory 的控制項。Control on JSX factories within files using the new // @jsx pragma.

您可以在 TypeScript 2.8 RC 部落格中深入了解 TypeScript 2.8。You can find more information on TypeScript 2.8 in the TypeScript 2.8 RC blog.

  • TypeScript 2.7 功能:TypeScript 2.7 features:
    • 嚴格屬性初始設定。Strict property initialization.
    • 數值分隔符號。Numeric separators.
    • 更聰明的型別成立條件。Smarter type guards.

您可以在 TypeScript 2.7 部落格中深入了解 TypeScript 2.7。You can find more information on TypeScript 2.7 in the TypeScript 2.7 blog.

我們也已修正客戶所引發的一些常見問題,包括過早觸發程式碼片段、無法取消重構、很難啟用格式化,以及不正確的 TypeScript 版本選取項目。We also fixed some of the top issues raised by customers, including premature triggering of snippets, uncancellable refactorings, hard-to-disable formatting, and incorrect TypeScript version selection.

注意

這些改善採用 TypeScript 2.8 技術。These improvements are powered by TypeScript 2.8. 為獲得最佳的體驗,請將現有專案更新為最新的 TypeScript 版本。For the best experience, update your existing projects to the latest TypeScript version.

使用 Microsoft Edge 的 JavaScript 偵錯JavaScript debugging with Microsoft Edge

Windows Insider 組建上的 Visual Studio ASP.NET 和 .NET 核心開發人員可以設定中斷點,並使用 Microsoft Edge 瀏覽器對其 JavaScript 檔案進行偵錯。Visual Studio ASP.NET and .NET core developers on Windows Insider builds, can set breakpoints and debug their JavaScript files using a Microsoft Edge browser. 以 Microsoft Edge 瀏覽器為目標時,Visual Studio 會使用 Microsoft Edge 小組所開發的新 Edge DevTools 通訊協定Visual Studio will use the new Edge DevTools Protocol developed by the Microsoft Edge team when targeting Microsoft Edge browser. 開發人員可以使用 Microsoft Edge 和 Google Chrome 瀏覽器偵錯並修正 Visual Studio 中的 JavaScript 問題。Developers can debug and fix JavaScript issues from within Visual Studio in both Microsoft Edge and Google Chrome browsers. 我們很高興我們的客戶啟用這個經常要求的功能。We are glad to enable this often-requested feature from our customers. 我們希望聽取您對功能的意見反應,協助我們改善並建置更好的 Visual Studio。We would love to hear your feedback on the feature to help us improve and build a better Visual Studio.

偵錯和診斷Debugging and Diagnostics

此版本新增來源連結的 VSTS 和 GitHub 驗證支援。This release adds VSTS and GitHub authentication support for Source Link. 如果可以透過 IDE 進行驗證,則會自動新增來源連結要求的驗證。Authentication will be added to Source Link requests automatically if it is available through the IDE. 如果使用者尚未通過驗證,則會顯示登入 UI 以啟用驗證。If the user is not already authenticated, the sign in UI will be shown to enable authentication.

支援 IntelliTrace 的回溯偵錯功能,以對 .NET Core 專案進行偵錯。IntelliTrace’s step-back debugging feature is supported for debugging .NET Core projects.

  • 若要啟用這項功能,請移至 [工具] > [選項] > [IntelliTrace] 設定,然後選取 [IntelliTrace events and snapshots] (IntelliTrace 事件與快照集) 選項。To enable the feature, go to Tools > Options > IntelliTrace settings, and select the IntelliTrace events and snapshots option.
  • IntelliTrace 的回溯偵錯功能支援在例外狀況發生時製作快照集。IntelliTrace's step-back debugging feature supports taking snapshots on exceptions. 若要啟用這項功能,請移至 [工具] > [選項] > [IntelliTrace] 設定,然後選取 [IntelliTrace events and snapshots] (IntelliTrace 事件與快照集) 選項 (圖 8)To enable the feature, go to Tools > Options > IntelliTrace settings, and select the option IntelliTrace events and snapshots (Figure 8).
Snapshot on exception
(圖 8) 例外狀況時的快照集(Figure 8) Snapshot on exception

啟動指令碼偵錯工具並將其附加至 ASP.NET 專案的 Microsoft EdgeLaunch and Attach Script Debugger to Microsoft Edge for ASP.NET Projects

您可以在使用 Google Chrome 作為您選擇的瀏覽器時,直接在 Visual Studio 中偵錯 JavaScript 和 TypeScript。You can debug both JavaScript and TypeScript directly in Visual Studio when using Google Chrome as your browser of choice. 您只需要在 Visual Studio 中選取 Chrome 作為您的瀏覽器,然後按 F5 鍵,即可進行偵錯。All you need to do is select Chrome as your browser in Visual Studio and hit F5 to debug. 如需其他資訊,請參閱 Client-side debugging of ASP.NET projects in Google (ChromeGoogle Chrome 中 ASP.NET 專案的用戶端偵錯)。See the Client-side debugging of ASP.NET projects in Google Chrome for additional information.

Team ExplorerTeam Explorer

在 [Team Explorer] 的 [Git 設定]、[全域設定] 中,有選項可以選擇 OpenSSL 或安全通道。In Git Settings, Global Settings in Team Explorer, there is an option to choose between OpenSSL and Secure Channel. 預設值是 OpenSSL。OpenSSL is the default.

適用於 6.2 Service Fabric 版本的 Service Fabric 工具Service Fabric Tooling for the 6.2 Service Fabric release

適用於 Service Fabric 6.2 版本的 Service Fabric Tools 可為 6.2 執行階段與 3.1 SDK 提供相容性支援。The Service Fabric Tools for the Service Fabric 6.2 release provide compatibility support for the 6.2 runtime and 3.1 SDK. 其中包括數項 Bug 修正,以及一項可將容器支援新增至現有 ASP.NET 或主控台專案的新功能。Along with several bug fixes, a new feature enables adding container support to existing ASP.NET or Console projects. .NET Framework 與 .NET Core 2.0 專案均享有透過新的 [新增協調流程] 操作功能表與對話方塊所提供的支援。Both .NET Framework and .NET Core 2.0 projects are supported through a new "Add Orchestration Support" context menu and dialog. 這些專案在新增 Service Fabric 協調流程支援後,就能在本機 Service Fabric 叢集上對其進行遠端部署與偵錯。Once these projects have added Service Fabric orchestration support, they can be deployed remotely and debugged on the local Service Fabric cluster.

Entity Framework Tools 改善Entity Framework Tools Improvements

F# 和 F# 工具改善F# and F# Tools Improvements

我們已對 F# 及其工具實作多項改善。We made many improvements to F# and its tools. 效能和清除現有 .NET SDK 樣式專案體驗已是此版本的焦點。Performance and cleaning up existing experiences with .NET SDK-style projects has been the focus for this release. 一如往常,我們也會收到令人讚嘆之 F# 社群的大量參與。As always, we also received significant contributions from the wonderful F# community.

F# 編譯器和核心程式庫改善F# Compiler and Core Library Improvements

  • 使用 .NET SDK 中的 F# 編譯器,啟用產生 F# AssemblyInfo 表單屬性。Enabled generating F# AssemblyInfo from properties with the F# compiler in the .NET SDK.
  • 在 Windows 上,F# .NET Core 編譯器支援 --debug:full--debug:full is supported for the F# .NET Core compiler on Windows.
  • 結構元組支援 MakeTupleMakeTuple is supported for struct tuples.
  • 現在可解析使用元組之擴充方法時的不必要警告An unnecessary warning when using an extension method for a tuple is now resolved.
  • MailboxProcessor.PostAndAsyncReply 在父處理序取消時會正確地處理取消作業。MailboxProcessor.PostAndAsyncReply properly handles cancellation when a parent process is cancelled.
  • 使用 NonStructuralComparison 時,float32 可別的相等性現在正確。Equality for float32 types is now correct when NonStructuralComparison is used.
  • 現在搜尋方法多載時會轉送警告,作者 Matthias DittrichWarnings are now forwarded when searching for method overloads, by Matthias Dittrich.
  • 在列舉上進行模式比對時發出警告的改善以發出不相符列舉的範例,作者 John WostenbergAn improvement to a warning when pattern matching on an enum to emit an example of an unmatched enum, by John Wostenberg.

F# 工具的改善F# Tooling Improvements

  • 已大幅縮減 F# 編譯器服務中的記憶體使用量,作者 Avi Avni 和 Microsoft。Significant reductions in memory usage in the F# Compiler Service, by Avi Avni and Microsoft.
  • 大幅提升 Unused Open Analyzer 在開啟時的效能。Significant performance improvements for the Unused Open Analyzer when it is turned on.
  • 改善 F# 分析器和程式碼修正開啟時的回應性,因此錯誤診斷的優先順序一律高於其餘項目。Improved responsiveness when F# analyzers and code fixes are turned on, such that error diagnostics are always prioritized above the rest.
  • 我們新增了適用於 F# 的 ASP.NET Core 範本。We added ASP.NET Core templates for F#.
  • 在貼入檔案的範圍頂端,.NET SDK 專案資料夾中已貼入檔案的初始順序現在已正確。The initial ordering for pasted files in folders for .NET SDK projects is now correctly at the top of the scope the file was pasted into.
  • 沒有專案檔的 F# 指令碼會在按 Alt+Enter 時將程式碼正確地傳送至 F# Interactive。F# scripts without a project file correctly sends code to F# Interactive when Alt+Enter is pressed.
  • F # 清單的偵錯工具檢視已從 50 個項目延伸到 5000 個項目。The debugger view for F# lists has been extended from 50 items to 5000 items.
  • 傳統 F# 專案 (僅限 .NET Framework) 也會執行設計階段組建,以減少解決方案載入時間。Classic F# projects (.NET Framework only) also perform design-time builds, which reduces solution load time.
  • 現在可以在 [設定] > [文字編輯器] > [F#] > [進階] 下方開啟 [Structured Guidelines] (結構化方針)和 [大綱] 檢視。The Structured Guidelines and Outlining views can now be toggled, under Settings > Text Editor > F# > Advanced.
  • F # 編譯器服務現在會傳回組件層級屬性。Assembly level attributes are now returned by the F# Compiler Service.
  • 我們已將 Entity.DeclaringEntity 新增至 F # 編譯器服務。We added Entity.DeclaringEntity to the F# Compiler Service.
  • 可以透過 F# 編譯器服務 API 進行最佳化,作者 Steffen ForkmannncaveOptimization is available via the F# Compiler Service API, by Steffen Forkmann and ncave.
  • GetDeclarationLocation 不再需要檔案來提供正確資料的結果,作者 amieresGetDeclarationLocation no longer requires a file to provide results on otherwise correct data, by amieres.
  • F# 符號 API 現在提供 IsNameGenerated,作者 Eugene AuduchinokIsNameGenerated is now available in the F# Symbols API, by Eugene Auduchinok.

F# 基礎結構改善F# Infrastructure Improvements

  • Mono 組建不再需要 autoconfautoconf is no longer required in our Mono build.
  • 所有 Visual Studio 整合專案現在使用 .NET SDK。All Visual Studio integration projects now use the .NET SDK.
  • [說明] > [關於 Microsoft Visual Studio] 現在會提供工具組建的認可雜湊。The commit hash for a build of the tools is available in Help > About Microsoft Visual Studio.

若要查看此版本引進的完整認可記錄,請參閱 15.7 發行標記To see the full commit log of what went into this release, check out our release tag for 15.7.


已知問題Known Issues

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

Visual Studio 2017 Known Issues


Release Notes Icon Visual Studio 2017 15.7.1 版Visual Studio 2017 version 15.7.1

於 2018 年 5 月 8 日發行released on May 08, 2018

15.7.1 中修正的常見問題Top Issues Fixed in 15.7.1

這些是 15.7.1 中已解決的客戶回報問題:These are the customer-reported issues addressed in 15.7.1:

  • 此版本包含可在載入解決方案期間減少記憶體使用率和 GC 壓力的修正。This release includes a fix that reduces memory usage and GC pressure during solution load.

Release Notes Icon Visual Studio 2017 15.7 版 資訊安全諮詢注意事項 Visual Studio 2017 version 15.7 Security Advisory Notice

於 2018 年 5 月 8 日更新updated on May 08, 2018

適用於 .NET Core 服務阻斷弱點的 Microsoft 資訊安全諮詢Microsoft Security Advisory for .NET Core Denial Of Service Vulnerability

CVE-2018-0765CVE-2018-0765

Microsoft 發佈此資訊安全諮詢的目的,是提供 .NET Core 與 .NET 原生版本 2.0 中有關弱點的資訊。Microsoft is releasing this security advisory to provide information about a vulnerability in .NET Core and .NET native version 2.0. 此諮詢也提供了指導,讓開發人員了解如何才能正確地更新應用程式來移除此弱點。This advisory also provides guidance on what developers can do to update their applications to remove this vulnerability.

Microsoft 注意到 .NET Framework 和 .NET Core 未正當處理 XML 文件時,會產生服務阻斷弱點。Microsoft is aware of a denial of service vulnerability that exists when .NET Framework and .NET Core improperly process XML documents. 成功惡意探索此弱點的攻擊者可能會使 .NET Framework、.NET Core 或 .NET 原生應用程式發生服務阻斷。An attacker who successfully exploited this vulnerability could cause a denial of service against a .NET Framework, .NET Core, or .NET native application.

本更新會修正 .NET Framework、.NET Core 和 .NET 原生應用程式處理 XML 文件的方式,進而解決該弱點。The update addresses the vulnerability by correcting how .NET Framework, .NET Core, and .NET native applications handle XML document processing.

若您的應用程式為 ASP.NET Core 應用程式,則我們也建議開發人員更新至 ASP.NET Core 2.0.8。If your application is an ASP.NET Core application, developers are also advised to update to ASP.NET Core 2.0.8.


Release Notes Icon Visual Studio 2017 15.7.2 版Visual Studio 2017 version 15.7.2 New Release icon

於 2018 年 5 月 21 日發行released on May 21, 2018

15.7.2 中修正的常見問題Top Issues Fixed in 15.7.2

這些是 15.7.2 中已解決的客戶回報問題:These are the customer-reported issues addressed in 15.7.2:


意見反應Feedback

請提供您的意見!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. 您也可以透過 UserVoice (英文) 提供產品建議,或透過即時聊天支援取得免費的安裝協助。You can also make a product suggestion through UserVoice or get free installation help through our Live Chat support.


部落格Blogs

善用「開發人員工具部落格」網站中的見解與建議,讓您能夠隨時取得所有新版本的最新資訊,以及涵蓋各類功能的深入探討文章。Take advantage of the insights and recommendations available in the Developer Tools Blogs site to keep you up-to-date on all new releases and include deep dive posts on a broad range of features.

Developer Tools Blogs


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

您可以檢視舊版的 Visual Studio 2017 版本資訊:You can view prior versions of Visual Studio 2017 release notes:


頁面頂端

Top of Page