Visual Studio Icon Visual Studio 2015 Update 1 版本資訊Visual Studio 2015 Update 1 Release Notes


| Developer Community | System Requirements | Compatibility | Distributable Code | License Terms | Blogs | Known Issues


注意

This is not the latest version of Visual Studio. To download the latest release, please visit the current release notes for Visual Studio 2019.


下載 Visual Studio 2015Download Visual Studio 2015

若要下載 Visual Studio 2015 Update 1,請按一下 [下載] 按鈕。To download Visual Studio 2015 Update 1, click on the download button. 這些檔案是從我們的免費 Dev Essentials 訂閱網站下載。The files are downloaded from our free Dev Essentials subscription-based site. 如需免費的開發人員計畫和服務的詳細資訊,請參閱Dev Essentials頁面。Please see the Dev Essentials page for information on our free comprehensive developer program and services.


Release Notes Icon Visual Studio 2015 Update 1Visual Studio 2015 Update 1

發行日期:2015 年 11 月 30 日Release Date: November 30, 2015

本版新功能的摘要Summary of What's New in this Release

其他變更:Other changes:


本版新功能的詳細資料Details of What's New in this Release

Apache Cordova 工具 Tools for Apache Cordova

第一次使用 Apache Cordova 工具 Visual Studio 2015 版以來的開發人員會發現更豐富的開發平臺,其中支援 iOS 9、Android 6 "Marshmallow" 的基礎、適用于 Azure AD 驗證的新外掛程式,以及數十個 .。。甚至數百個 bug 修正,以改善開發人員體驗。Developers using the Tools for Apache Cordova for the first time since the Visual Studio 2015 release will find a richer development platform with support for iOS 9, the groundwork for Android 6 “Marshmallow”, a new plug-in for Azure AD authentication and dozens...even hundreds of bug fixes to improve the developer experience.

在本文中,我們也有新的範例、教學課程和檔的目的地We also have a new destination for samples, tutorials and documentation, in this article. 而現在,檔直接源自 GitHub,讓開發人員可以使用簡單的提取要求來提供秘訣、訣竅和更正。And now, docs are sourced directly from GitHub, making it possible for developers to contribute tips, tricks, and corrections by using a simple pull request.

適用於通用 Windows app 的工具 Tools for Universal Windows Apps

您可以使用適用于通用 Windows 應用程式(v1.1)的工具,以 Windows 10 SDK 1511 版為目標來建立應用程式,並將其提交至 Windows Store。You can use Tools for Universal Windows Apps (v1.2) to build and submit apps to the Windows Store by targeting Windows 10 SDK Version 1511. 此版本也包含數項開發人員生產力改善,.NET Native、XAML 設計工具、資訊清單設計工具、Windows Store 封裝和偵錯工具。Also included in this release are several developer productivity improvements to .NET Native, the XAML designer, the manifest designer, Windows Store packaging, and the debugger.

如果您還沒有安裝適用于通用 Windows 應用程式的工具,可以修改 Visual Studio 2015 安裝來加以啟用,或直接從這個連結進行安裝。If you don't already have Tools for Universal Windows Apps installed, you can enable them by modifying the Visual Studio 2015 installation, or by directly installing them from this link

Visual C# Visual C#

[ C# 互動] 視窗會回到 Visual Studio,以及命令列c # 複寫視窗。The C# Interactive Window is back in Visual Studio, as well as the command-line C# REPL window. ([互動式] 視窗是 Visual Studio 內的 [複寫] 視窗)。(The Interactive Window is the REPL window inside Visual Studio.)

我們也發行了腳本 api ,可讓您以腳本的形式建立和執行 c #。We've also released scripting APIs that enable you to build and run C# as a script. 您可以從GitHub取得腳本 api。The scripting APIs are available on GitHub.

此外,我們已發行csi,這是一種工具,可讓您用來從開發人員命令提示字元執行 c # 腳本檔案(. .csx)。Additionally, we've released csi.exe, which is a tool that you can use to run a C# script file (.csx) from the Developer Command Prompt. 例如,只要輸入 csi Myscript.sql. .csx 即可執行您的腳本檔案。For example, simply type csi myScript.csx to run your script file. 或者,您可以輸入命令列複寫模式,以互動方式評估 c # 程式碼的程式碼片段。Or, you can enter the command-line REPL mode to interactively evaluate snippets of C# code. 若要進入此模式,請執行命令 csi,而不需要開發人員命令提示字元中的任何引數。To get to this mode, run the command csi without any arguments from the Developer Command Prompt.

偵錯工具和診斷 Debugging and Diagnostics

Visual C++ Visual C++

在此版本中,我們新增了 /BigObj編輯後繼續支援,這表示您現在可以在偵錯工具Windows Store c + + 專案時編輯並繼續編輯程式碼。In this release, we've added Edit and Continue support for /BigObj, which means that you can now Edit and Continue to edit code while debugging Windows Store C++ projects.

在 UWP 應用程式中的「偵測」會話期間的編輯器,反白顯示 [繼續] 按鈕

IDEIDE

我們一直在等待的功能都在這裡!The feature we've all been waiting for is finally here! 您現在可以在介面或抽象方法定義上按一下滑鼠右鍵,然後使用 [移至執行] 快捷方式流覽至它的執行。You can now right-click on an interface or abstract method definition and navigate to its implementation by using the Go To Implementation shortcut.

滑鼠右鍵功能表上的 [移至實作] 快捷方式影像

我們也加入了新的重整功能,可讓您使用 [快速動作] 命令Ctrl + ,將 get 方法轉換為屬性。We've also added a new refactoring that lets you convert get methods to properties by using the Quick Action command, Ctrl + .

此外,我們修正了錯誤的格式設定、不必要的轉型、WinForms 整合、搜尋方案總管中的類別,以及使用「使用索引標籤」移至 DEF/ma 的問題。Additionally, we've fixed bugs around formatting, unnecessary casting, WinForms integration, crashing when searching for a class in the Solution Explorer, and go to def/MAS with "Use Tabs." 而且,我們現在會在第一次開啟時自動折迭區域。And, we've made regions now auto-collapse upon first open.

程式碼分析Code Analysis

我們現在支援 IDE 中的下列案例,以管理來自程式碼分析的技術債務:We now support the following scenarios in the IDE for managing the technical debt that comes from code analysis:

  • 僅針對「我的程式碼變更」來查看分析警告和訊息。View analysis warnings and messages for only 'my code changes.'
  • 「基準」所有目前的問題,並持續不斷地繼續進行。'Baseline' all current issues and "stay clean" moving forward.
  • 查看及管理您的基準,以審核隱藏隱藏,或解決現有的技術債務。View and manage your baseline to audit suppressions, or to address existing technical debt.
  • 移除錯誤清單中重複的警告實例,將結果焦點放在唯一的集合中。Remove duplicate instances of warnings in the error list to focus results to the unique set.

使用隱藏專案管理分析問題

診斷工具視窗Diagnostics Tools window

我們對 [診斷工具] 視窗的 [事件] 索引標籤進行了幾項改進,協助您更快且更有效率地閱讀和瞭解其事件清單。We've made several improvements to the Events tab of the Diagnostic Tools window to help you read through and understand its list of events even faster and more efficiently than before.

以下是新增功能:Here's what's new:

  1. 改良的篩選功能表,您可以透過下列方式自訂:An improved filtering menu that you can customize in the following ways:
    依類別、依執行緒,或使用Just My CodeBy category, by thread, or by using Just My Code.
  2. 新的搜尋控制項,可讓您搜尋事件資料表的所有可見資料行。A new search control that allows you to search all visible columns of the Events table.
  3. 類別首碼 * * 我們已新增至所有事件,讓它們更容易閱讀。Category prefixes** that we've added to all events, which makes them easier to read.

注意

這些 [診斷工具] 視窗改良功能適用于所有版本的 Visual Studio。These Diagnostics Tools window improvements are available in all editions of Visual Studio. 不過,下列螢幕擷取畫面來自具有 IntelliTrace 的 Visual Studio Enterprise,並可讓您存取比其他版本更多的事件類別目錄。However, the following screenshot comes from Visual Studio Enterprise, which has IntelliTrace, and gives you access to more event categories than other editions.

[改良的診斷工具] 視窗的螢幕擷取畫面

深入瞭解 [診斷工具] 視窗Learn more about the Diagnostics Tools window.

分析您在進行偵錯工具時的 CPU 使用量Profile your CPU Usage while debugging

現在,您可以在進行偵錯工具時,取得 CPU 使用量的詳細每個函式設定檔。Now, you can get a detailed per-function profile of your CPU Usage while you are debugging. 當您處於中斷狀態時,您可以開啟和關閉 CPU 分析,而這可讓您針對在中斷點和步驟之間執行的程式碼,查看 CPU 使用量的每個功能細目。You can turn CPU Profiling on and off while debugging and view the results when you are in a break state, which allows you to view a per-function breakdown of CPU Usage of code that executed between breakpoints and during steps. (若要使用此功能,請開啟 [診斷工具] 視窗(Debug- > 診斷工具),切換到 [cpu] 索引標籤,然後按一下 [Cpu 分析] 按鈕)。(To use this functionality, open the Diagnostic Tools window (Debug -> Diagnostic Tools), switch to the CPU tab, and then click the "CPU Profiling" button.)

如需詳細資訊,請閱讀我們的「在Visual Studio 2015 中的偵錯工具中分析 CPU」的 blog 文章。For more information, read our " Profile Your CPU in the Debugger in Visual Studio 2015" blog post.

.NET Framework 4.6。1 .NET Framework 4.6.1

Visual Studio 2015 Update 1 現在包含 .NET Framework 的最新版本(4.6.1)。Visual Studio 2015 Update 1 now includes the latest version (4.6.1) of the .NET Framework. .NET Framework 4.6.1 包括 .NET 4.6 的所有功能和改進,以及許多可靠性、穩定性、安全性及效能修正。The .NET Framework 4.6.1 includes all the features and improvements of .NET 4.6 as well as numerous reliability, stability, security, and performance fixes. 以下是4.6.1 中的一些主要功能:These are some of the top features in 4.6.1:

  • Windows Presentation Foundation (WPF)的拼寫檢查改良、每個使用者自訂字典的支援,以及改進的觸控效能Windows Presentation Foundation (WPF) improvements for spell check, support for per-user custom dictionaries and improved touch performance
  • 密碼編譯:加強支援橢圓曲線數位簽章演算法(ECDSA) X509 憑證Cryptography: Enhanced support for Elliptic Curve Digital Signature Algorithm (ECDSA) X509 certificates
  • ADO.NET:已在 SQL 連線性中新增AlwaysOnAlways Encrypted的支援ADO.NET: Added support in SQL Connectivity for AlwaysOn and Always Encrypted
  • Windows Workflow Foundation:交易 api 現在支援具有非 MSDTC 協調器的分散式交易Windows Workflow Foundation: System.Transactions APIs now support distributed transactions with a non-MSDTC coordinator
  • 與 IcorProfilerInfo 介面相關的程式碼剖析改進Profiling improvements related to IcorProfilerInfo interface
  • Ngen:引進 ngen pdbNGen: Introduction of NGen PDBs
  • 已新增 HttpListener API 支援,讓伺服器應用程式能夠使用權杖系結Added support to HttpListener API to enable server applications to use token binding
  • RyuJIT、GC、WPF 和 WCF 中其他許多效能、穩定性和可靠性相關的修正。Many other performance, stability, and reliability related fixes in RyuJIT, GC, WPF, and WCF.

如需 .NET Framework 4.6.1 的詳細資訊,請參閱下列文章:For more details on the .NET Framework 4.6.1, see the following articles:

ASP.NET ASP.NET

ASP.NET 5 Beta 8ASP.NET 5 Beta 8

注意

雖然 Visual Studio 2015 Update 1 包含 ASP.NET 5 Beta 8,但我們強烈建議您嘗試新發行的 ASP.NET 5 RC1,現在已可供下載;如需詳細資訊,請參閱此頁面上的ASP.NET 5 RC1While Visual Studio 2015 Update 1 includes ASP.NET 5 Beta 8, we strongly encourage you to try the newly released ASP.NET 5 RC1 that is now available for download; for details, see ASP.NET 5 RC1 on this page.

ASP.NET 5 Beta 8 具有下列功能和更新:ASP.NET 5 Beta 8 has the following features and updates:

  • DNX監看員可讓使用命令列的開發人員體驗與 ASP.NET 5 應用程式相同的編輯和重新整理瀏覽器體驗 Visual Studio 開發人員。DNX Watcher allows developers who use the command line to experience the same edit and refresh browser experience that Visual Studio developers have been enjoying with ASP.NET 5 applications. DNX 監看員將會在您的專案中觀賞檔案,並顯示編譯錯誤(如果有的話)。DNX Watcher will watch the files in your project and show compilation errors if you have any. 一旦您的程式碼可以再次編譯,它就會啟動它,而且您可以流覽至您的應用程式。And as soon as your code can compile again, it will launch it and you can browse to your app.
  • 當地語系化Localization. 應用程式開發人員現在可以開發可由許多不同文化特性轉譯和使用的 web 應用程式。Application developers can now develop web applications that can be translated and used by many different cultures. 中介軟體能夠設定文化特性,使其可透過 CurrentCulture 存取,並提供 Api 以從資源檔讀取可根據目前文化特性選取的字串。Middleware is capable of setting a culture so that it is accessible through Thread.CurrentCulture, and APIs have been provided to read strings from resource files that can be selected based on current culture.

當地語系化程式庫的其中一個優點是,當地語系化字串的索引鍵是預設文化特性中的值。One of the great things about the localization libraries is that the keys for your localized strings are the values in the default culture. 例如,如果您是以英文撰寫應用程式,您可以將英文字串放成索引鍵名稱。So, for example, if you are writing an application in English, you can put English strings as the key names.

而不是您的程式碼,如下所示:So instead of your code being something like this:

var myMessage = resources。Resources.mymessagestringvar myMessage = resources.MyMessageString;

相反地,它可以讓您更輕鬆地將應用程式中的訊息與設定它的程式碼相互關聯:It can be this, instead, which makes it easier to correlate a message in your app to the code that sets it:

var myMessage = stringLocalizer ["感謝您使用我們的產品"];var myMessage = stringLocalizer[“Thank you for using our products”];

TypeScript TypeScript

Visual Studio 2015 Update 1 包含TypeScript 工具1.6 和1.7 版本的功能。Visual Studio 2015 Update 1 includes features from the 1.6 and 1.7 releases of the TypeScript tools. 它為 TypeScript 的型別系統帶來了顯著的增強功能,並可支援多型類型、交集類型、區欄位型別宣告、泛型型別別名,以及使用者定義的類型 guard 函數。It brings significant enhancements to TypeScript's type system and enables support for the polymorphic type, intersection types, local type declarations, generic type aliasing, and user-defined type guard functions.

它也會藉由加入 ES6 產生器和 ES6 類別運算式來完成 TypeScript 中的 ES6 支援,並提供新 ES7 功能提議的支援,例如 ES7 乘冪運算子和 ES7 Async 函數。It also completes ES6 support in TypeScript by adding ES6 Generators and ES6 Class expressions, and brings support for new ES7 feature proposals like ES7 Exponentiation operator and ES7 Async functions.

此外,現在 TypeScript 編譯器和工具原本就支援回應的 JSX。Additionally, React's JSX is now natively supported by the TypeScript compiler and tooling. 除了增強的節點模組路徑解析支援外,此版本也可讓您在使用 Node 原生模組系統(--module commonjs)時,將目標設為 ES6 功能(--target ES6)原生的節點實作為。This release also enables targeting Node v4's native implementations of ES6 features (--target ES6) while using Node native module system (--module commonjs), apart from an enhanced support for node module path resolution.

其他 Miscellaneous

平行測試執行Parallel Test Execution

Visual Studio 測試平臺引進了平行執行測試案例的支援。The Visual Studio Test Platform introduces support parallel execution of test cases.

平行測試執行會利用電腦上的可用核心,並藉由將每個可用核心上的測試執行引擎啟動為不同的進程來實現,並將其交給容器(元件、DLL 或包含要執行之測試的相關成品),而值得執行的測試。Parallel test execution leverages the available cores on the machine, and is realized by launching the test execution engine on each available core as a distinct process, and handing it a container (assembly, DLL, or relevant artifact containing the tests to execute), worth of tests to execute. 排程單位為測試容器。The unit of scheduling is the test container. 在每個容器中,會根據測試架構的語義來執行測試。Within each container, the tests will be executed as per the semantics of the test framework. 如果有許多這類容器,則當處理序執行完容器內的測試時,就會將下一個可用的容器交給處理序。If there are many such containers, then as processes finish executing the tests within a container, they are handed the next available container.

使用 .runsettings 檔案全域區段中的 MaxCpuCount 設定,即可啟用平行測試執行(如下列螢幕擷取畫面所示)。Parallel Test Execution is enabled using the MaxCpuCount setting in the global section of the .runsettings file (as shown in the following screenshot).

使用 .runsettings 檔案全域區段中的 MaxCpuCount 設定,即可啟用平行測試執行

MaxCpuCount 的值具有下列的語義:The value for MaxCpuCount has the following semantics:

  • ' n ' (其中 1 < = n < = 核心數目):將啟動最多 ' n ' 個進程。‘n’ (where 1 <= n <= number of cores) : upto ‘n’ processes will be launched.
  • 其他任何值的 ' n ':啟動的進程數目將會與電腦上的可用核心數一樣多。‘n’ of any other value : The number of processes launched will be as many as the available cores on the machine.

所有啟動點皆支援平行執行-CI、命令列(CLI)和 IDE (測試瀏覽器、CodeLens、各種 "Run" 命令等),而測試瀏覽器指標則會追蹤平行執行測試的進度。Parallel execution is supported through all launch points - CI, command line (CLI) and the IDE (Test Explorer, CodeLens, various “Run” commands, etc.), and the Test Explorer indicators track the progress of tests executing in parallel.

ASP.NET 5-MSTest 支援和 CodeCoverage 支援ASP.NET 5 - MSTest support and CodeCoverage support

Visual Studio 測試平臺為 ASP.NET 5 個應用程式引進了 MSTest 架構測試的支援。The Visual Studio Test Platform introduces support for MSTest framework-based tests for ASP.NET 5 applications.

您可以從 NuGet 資源庫取得 MSTest 架構元件。The MSTest framework components are available from the NuGet gallery.

Visual Studio 測試平臺在以 CoreCLR/CLR 為目標的 x86/x64 平臺上,引進了 ASP.NET 5 應用程式的 CodeCoverage 支援。The Visual Studio Test Platform introduces support for CodeCoverage for ASP.NET 5 applications on the x86/x64 platforms that target the CoreCLR/CLR.

組建的 Subversion 支援Subversion support for build

您現在可以從 subversion 型原始檔控制存放庫進行建立,讓小組能夠集中化 TFS 中的所有組建和工作專案管理,而不需要立即移動其原始程式碼。You can now build from subversion-based source control repositories, which can enable teams to centralize all build and work item management in TFS without having to move their source code right away.

Visual Studio 中的提取要求中樞Pull requests hub in Visual Studio

Team Explorer 現在提供新的提取要求中樞,使用者可在其中查看所建立的提取要求清單,以及其他人已指派給它們的提取要求。Team Explorer now features a new Pull Requests hub where users can see the list of pull requests that they have created, as well as the pull requests that others have assigned to them.

我們也改進了建立提取要求的體驗;現在,使用者可以在單一動作中發佈分支並建立提取要求。We've also improved the Create Pull Request experience; now, users can publish branches and create pull requests in a single action.

「需要提取要求」工作專案原則"Pull request required" work item policy

我們現在有一個分支原則,要求任何提取要求都有相關聯的工作專案。We now have a branch policy that requires associated work items for any pull request. 就像程式碼審核者和組建原則一樣,任何提交到分支的程式碼都必須透過提取要求提交。Like the code reviewer and build policies, any code that is submitted to the branch must be submitted via pull request. 建立提取要求時,將會檢查相關聯的認可是否有工作專案連結,如果至少有一個連結,則會滿足原則。When a pull request is created, the associated commits will be inspected for work item links, and if there is at least one link, the policy will be fulfilled.

此外,您現在可以將工作專案直接連結到提取要求,如果提取要求直接連結到至少一個工作專案,則會滿足原則。Also, you can now link work items to pull requests directly, and if the pull request is directly linked to at least one work item, the policy will be fulfilled. (如果沒有任何工作專案連結到提取要求或相關聯的認可,原則就會失敗)。(If no work items are linked to the pull request or the associated commits, the policy will fail.)

其他變更: Bug 修正 & 的已知問題 Other changes: Bug Fixes & Known Issues

如需此版本的技術改進、錯誤 (bug) 修正及已知問題的完整說明,請參閱下列 MSDN 文章。For a complete description of technology improvements, bug fixes, and known issues in this release, see the following MSDN article.

深入瞭解Visual Studio 2015 Update 1 的說明Learn More: Description of Visual Studio 2015 Update 1

ASP.NET 5 RC1 ASP.NET 5 RC1

ASP.NET 5 RC1 包含下列功能和更新:ASP.NET 5 RC1 includes the following features and updates:

  • 啟動程式工具箱Bootstrap Toolbox
  • Bower 套件管理員Bower Package Manager
  • JSX 編輯器JSX Editor
  • 更好的角度 JS HTML 屬性顏色標示Better Colorization of Angular JS HTML attributes
  • 改良的 Razor IntelliSense 和標記協助程式Improved Razor IntelliSense and Tag Helpers
  • 可開啟 MVC 4 專案Can open MVC 4 projects
  • NPM 套件 IntelliSense (類似 Bower 的運作方式)NPM Package IntelliSense (similar to how Bower.json works)
  • 已清除 ASP.NET 方案總管Cleaned up ASP.NET Solution Explorer

如需有關 ASP.NET RC1 的詳細資訊,請參閱「宣佈 ASP.NET 5 發行候選版本 1」的 blog 文章。For more information about ASP.NET RC1, see the " Announcing ASP.NET 5 Release Candidate 1" blog post. 若要深入瞭解 .NET Core 和 ASP.NET,請參閱「宣佈 .Net core 和 ASP.NET 5 RC」的 blog 文章。And to learn more about .NET Core and ASP.NET, see the " Announcing .NET Core and ASP.NET 5 RC" blog post.

適用于 .Net 的 Azure SDK 2。8 Azure SDK 2.8 for .NET

我們已發行適用于 Visual Studio 2013 和 Visual Studio 2015 的 Azure SDK 2.8,其中包含下列功能和更新:We've released Azure SDK 2.8 for Visual Studio 2013 and Visual Studio 2015, which includes the following features and updates:

  • Azure Resource ManagerAzure Resource Manager
  • 「傳送 Azure 診斷資料」至 Application Insights"Send Azure Diagnostics data" to Application Insights
  • Docker 的新支援New Support for Docker
  • Mobile Apps 範本的更新Updates to the Mobile Apps template
  • Microsoft Azure 儲存體總管預覽Microsoft Azure Storage Explorer Preview
  • Azure Service Fabric 工具Azure Service Fabric Tools
  • 適用于 Visual Studio 的 Azure HDInsight 工具Azure HDInsight Tools for Visual Studio
  • Azure Data Factory 工具Azure Data Factory Tools

如需此版本及其新功能與更新的詳細資訊,請參閱「宣佈 AZURE SDK 2.8 for .net」的 blog 文章。For more detailed information about this release and its new features and updates, see the " Announcing the Azure SDK 2.8 for .NET" blog post.

Visual Studio Code Beta Visual Studio Code Beta

我們有許多令人興奮的公告,可以與您分享 Visual Studio Code 的 Beta 版,包括下列功能和更新:We have a number of exciting announcements to share with you about the beta for Visual Studio Code, including the following features and updates:

  • 擴充性 [外掛程式] VS Code 中的支援Extensibility [Plug-in] Support in VS Code
  • 擴充功能 Marketplace/資源庫Extension Marketplace/Gallery
  • 延伸模組「準備好立即試用」Extensions "Ready to try now"
  • VS Code 是開放原始碼VS Code is open-sourced

如需詳細資訊和下載連結,請參閱「宣佈 Visual Studio Code Beta」的 blog 文章。For detailed information and a download link, see the " Announcing Visual Studio Code Beta" blog post.

Visual Studio GDB 偵錯工具 Visual Studio GDB Debugger

我們很高興引進新的延伸模組,可讓 Visual Studio 偵錯工具與 GDB 互動。We're pleased to introduce a new extension that enables the Visual Studio debugger to interact with GDB. 這特別適合用來進行遠端 Linux 目標的偵錯工具。This is particularly useful for debugging remote Linux targets. 例如,您可以在下列案例中使用 Visual Studio GDB 偵錯工具:For example, you can use Visual Studio GDB Debugger in the following scenarios:

  • 本機 GDB 的調試Local GDB debugging
  • Azure Linux VM 上的 GDB 偵錯工具GDB debugging on an Azure Linux VM
  • 在具有 Azure IoT 中樞的 Raspberry Pi 上進行 GDB 調試GDB debugging on a Raspberry Pi with Azure IoT Hub

注意

若要使用此延伸模組,您必須安裝 Visual Studio 2015 的社區或更新版本,以及適用于 Android 或 iOS 的 Visual C++ 工具。To use this extension, you must have both Visual Studio 2015 Community or higher installed and the Visual C++ tools for Android or iOS installed.

如需詳細資訊,請參閱「宣佈 VS GDB 偵錯工具延伸模組」的 blog 文章。For more information, see the " Announcing the VS GDB Debugger extension" blog post.

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

適用于 Visual Studio的 node.js 工具是免費的開放原始碼擴充功能,可將 Visual Studio 為強大的 node.js 開發環境,並在最新版本中包含許多增強功能,例如:A free and open-source extension that turns Visual Studio into a powerful Node.js development environment, Node.js Tools for Visual Studio includes many enhancements in the latest release, such as:

  • 支援 node.js v4. xSupport for Node.js v4.x
  • 支援 npm v3. x,協助解決潛在的 MAX_PATH 問題Support for npm v3.x, which helps work around potential MAX_PATH issues
  • 更快速且無雜亂的 IntelliSense,包括更佳的認可字元預設值,以及加入即將推出之 ES6 IntelliSense 引擎預覽版本的功能Faster and clutter-free IntelliSense, including better commit-character defaults, and the ability to opt in to a preview release of the upcoming ES6 IntelliSense engine
  • 改善調試過程中的穩定性,以及更快的專案載入時間Improved stability during debugging, and faster project load times
  • 程式碼片段支援Code snippet support

如需詳細資訊,請參閱「已發行 Visual Studio 的 Node.js 工具 1.1」的 blog 文章。For more information, see the " Node.js Tools 1.1 for Visual Studio Released" blog post.

NuGet NuGet

NuGet 3.3NuGet 3.3

NuGet 擴充功能的配套版本為3.3。The bundled version of the NuGet extension is 3.3. 如需所有更新的詳細資訊,請參閱NuGet 3.3 版本資訊。For more information about all the updates, see the NuGet 3.3 release notes.

NuGet 套件管理員NuGet Package Manager

根據使用者的意見反應,我們對 NuGet 套件管理員使用者介面進行了幾項變更,以提供下列優點:Based on user feedback, we've made several changes to the NuGet Package Manager user interface, to provide the following benefits:

  • 直接出現在套件清單中的動作按鈕,可讓您更快速地存取常用的管理功能。Action buttons that appear directly in the package list, which provides quicker access to common management functions.
  • 以一系列索引標籤分隔的使用者介面,這是您在專案中可能使用之封裝的特定篩選。A user interface separated into a series of tabs, which are specific filters of the packages that you might work with in your projects.
  • 當您在解決方案層級使用封裝時,所要使用的 [合併] 索引標籤。A Consolidate tab to use when you are working with the packages at the Solution level. 它也會顯示徽章,指出您可以在專案中更新的候選封裝數目。It will also show a badge that indicates how many packages are candidates that you can update in projects.
  • [更新] 索引標籤,可供多重選取套件使用。An Update tab to multi-select packages. 您不僅可以一次更新所有選取的封裝,也可以使用此功能來選擇所有封裝,並在專案或解決方案內執行「全部更新」動作。Not only can you update all selected packages at one time, but you can also use this feature to choose all packages and perform an "Update All" action inside of a project or the solution. (而且和 [合併] 索引標籤一樣,它也會顯示徽章,指出您可以在專案中更新的候選封裝數目。)(And, like the Consolidate tab, it too shows a badge that indicates how many packages are candidates that you can update in projects.)

已改善 NuGet 中的本機資料夾支援Improved Local Folder Support in NuGet

NuGet 工具現在支援更快速地存取特別製作的本機資料夾存放區。The NuGet tools now support significantly faster access to a specially crafted local folder store. 若要瞭解如何設定此存放庫,請參閱NuGet 3.3 版本資訊,以取得詳細指示。To learn how to configure this repository, see the NuGet 3.3 release notes for detailed instructions.


Visual Studio 2015 Releases

You can view all versions of Visual Studio 2015 release notes:


Top of Page