Visual Studio Icon Visual Studio 2019 Preview 版本資訊Visual Studio 2019 Preview Release Notes


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


重要

此版本未正式運作,而不適用於實際執行電腦,或建立實際執行程式碼。This release is not "go-live" and not intended for use on production computers or for creating production code. 如需安裝及更新 Visual Studio 2019 的指示,請參閱將 Visual Studio 2019 更新至最新版本.文件。For instructions on installing and updating Visual Studio 2019, see this documentation on updating Visual Studio 2019 to the most recent release.


Visual Studio 2019 的新功能What's New in Visual Studio 2019

Visual Studio 2019 Preview 版本Visual Studio 2019 Preview Releases

Visual Studio 2019 部落格Visual Studio 2019 Blog

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


Release Notes Icon Visual Studio 2019 16.4 版 Preview 5Visual Studio 2019 version 16.4 Preview 5 New release icon

2019年11月14日發行released November 14, 2019

Visual Studio 2019 16.4 版 Preview 5 中修正的常見問題Top Issues Fixed in Visual Studio 2019 version 16.4 Preview 5


Release Notes Icon Visual Studio 2019 16.4 版 Preview 4Visual Studio 2019 version 16.4 Preview 4

發行於 2019 年 11 月 6 日released November 6, 2019

Visual Studio 2019 16.4 版 Preview 4 中已修正的常見問題Top Issues Fixed in Visual Studio 2019 version 16.4 Preview 4


Release Notes Icon Visual Studio 2019 16.4 版 Preview 3Visual Studio 2019 version 16.4 Preview 3

發行於 2019 年 11 月 4 日released November 4, 2019

Visual Studio 2019 16.4 版 Preview 3 中修正的常見問題Top Issues Fixed in Visual Studio 2019 version 16.4 Preview 3

16.4 Preview 2 和3中的已知問題Known Issue in 16.4 Preview 2 and 3

案例:Scenario:

  • 使用者已在其電腦上安裝 16.3.x,而且使用者具有 16.4 Preview 1User has 16.3.x installed on their machine and user has 16.4 Preview 1
  • 使用者升級為 16.4 Preview 2 或 16.4 Preview 3User UPGRADES to either 16.4 Preview 2 or 16.4 Preview 3
  • 從方塊中移除了 .NET 3.NET 3 is removed from the box
  • 16.3 .NET 3 開發中斷了16.3 .NET 3 development broke

解決方式:Resolution:

  • 在 16.3 上執行修復會修正環境。Running repair on 16.3 fixes the environment.

Visual Studio 2019 16.4 版 Preview 3 的新功能摘要Summary of What's New in Visual Studio 2019 version 16.4 Preview 3

  • XAML 設計工具縮放/位置現在預設為 [調整成畫面大小]。XAML Designer zoom/position now defaults to Fit All.
  • 新增了 [建立資料繫結] 對話方塊。Create Data Binding Dialog has been added.
  • 改進了 regions IntelliSenseImprovements to regions IntelliSense
  • XAML IntelliSense 中的程式碼片段Snippets in XAML IntelliSense
  • 在設計工具外以另一個視窗快顯 XAML 編輯器Pop-up XAML editor as a separate window from designer
  • 顯示參考組件的資源Displaying resources for referenced assemblies
  • 即時視覺化樹狀結構中的「只顯示我的 XAML」Just My XAML in Live Visual Tree
  • 合併資源字典Merge Resource Dictionary
  • 編輯範本現在可與協力廠商控制項搭配運作。Edit Template now works with controsl from 3rd party controls.

Visual Studio 2019 16.4 版 Preview 2 的新功能詳細資料Details of What's New in Visual Studio 2019 version 16.4 Preview 2

PythonPython

  • 即將推出 Python 3.8 的正式支援,但尚無法使用。Official support for Python 3.8 is coming soon, but not yet available. 如需可能會發生之問題的詳細資料,請參閱 Github 問題。For more details on issues that may be experienced, see the Github issue.

WPF/UWP 工具WPF/UWP Tooling

建置 WPF/UWP 應用程式的客戶會在 Visual Studio XAML 工具中看到下列改進:Customers building WPF/UWP applications will see the following improvements in Visual Studio XAML tooling:

DesignerDesigner

  • XAML 設計工具縮放/位置現在預設為 [調整成畫面大小]: 根據客戶的意見反應,我們重新評估了您開啟 XAML 視窗/頁面/控制項/等項目時,所發生的預設 XAML 設計工具縮放行為。之前的情況是,系統會在 Visual Studio 工作階段間儲存每個檔案的縮放比例和位置,但當客戶過段時間再回到檔案時,這會造成混淆。XAML Designer zoom/position now defaults to Fit All: Based on customer feedback we’ve reevaluated the default XAML Designer zoom behavior that occurs when you open a XAML window/page/control/etc. The previous experienced stored the zoom level and position for each file across Visual Studio sessions which caused confusion when customers were coming back to a file after some time had passed. 從這個版本開始,我們只會在使用中工作階段期間儲存縮放比例和位置,當 Visual Studio 重新啟動後,即會回到 [調整成畫面大小] 預設。Starting with this release we will only store the zoom level and position for the duration of the active session and go back to a “fit all” default once Visual Studio is restarted.
  • [建立資料繫結] 對話方塊: Visual Studio 已經有 [資料繫結] 對話方塊,WPF .NET Framework 開發人員以滑鼠右鍵按一下 XAML 設計工具和屬性總管即可予以使用,而此對話方塊先前也可供 UWP 開發人員使用。Create Data Binding Dialog: Visual Studio has had a data binding dialog available to WPF .NET Framework developers from the right-click of the XAML Designer and Property Explorer, and this dialog was also previously available to UWP developers. 在此版本中,我們會再度為 UWP 開發人員提供這項體驗,並新增 WPF .NET Core 應用程式的支援。In this release we’re bringing back this experience to UWP developers and adding support for WPF .NET Core applications. 這項功能仍在開發階段,未來將會持續改進,以恢復與 .NET Framework 對話方塊功能的功能同位。This feature is still in development and will continue to improve in the future to bring back feature parity with .NET Framework dialog capabilities.

XAML 編輯器XAML Editor

  • 改進了 #regions IntelliSense: 從 Visual Studio 2015 開始,WPF 與 UWP XAML 開發人員已可使用 #region 支援,最近也已可供 Xamarin.Forms 使用。Improvements to #regions IntelliSense: Starting with Visual Studio 2015 #region support has been available for WPF and UWP XAML developers and more recently for Xamarin.Forms. 在此版本中,我們修正了 IntelliSense Bug,經過此次修正後,#regions 現在會在您開始鍵入 <! 時正確顯示。In this release we’ve fixed an IntelliSense bug, with this fix #regions will now show properly as you begin to type <!. 我們也新增了讓 #regions 在任何項目巢狀層級都能正確運作的功能。We have also added the ability for #regions to work correctly across any element nesting levels.
  • XAML IntelliSense 中的程式碼片段: IntelliSense 已增強為支援顯示 XAML 程式碼片段,這同時適用於內建程式碼片段和您手動新增的所有自訂程式碼片段。Snippets in XAML IntelliSense: IntelliSense has been enhanced to support showing XAML snippets, this will work for both built-in snippets and any custom snippets that you add manually. 從這個版本開始,我們也會包含一些現成的 XAML 程式碼片段:#region、資料行定義、資料列定義、Setter 和標記。Starting with this release we’re also including some out-of-the-box XAML snippets: #region, Column definition, Row definition, Setter and Tag.
  • 在設計工具外以另一個視窗快顯 XAML 編輯器: 您現在可以使用 [XAML] 索引標籤旁邊的新 [快顯 XAML] 按鈕,輕鬆地將 XAML 設計工具及其基礎 XAML 編輯器分割成不同的視窗。當您按一下時,[XAML 設計工具] 會將其附加的 XAML 索引標籤最小化,而且只會快顯開啟 XAML 編輯器檢視的新視窗。Pop up XAML editor as a separate window from designer: It is now possible to easily split the XAML Designer and its underlying XAML editor into separate windows using the new Pop up XAML button next to the XAML tab. When clicked the XAML designer will minimize its attached XAML tab and pop open a new window for just the XAML editor view. 您可以將這個新視窗移至 Visual Studio 中的任何顯示或索引標籤群組。You can move this new window to any display or tab group in Visual Studio. 請注意,您仍然可以展開原始的 XAML 檢視,但相同檔案的所有 XAML 檢視無論如何都會即時保持同步。Note that it is still possible to expand the original XAML view but regardless all XAML views of the same file will stay synchronized in real-time.
Pop up XAML code window
快顯 XAML 程式碼視窗Pop up XAML code window
  • 顯示參考組件的資源: XAML IntelliSense 已更新為支援從 WPF 架構和 WPF .NET Core 專案的參考組件 (當來源無法使用時) 顯示 XAML 資源。Displaying resources for referenced assemblies: XAML IntelliSense has been updated to support displaying XAML resources from a referenced assembly (when source is not available) for WPF Framework and WPF .NET Core projects.

XAML 偵錯工具XAML Debugging Tools

  • 即時視覺化樹狀結構中的「只顯示我的 XAML」: 「即時視覺化樹狀結構」是一項功能,當 UWP 和 WPF 開發人員在偵錯模式中執行應用程式時,可同時供他們使用,而且它也屬於與 XAML 熱重新載入相關的即時編輯工具。Just My XAML in Live Visual Tree: The Live Visual Tree is a feature that is available to both UWP and WPF developers when they run their application in debug mode and is part of the live editing tooling related to XAML Hot Reload. 此功能之前會顯示已附加執行中應用程式的完整即時視覺化樹狀結構,但並沒有篩選,無法只查看您在應用程式中撰寫的 XAML。Previously the feature would display the full live visual tree of the attached running application with no filter possible to see just the XAML you’ve written in your app. 這使體驗非常紛亂,於是我們根據客戶的意見反應,新增了稱為「只顯示我的 XAML」的預設,這會限制樹狀結構只顯示您在應用程式中撰寫的控制項。This made for a very noisy experience and based on customer feedback we’ve added a new default called “Just My XAML” which will limit the tree to just controls you wrote in your application. 雖然這是新預設,但您仍然可以透過即時視覺化樹狀結構本身內含的按鈕或透過新設定 (位置如下),返回先前的行為:[選項] > [偵錯] > [一般] > 啟用只顯示我的 XAMLWhile this is the new default it is still possible to go back to the previous behavior through either the button within tine Live Visual Tree itself or through a new setting (found under: Options > Debugging > General > Enable Just My XAML)
Show Just My XAML in Live Visual Tree
在即時視覺化樹狀結構中只顯示我的 XAMLShow Just My XAML in Live Visual Tree

資源與範本Resources & Templates

  • 合併資源字典: 您現在可以使用方案總管提供的新功能,輕鬆地將 UWP/WPF 專案內的現有資源字典與任何有效的 XAML 檔案合併。Merge Resource Dictionary: It is now possible to easily merge an existing resource dictionary within your UWP/WPF project with any valid XAML file using the new feature available through the solution explorer. 只要在方案總管中開啟您要在其中新增合併陳述式的 XAML 檔案,然後找出並以滑鼠右鍵按一下您要合併的檔案,就大功告成了。Simply open the XAML file in which you want to add the merge statement, then find the file you wish to merge in and right-click on it in solution explorer. 在操作功能表中,選取 [將資源字典合併到使用中視窗內] 選項,即會新增包含路徑的正確合併 XAML。In the context menu select the option “Merge Resource Dictionary Into Active Window”, which will add the right merge XAML with path.
Merge Resource Dictionary
合併資源字典Merge Resource Dictionary
  • 「編輯範本」現在適用於協力廠商控制項程式庫中的控制項: 即使控制項範本不是您解決方案中的原始程式碼,您現在也可以建立控制項範本的複本。Edit Template now works with controls from 3rd party controls: It is now possible to create a copy of a controls template even when it’s not part of your solution as source code. 經過此次變更,現在您可使用 [編輯範本] 功能,而且運作起來形同在您目前有原始程式碼的項目中一樣。With this change the “Edit Template” feature will now be available and work as it does for 1st party elements where the source is available today. 請注意,這項功能也同時適用於協力廠商控制項程式庫和您沒有原始程式碼的控制項程式庫。Note that this feature is applicable to both 3rd party control libraries and 1st party where source isn’t available.

Release Notes Icon Visual Studio 2019 16.4 版 Preview 2Visual Studio 2019 version 16.4 Preview 2 New release icon

發行於 2019 年 10 月 15 日released October 15, 2019

Visual Studio 2019 16.4 版 Preview 2 中修正的常見問題Top Issues Fixed in Visual Studio 2019 version 16.4 Preview 2

Visual Studio 2019 16.4 版 Preview 2 的新功能摘要Summary of What's New in Visual Studio 2019 version 16.4 Preview 2

Visual Studio 2019 16.4 版 Preview 2 的新功能詳細資料Details of What's New in Visual Studio 2019 version 16.4 Preview 2

C++C++

  • Visual Studio CMake 專案現在具有 [概觀] 頁面,可協助您開始進行跨平台開發。Visual Studio CMake projects now have Overview Pages to help you get started with cross-platform development. 這些頁面是動態的,可協助您連線至 Linux 系統,並將 Linux 或 WSL 組態新增至 CMake 專案。These pages are dynamic and help you connect to a Linux system and add a Linux or WSL configuration to your CMake project.
CMake Overview Pages
CMake 概觀頁面CMake Overview Pages
  • 您現在可以透過 CMakeSettings 進一步設定要在 CMake 專案中使用的程式碼分析工具。You can now further configure which code analysis tool(s) to use in CMake projects via CMakeSettings.json. 如需詳細資訊,請參閱 C++ 小組部落格See the C++ Team Blog for more information.
Clang-Tidy warnings in the Error List
錯誤清單中的 Clang-Tidy 警告Clang-Tidy warnings in the Error List
  • CMake 專案的啟動下拉式功能表,現在會顯示您最近使用過的目標並可進行篩選。The launch drop-down menu for CMake projects now displays your most recently used targets and can be filtered.
  • C++/CLI 現在支援在 Windows 上使用 .NET Core 3.1 和更新版本的 interop。C++/CLI now supports interop with .NET Core 3.1 and higher on Windows.
  • 您現在可以針對以 Windows 上的 MSVC 所編譯專案來啟用 ASan,以進行 C++ 程式碼的執行階段檢測,其可協助偵測記憶體錯誤。You can now enable ASan for projects compiled with MSVC on Windows for runtime instrumentation of C++ code that helps with detection of memory errors.

發佈至 GitHub 支援Publish to GitHub Support

  • 屬於適用於 Visual Studio 之 GitHub 延伸模組的 [發佈至 GitHub] 功能,現在已包含在 Visual Studio 的 GitHub Essentials 中。The publish to GitHub feature that was a part of the GitHub Extension for Visual Studio is now included in Visual Studio’s GitHub Essentials.
  • 您現在可以使用 [Team Explorer 同步處理] 頁面上的 [發佈至 GitHub] 按鈕,將本機 Git 存放庫發佈至 GitHub。You can now publish local Git repositories to GitHub using the Publish to GitHub button on Team Explorer Synchronization page.

Visual Studio 中的垂直文件索引標籤Vertical Document Tabs in Visual Studio

在編輯器左側或右側的垂直清單中管理文件索引標籤。Manage your document tabs in a vertical list on either the left or right side of your editor.

Visual Studio 中的垂直文件索引標籤Vertical Document Tabs in Visual Studio

整合式終端機Integrated terminal

  • 您現在可以建立多個終端機執行個體You can now create multiple terminal instances
  • 開發人員 PowerShell 的設定檔、開發人員命令提示字元和任何可用的 WSL 發行版本會在第一次啟動時自動產生,或在使用設定檔的 [還原] 按鈕之後產生Profiles for Developer PowerShell, Developer Command Prompt and any available WSL distros are automatically generated on first launch or after using the profile's restore button
  • 終端機支援所選的 Visual Studio 色彩主題The terminal supports the selected Visual Studio color theme

自動隱藏工具視窗Autohide tool windows

啟用此預覽功能選項可讓您在開啟多個工具視窗的情況下,略過啟動 Visual Studio 所引起的啟動延遲。Enabling this preview feature option allows you to skip startup delays introduced by launching Visual Studio with multiple tool windows opened.

.NET 生產力.NET Productivity

  • 您現在可以直接透過錯誤清單來設定程式碼樣式規則的嚴重性層級。You can now configure the severity level of a code style rule directly through the error list. 將游標放在錯誤、警告或建議上。Place your cursor on the error, warning, or suggestion. 按一下滑鼠右鍵並選取 [設定嚴重性]。Right click and select Set severity. 然後選取您想要為該規則設定的嚴重性層級。Then select the severity level you would like to configure for that rule. 這會以規則的新嚴重性更新現有的 EditorConfig。This will update your existing EditorConfig with the rule’s new severity. 這也適用於協力廠商分析器。This also works for third party analyzers.
Set rule severity directly through the error list
直接透過錯誤清單設定規則嚴重性Set rule severity directly through the error list
  • [尋找所有參考] 現在可讓您依類型和成員進行分組。Find All References now allows you to group by type and member.
Group by type and member in Find All References
[尋找所有參考] 中的 [依類型和成員進行分組]Group by type and member in Find All References
  • 您現在可以將區域函式設為靜態,並將函式外部所定義變數傳遞至函式的宣告與呼叫。You can now make a local function static and pass in variables defined outside the function to the function’s declaration and calls. 將游標放在區域函式名稱上。Place your cursor on the local function name. 按下 (Ctrl+. ),以觸發 [快速動作與重構] 功能表。Press (Ctrl+.) to trigger the Quick Actions and Refactorings menu. 選取 [將區域函式設為 static]。Select Make local function static.
Make local function static
將區域函式設為靜態Make local function static
  • 您現在可以將變數明確傳遞至本機靜態函式。You can now pass a variable explicitly into a local static function. 將游標放在靜態區域函式的變數上。Place your cursor on the variable in the static local function. 按下 (Ctrl+. ),以觸發 [快速動作與重構] 功能表。Press (Ctrl+.) to trigger the Quick Actions and Refactorings menu. 選取 [在本機靜態函式中明確傳遞變數]。Select Pass variable explicitly in local static function.
Pass a variable into a local static function
將變數傳遞至本機靜態函式Pass a variable into a local static function

Release Notes Icon Visual Studio 2019 16.4 版 Preview 1Visual Studio 2019 version 16.4 Preview 1

發行於 2019 年 9 月 23 日released September 23, 2019

Visual Studio 2019 16.4 版 Preview 1 的新功能摘要Summary of What's New in Visual Studio 2019 version 16.4 Preview 1

Visual Studio 2019 16.4 版 Preview 1 中修正的主要開發人員社群問題Top Developer Community Issues Fixed in Visual Studio 2019 version 16.4 Preview 1

Visual Studio 2019 16.4 版 Preview 1 的新功能詳細資料Details of What's New in Visual Studio 2019 version 16.4 Preview 1

C++C++

  • 無論您是使用 Clang 或 MSVC 工具,程式碼分析現在都可針對 MSBuild 和 CMake 專案,以原生方式支援 clang-tidy。Code Analysis now natively supports Clang-Tidy for both MSBuild and CMake projects, whether you're using a Clang or MSVC toolset. clang-tidy 檢查可作為背景程式碼分析的一部分來執行、顯示為編輯器內的警告 (波浪線),以及顯示在錯誤清單中。clang-tidy checks can run as part of background code analysis, appear as in-editor warnings (squiggles), and display in the Error List.

.NET Web 工具.NET Web Tools

  • 管理發佈相依性或使用已連線的服務時,自動偵測 SQL Server 和 Azure 儲存體連接字串。Automatic detection of SQL Server and Azure Storage connections strings when managing publish dependencies or using Connected Services. 將會在下拉式清單中提供這些字串以供使用者從中挑選,但使用者必須在這之前重新鍵入這些字串。They are offered in a drop-list for users to pick from, whereas before they had to re-type them in.
  • 新增使用 64 位元執行階段開發 Azure Functions 的支援Added support for developing Azure Functions using the 64bit runtime
  • 新增對 .NET Core 3.0 應用程式發佈選項的支援:準備好執行 (Crossgen)、連結及 SingleExeAdded support for .NET Core 3.0 app publishing options: Ready to Run (Crossgen), Linking, and SingleExe

.NET 生產力.NET Productivity

  • 您現在可以直接透過編輯器設定程式碼樣式規則的嚴重性層級。You can now configure the severity level of a code style rule directly through the editor. 如果使用者目前沒有 .editorconfig 檔案,系統就會為其產生一個檔案。If a user does not currently have an .editorconfig file, one will be generated for them. 將您的資料指標放在錯誤、警告或建議與類型 (Ctrl+. ) 上,以開啟[快速動作與重構] 功能表。Place your cursor on the error, warning, or suggestion and type (Ctrl+.) to open the Quick Actions and Refactorings menu. 選取 [設定或隱藏問題]。Select ‘Configure or Suppress issues’. 然後選取規則,並選擇您想要為該規則設定的嚴重性層級。Then select the rule and choose the severity level you would like to configure for that rule. 這會以規則的新嚴重性更新現有的 EditorConfig。This will update your existing EditorConfig with the rule’s new severity. 這也適用於協力廠商分析器。This also works for third party analyzers.
Set rule severity directly through the editor
直接透過編輯器設定規則嚴重性Set rule severity directly through the editor
  • 您現在可以使用 [移至基底] 命令向上巡覽繼承鏈。You can now use the Go To Base command to navigate up the inheritance chain. 在您想要巡覽繼承階層的項目操作 (右鍵) 功能表上,會提供 [移至基底] 命令。Go To Base command is available on the context (right-click) menu of the element you want to navigate the inheritance hierarchy. 或者,您可以鍵入 (Alt+Home)。Or you can type (Alt+Home). 如果有一個以上的結果,則會開啟工具視窗,其中包含您可以選擇要巡覽的所有結果。If there is more than one result a tool window will open with all of the results that you can choose to navigate to.
Go To Base
移至基底Go To Base
  • 您現在可以為所有參數新增 Null 檢查。You can now add null checks for all parameters. 這會新增 if 陳述式,以檢查所有可為 Null 之非檢查參數的 Null 狀態。This will add if statements that check nullity of all the nullable, non-checked parameters. 將游標放在方法內的任何參數上。Place your cursor on any parameter within the method. 按下 (Ctrl+. ),以觸發 [快速動作與重構] 功能表。Press (Ctrl+.) to trigger the Quick Actions and Refactorings menu. 選取 [為所有參數新增 Null 檢查] 的選項。Select the option to ‘Add null checks for all parameters’.
Add null checks for all parameters
為所有參數新增 Null 檢查Add null checks for all parameters
  • 沒有 XML 文件之方法現在可以從它所覆寫的方法自動繼承 XML 文件。Methods that have no XML documentation can now automatically inherit XML documentation from the method it is overriding. 將游標放在會實作已記載介面方法的未記載方法上。Place your cursor over the undocumented method that implements a documented interface method. [快速諮詢] 會接著顯示介面方法中的 XML 文件。Quick Info will then display the XML documentation from the interface method.
XML inherit documentation
XML 繼承文件XML inherit documentation

已知問題Known Issues

遵循以下連結,查看所有已知問題和 Visual Studio 2019 中可用的因應措施。See all open issues and available workarounds in Visual Studio 2019 by following the below link.


意見反應Feedback

我們很希望聽聽您的意見!We would love to hear from you! 若有任何問題,請透過安裝程式或 Visual Studio IDE 本身右上角的回報問題選項來通知我們。For issues, let us know through 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 make a product suggestion or track your issues in the Visual Studio Developer Community, where you can ask questions, find answers, and propose new features. 您也可以透過我們的即時聊天支援取得免費的安裝協助。You can also 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.


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

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


頁首
Top of Page