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



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


注意

這不是 Visual Studio 的最新版本。This is not the latest version of Visual Studio. 若要下載最新版本,請參閱 Visual Studio 2019 的最新版本資訊To download the latest release, please visit the current release notes for Visual Studio 2019.


下載 Visual Studio 2015Download Visual Studio 2015

若要下載 Visual Studio 2015,請按一下 [下載] 按鈕。To download Visual Studio 2015, click on the download button. 這些檔案是從我們的免費 Dev Essentials 訂用帳戶網站下載。The files are downloaded from our free Dev Essentials subscription-based site. 請參閱 Dev Essentials 頁面,以取得我們的免費全方位開發人員計畫和服務的相關資訊。See the Dev Essentials page for information on our free comprehensive developer program and services.

Download Visual Studio 2015


Release Notes Icon Visual Studio 2015Visual Studio 2015

發行於 2015 年 7 月 20 日Released July 20, 2015

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

其他變更:Other changes:

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

適用於跨平臺行動裝置應用程式開發的 Visual C++ Visual C++ for Cross-Platform Mobile Development

現在,您可以輕鬆地在多個應用程式平臺上共用、重複使用、建立、部署和偵測所有的平臺專用程式碼,但在 Visual Studio 的單一解決方案中。Now it is easy to share, reuse, build, deploy, and debug all but the most platform-specific code across multiple app platforms, all within a single solution in Visual Studio. 以下是您可以執行的幾項作業:Here are just a few of the things you can do:

  • 從適用于 Android Native Activity 應用程式的範本,或您可以在多個平臺和 Xamarin 原生 Android 應用程式中使用的共用程式碼程式庫建立專案。Create projects from templates for Android Native Activity apps, or for shared code libraries that you can use on multiple platforms and in Xamarin native Android applications.

  • 使用平臺特定的 IntelliSense 來流覽 Api,並產生適用于 Android 或 Windows 目標的正確程式碼。Use platform-specific IntelliSense to explore APIs and generate correct code for Android or Windows targets.

  • 針對 x86 或 ARM 原生平台設定您的組建。Configure your build for x86 or ARM native platforms.

  • 將您的程式碼部署至連接的 Android 裝置,或使用 Microsoft 具效能的 Android 模擬器進行測試。Deploy your code to attached Android devices or use Microsoft's performant Android emulator for testing.

  • 在 Visual Studio 偵錯工具中設定中斷點、監看變數、檢視堆疊及逐步執行程式碼。Set breakpoints, watch variables, view the stack and step through code in the Visual Studio debugger.

  • 使用 LogCat 檢視器查看 Android 裝置的訊息記錄檔。View the message log from an Android device by using the LogCat viewer. (Logcat 是一項診斷工具,而且很重要,可進行良好的編輯- > 組建- > debug 體驗。 ) (Logcat is a diagnostic tool and essential for a good edit->build->debug experience.)
    使用 Logcat 執行下列動作:Use Logcat to do the following:

    • 使用搜尋列搜尋特定的記錄訊息。Search for specific log messages by using search bar.
    • 使用切換 Autoscroll 可輕鬆地查看即將推出的記錄訊息。Use Toggle Autoscroll to view upcoming log messages easily.
    • 清除先前的記錄輸出訊息。Clear previous log output messages.
    • 選擇不同的記錄層級。Choose between various log levels.
  • 撰寫以 iOS 平臺為目標的 c + + 程式碼,並利用我們的先進程式碼撰寫功能,例如(但不限於)程式碼共用、跨平臺的 IntelliSense、重構和查看定義。Write C++ code targeting the iOS platform and take advantage of our advanced code authoring features, such as, but not limited to, code sharing, cross-platform IntelliSense, refactoring, and peek definition. iOS 支援仍在進行中,因此請立即留意更多相關資訊。iOS support is still work in progress, so keep an eye out for more on this soon. 您可以使用「 連接 bug」來傳送意見反應給我們。You can send us feedback by using Connect for bugs. 此外,您也可以使用 Visual Studio IDE 中的 傳送笑臉 ,將您的想法傳送給我們。Additionally, you can send us your quick thoughts by using Send-a-Smile in the Visual Studio IDE.

我們也已新增或更新下列內容:We also added or updated the following:

  • 支援 Android API 層級 21 (棒) 。Support for Android API Level 21 (Lollipop).
  • 以 Android 的檔案支援為基礎的新範本,可讓您使用外部組建系統 (包括 NDK 組建) 。A new template that is based on make file support for Android, that allows using an external build system (including NDK- BUILD).
  • 所有範本中的先行編譯標頭檔 (包括動態共用程式庫、靜態程式庫,以及跨平臺行動範本) 。Precompiled headers in all templates (including Dynamic Shared Library, Static Library, and Cross-platform mobile templates).

Apache Cordova 的 Visual Studio Tools Visual Studio Tools for Apache Cordova

Apache Cordova 的 Visual Studio Tools 之前稱為 Visual Studio 的多重裝置混合式應用程式,可讓您輕鬆地建立、偵測及測試以 Android、iOS、Windows 和 Windows Phone 為目標的跨平臺應用程式,只需要一個簡單的 Visual Studio 專案。Formerly known as Multi-Device Hybrid Apps for Visual Studio, the Visual Studio Tools for Apache Cordova make it easy to build, debug, and test cross-platform apps that target Android, iOS, Windows, and Windows Phone from one simple Visual Studio project.

先前 Ctp 中可用的所有功能現在都可在 Visual Studio 2015 RC 中使用,包括下列改良功能:All of the features available in previous CTPs are now available in the Visual Studio 2015 RC, including the following improvements:

  • 針對 Ripple 進行儲存時更新-不需要重建!Update on save for Ripple – no need to rebuild!
  • 當您的應用程式部署至 iOS 模擬器或 Mac 上的連接裝置時,從 Visual Studio 中進行應用程式的 iOS 版本的偵錯工具Debug an iOS version of your app from Visual Studio when it is deployed to the iOS Simulator or a connected device on a Mac
  • 改進包含的遠端 iOS 組建代理程式安全性和簡化的設定Improved security and simplified configuration for the included remote iOS build agent
  • 改良的外掛程式管理體驗,包括從 Git 或檔案系統將自訂外掛程式新增至您的專案的支援An improved plugin management experience that includes support for adding custom plugins to your project from Git or the filesystem
  • 從改良的 config.xml 設計工具中選取平臺特定的設定選項Select platform-specific configuration options from an improved config.xml designer
  • 支援 Apache Cordova 4.0.0。Support for Apache Cordova 4.0.0.

我們聽取您的意見反應,並放寬了您可以進行調試的裝置數量,如下所示:We listened to your feedback and broadened the number of devices you can debug to, as follows:

  • Android 4.4、Android 4.3 及更早版本(含 jsHybugger)Android 4.4, Android 4.3 and earlier with jsHybugger
  • iOS 6、7 和 8iOS 6, 7, and 8
  • Windows 市集 8.1Windows Store 8.1

然後,我們會進一步放寬了調試支援。Then, we broadened our debugging support further. 您現在可以將目標設為 Windows Phone 8.1 的 Apache Cordova 應用程式進行偵錯工具。You can now debug your Apache Cordova apps that target Windows Phone 8.1.

您可以在 Windows Phone 8.1 模擬器或連接的裝置上設定中斷點、檢查變數、使用主控台,以及執行其他的偵錯工具。You can set breakpoints, inspect variables, use the console, and perform other debugging tasks on your Windows Phone 8.1 emulator or attached device.

使用 Visual Studio Tools 進行 Apache Cordova 的偵錯工具

我們新增了 RC 版本的 CLI 互通性We added CLI interoperability for the RC release. Visual Studio 中的 Cordova 專案現在會與您在磁片上的專案資料夾所做的變更進行同步處理。Cordova projects in Visual Studio will now synchronize with changes made to your project folder on-disk. 無論您使用的是協力廠商工具或其他作業系統,變更都會流入或流出 Visual Studio。Changes can flow in and out of Visual Studio whether you are working with third-party tools or on other operating systems. (Cordova 專案的預設檔案結構是以 Apache Cordova 命令列工具所需的結構為基礎,這可讓您更輕鬆地直接使用 Apache Cordova CLI 或其他預期該資料夾結構的工具。 ) (The default file structure for Cordova projects is based on the structure expected by the Apache Cordova command-line tools, which makes it easier to work directly with the Apache Cordova CLI or other tools that expect that folder structure.)

適用于 Android 的 Visual Studio 模擬器 Visual Studio Emulator for Android

您可以在 Visual Studio (Xamarin 或 c + +) 的跨平臺專案中,或 Visual Studio Tools Apache Cordova 中使用適用于 Android 的 Visual Studio 模擬器。You can use the Visual Studio Emulator for Android either in a cross-platform project in Visual Studio (Xamarin or C++), or in Visual Studio Tools for Apache Cordova. 模擬器可讓您在不同的平臺模擬器之間切換,而不會發生 Hyper-v 衝突。The emulator allows you to switch between different platform emulators without Hyper-V conflicts. 它支援各種不同的感應器和模擬,包括 GPS/位置、加速計、螢幕旋轉、縮放、SD 卡、相機、多點觸控及網路存取。It supports a wide variety of sensors and simulations, including GPS/Location, accelerometer, screen rotation, zoom, SD card, camera, multi-touch, and network access. 它也支援 Android 版本 4.4 (KitKat、API 層級 19) 和 5.0 (棒裡的 API 層級 21) 。It also supports Android versions 4.4 (KitKat, API Level 19) and 5.0 (Lollipop, API Level 21).

適用于 Android 的 Visual Studio 模擬器支援 WiFi 模擬,以及從數個不同的裝置硬體設定中選擇的能力。The Visual Studio Emulator for Android supports both WiFi simulation and the ability to choose from several different device hardware configurations.

我們為 RTM 新增了下列新功能:We added the following new features for RTM:

  • 新平臺New platforms. 提供 jellybean (API 17) 和 5.1 (API 22) 映射可供使用。Jellybean (API 17) and Lollipop 5.1 (API 22) images are available.
  • 命令列介面Command-line interface. 在命令提示字元中流覽至% programfiles (x86) % \ Microsoft Emulator Manager\1.0\emulatorcmd.exe 將可讓您與模擬器管理員 (清單、安裝、啟動設定檔等 ) 互動,而不需要 UI。Navigating to %programfiles(x86)%\Microsoft Emulator Manager\1.0\emulatorcmd.exe in a command prompt will allow you to interact with the emulator manager (list, install, start profiles, etc.) without a UI.
  • 拖放 zip 程式庫Drag-and-drop zip libraries. 在模擬器上拖放可刷新 zip,現在會自動將它解壓縮並進行安裝。Dragging and dropping a flashable zip onto the emulator will now automatically unpack and install it.
  • SD 卡 索引標籤。[其他工具] 視窗中的這個新索引標籤可讓您在 SD 記憶卡上推送和提取資料。SD Card tab. This new tab in the "Additional Tools" window allows you to push and pull data to and from the SD Card.
  • 自行取得Acquire on its own. 模擬器可以安裝在電腦上,而不需要安裝 Visual Studio。The emulator can be installed on a machine without requiring you to install Visual Studio. 模擬器管理員的快捷方式會出現在 [開始] 功能表中,讓您可以從任何開發工具鏈啟動和使用它。A shortcut to the Emulator Manager appears in the Start menu so that you can start it and use it from any development tool chain.

如需詳細資訊,請參閱 適用于 Android 的 Visual Studio 模擬器For more information, see Visual Studio Emulator for Android.

適用于通用 Windows 應用程式開發的 Visual Studio Tools Visual Studio Tools for Universal Windows App Development

適用于通用 Windows 應用程式開發的 Visual Studio 工具已與 Visual Studio 安裝程式整合。The Visual Studio tools for Universal Windows app development is integrated with Visual Studio setup. 這些工具可讓您建立在所有 Windows 10 裝置上執行的 Windows 應用程式– pocket 中的手機、包中的平板電腦或膝上型電腦、電腦上的電腦、IoT 裝置、不久、您房屋中的 Xbox 主控台、Surface Hub 等等。These tools enable you to build Windows apps that run across all Windows 10 devices – the phone in your pocket, the tablet or laptop in your bag, the PC on your desk, the IoT devices and soon, the Xbox consoles in your house, the Surface Hub, and more. 此外,您也可以使用這些工具來建立可利用 Windows 10 Api 的 Windows 桌面應用程式。In addition, you can also use these tools to build Windows Desktop Applications that leverage Windows 10 APIs. 如需詳細資訊,請參閱 通用 Windows 應用程式 Visual Studio Tools 的新功能For more information, see What's New in Visual Studio Tools for Universal Windows Apps.

如需 Windows 應用程式開發的詳細資訊,請參閱 通用 windows 應用程式Windows 開發人員中心指南。For more information on Windows app development, see the Guide to Universal Windows apps and the Windows Developer Center. 如需最新 Windows 組建和 Sdk 的詳細資訊,請參閱 Windows 測試人員 入口網站。For information on the latest Windows builds and SDKs, see the Windows Insider portal.

Visual C++ Visual C++

在此版本中,c + + 編譯器和標準程式庫已更新,並增強對 c + + 11 的支援,以及特定 c + + 14 功能的初始支援。In this release, the C++ compiler and standard library have been updated with enhanced support for C++11 and initial support for certain C++14 features. 其中也包括 C++17 標準預期會有的特定功能之初步支援。They also include preliminary support for certain features expected to be in the C++17 standard.

此外,已修正500以上的編譯器 bug,其中許多都是由客戶透過 Microsoft 開發人員的社區 所提交-感謝您!Additionally, more than 500 compiler bugs have been fixed, including many submitted by customers through Microsoft Developer Community ­— thank you!

語言功能Language Features

我們新增了下列新功能,讓編譯器更接近 standard c + +:We added the following new features to bring the compiler closer to standard C++:

  • 可繼續的函式 (resume/await) Resume 和 await 關鍵字提供非同步程式設計的語言層級支援,並啟用可繼續的功能。Resumable Functions (resume/await) The resume and await keywords provide language-level support for asynchronous programming and enables resumable functions. 目前,這項功能只適用於 x64 的目標。Currently, this feature is only available for x64 targets. 針對 c + + 17 建議 [>n3858]Proposed for C++17 [N3858]
  • 泛型 (多型) Lambda 運算式 現在可以使用 auto 指定 Lambda 函式參數類型;編譯器會在此內容中解讀 auto,表示關閉的函式呼叫運算子是成員函式樣板,而且 lambda 運算式中的每個 auto 使用都會對應到不同的樣板型別參數。Generic (Polymorphic) Lambda Expressions Lambda function parameter types can now be specified using auto; the compiler interprets auto in this context to mean that the closure's function call operator is a member function template and that each use of auto in the lambda expression corresponds to a distinct template type parameter. C + + 14C++14
  • 一般化的 Lambda 捕獲運算式 也稱為 init-capture。Generalized Lambda Capture Expressions Also known as init-capture. 現在可以將任意一個運算式的結果指派給 Lambda 擷取子句中的變數。The result of an arbitrary expression can now be assigned to a variable in the capture clause of a lambda. 這可用傳值方式擷取 move-only 類型,並讓 Lambda 運算式定義其 Closure 物件中的任意資料成員。This enables move-only types to be captured by value and enables a lambda expression to define arbitrary data members in its closure object. C + + 14C++14
  • 現在支援 二進位常 值。Binary Literals are now supported. 這類常值前面會加上 0B 或 0b,而且只能由數字 0 和 1 組成。Such literals are prefixed with 0B or 0b and consist of only the digits 0 and 1. C + + 14C++14
  • 傳回 型別推斷 現在可以推算一般函數的傳回類型,包括具有多個傳回語句和遞迴函數的函式。Return Type Deduction The return type of normal functions can now be deduced, including functions with multiple return statements and recursive functions. 這類函式定義的開頭會是 auto 關鍵字,如同在具有尾端傳回型別的函式定義中,但會省略尾端傳回型別。Such function definitions are preceded by the auto keyword as in function definitions with a trailing return type, however the trailing return type is omitted. C + + 14C++14
  • decltype ( 使用 auto 關鍵字來初始化運算式時,會從運算式中移除 ref 限定詞和最上層 cv 限定詞,以自動) 型別推斷。decltype(auto) Type deduction using the auto keyword for initializing expressions strips ref-qualifiers and top-level cv-qualifiers from the expression. decltype(auto) 保留 ref 和 cv 限定詞,除了要引進有推斷的或尾端傳回類型的函式以外,可立即在能用 auto 的任何地方使用。decltype(auto) preserves ref- and cv-qualifiers and can now be used anywhere that auto can be used, except to introduce a function with an inferred or trailing return type. C + + 14C++14
  • 移動特殊成員函式的隱含產生 當條件允許時,現在會隱含地產生移動函式和移動指派運算子,使得編譯器完全符合 c + + 11 右值參考。Implicit Generation of Move Special Member Functions Move constructors and move assignment operators are now implicitly generated when conditions allow, thus bringing the compiler into full conformance with C++11 rvalue references. C++11C++11
  • 繼承函數 衍生類別現在可指定它將繼承其基類 base 的函式,方法是使用 Base:: Base 來加入語句。在其定義中。Inheriting Constructors A derived class can now specify that it will inherit the constructors of its base class, Base, by including the statement using Base::Base; in its definition. 衍生的類別只可以繼承其基底類別的所有建構函式,而沒有辦法繼承只有特定基底的建構函式。A deriving class can only inherit all the constructors of its base class, there is no way to inherit only specific base constructors. 如果衍生的類別具有相同簽章的建構函式,會無法從多個基底類別繼承;衍生的類別也無法定義具有任何它所繼承的建構函式相同簽章的建構函式。A deriving class cannot inherit from multiple base classes if they have constructors that have an identical signature, nor can the deriving class define a constructor that has an identical signature to any of its inherited constructors. C++11C++11
  • 對齊查詢和控制項 您可以使用 alignof ( # A1 運算子來查詢變數的對齊,並使用 alignas ( # A3 規範來控制變數的對齊。Alignment Query and Control The alignment of a variable can be queried by using the alignof() operator and controlled by using the alignas() specifier. alignof ( # A1 會傳回必須配置之類型實例的位元組界限;對於參考,它會傳回所參考類型的對齊,而針對陣列,則會傳回專案類型的對齊方式。alignof() returns the byte boundary on instances of the type that must be allocated; for references it returns the alignment of the referenced type, and for arrays it returns the alignment of the element type. alignas ( # A1 控制變數的對齊;它採用常數或型別,其中的類型是 alignas (alignof (類型) # A5 的速記。alignas() controls the alignment of a variable; it takes a constant or a type, where a type is shorthand for alignas (alignof(type)). C++11C++11
  • 擴充 sizeof 類別或結構成員變數的大小現在可以使用 sizeof ( # A1 來判斷,而不需要類別或結構的實例。Extended sizeof The size of a class or struct member variable can now be determined without an instance of the class or struct by using sizeof(). C++11C++11
  • constexpr C + + 11 constexpr 的部分支援。constexpr Partial support for C++11 constexpr. C + + 11 (部分) C++11 (partial)
  • 使用者定義常值 (udl) 現在可將有意義的後置字元附加至數值和字串常值,以提供特定的語法。User-Defined Literals (UDLs) Meaningful suffixes can now be appended to numeric and string literals to give them specific semantics. 編譯器會將尾碼常值解譯為適當的 UDL 運算子呼叫。The compiler interprets suffixed literals as calls to the appropriate UDL-operator. C++11C++11
  • 安全線程 "魔術" 靜態 靜態區域變數現在會以安全線程方式進行初始化,而不需要手動同步處理。Thread-Safe "Magic" Statics Static local variables are now initialized in a thread-safe way, eliminating the need for manual synchronization. 只有初始化是安全執行緒,以多個執行緒使用靜態區域變數仍必須以手動方式同步處理。Only initialization is thread-safe, use of static local variables by multiple threads must still be manually synchronized. 若要避免採用 CRT 相依性,使用 /Zc:threadSafeInit- 旗標可停用安全執行緒的靜態變數功能。The thread-safe statics feature can be disabled by using the /Zc:threadSafeInit- flag to avoid taking a dependency on the CRT. C++11C++11
  • 執行緒區域儲存區 使用 thread_local 關鍵字來宣告應該為每個執行緒建立獨立的物件。Thread-Local Storage Use the thread_local keyword to declare that an independent object should be created for each thread. C++11C++11
  • Noexcept 運算子現在可以用來檢查運算式是否可能擲回例外狀況。The noexcept operator can now be used to check whether an expression might throw an exception. 現在可用 noexcept 規範指定讓函式不擲回例外狀況。The noexcept specifier can now be used to specify that a function does not throw exceptions. C++11C++11
  • 內嵌命名空間 現在可將命名空間指定為內嵌,以將其內容提升至封入命名空間。Inline Namespaces A namespace can now be specified as inline to hoist its contents into the enclosing namespace. 根據預設,內嵌命名空間可用來建立會公開其最新版本的版本化程式庫,同時仍讓舊版應用程式開發介面的版本明確。Inline namespaces can be used to create versioned libraries that expose their most-recent version by default, while still making previous API versions available explicitly. C++11C++11
  • 受限制 的等位等位類型現在可包含具有非一般的函式的類型。Unrestricted Unions A union type can now contain types with non-trivial constructors. 這類等位的建構函式必須加以定義。Constructors for such unions must be defined. C++11C++11
  • 新的字元類型和 Unicode 常 值現在支援 UTF-8、UTF-16 和 UTF-32 的字元和字串常值,並已引進新的字元類型 char16_t 和 char32_t。New Character Types and Unicode Literals Character and string literals in UTF-8, UTF-16, and UTF-32 are now supported and new character types char16_t and char32_t have been introduced. 字元常值前面可加上如 U'a' 中的 u8 (UTF-8),u (UTF-16) 或 U (UTF-32),而字串常值前面可另外加上原始字串對等項目 u8R (UTF-8 原始字串),uR (UTF-16 原始字串) 或 UR (UTF-32 原始字串)。Character literals can be prefixed with u8 (UTF-8), u (UTF-16), or U (UTF-32) as in U'a', while string literals can additionally be prefixed with raw-string equivalents u8R (UTF-8 raw-string), uR (UTF-16 raw-string), or UR (UTF-32 raw-string). 通用字元名稱可自由使用於 Unicode 常值中,例如 u ' \u00EF '、u8 "\u00EF 是 i",以及您「\U000000ef is 是 I」。Universal character names can be freely used in Unicode literals as in u'\u00EF', u8"\u00EF is i", and u"\U000000ef is I". C++11C++11
  • func 預先定義的識別碼 func 會隱含定義為字串,其中包含封入函式的不合格和未名稱。func The predefined identifier func is implicitly defined as a string that contains the unqualified and unadorned name of the enclosing function. C++11C++11
  • __restrict __restrict 現在可以套用至參考。__restrict __restrict can now be applied to references.
  • Typename 關鍵字Typename keyword. 使用者現在可以在範本範本參數中寫入 typename 而不是類別。Users can now write typename instead of class in a template template parameter. C + + 14C++14
  • 全域 void 運算子 delete (void *、std:: size_t) noexceptvoid 運算子 delete [](void *, std::size_t) noexcept 現在可以多載。The globals void operator delete(void *, std::size_t) noexcept and void operator delete[](void *, std::size_t) noexcept can now be overloaded. C + + 14C++14
  • 數位分隔符號 現在,您可以使用單引號來散置數值常值,使其更容易閱讀。Digit separators Now, you can intersperse numerical literals with single quotes to make them more readable. 例如,int x = 1 ' 000 ' 000;。For example, int x = 1'000'000;. C + + 14C++14
  • 常值中的通用字元名稱 您現在可以撰寫基底字元(例如 ' A ' 和換行字元)作為常值中的程式碼點。Universal character names in literals You can now write basic characters, like 'A' and the line feed character, as code points in literals. 例如,const char * s = "\u0041\u000A";。For example, const char *s = "\u0041\u000A";. C++11C++11
  • 非靜態資料成員初始化運算式 現在可正確搭配初始化運算式清單使用。Non-static data member initializers now work correctly with initializer lists. C++11C++11
  • 屬性 您現在可以將函式指定為 [[noreturn]],以通知編譯器該函式不會傳回 (但它可能會擲回例外狀況) 。Attributes You can now specify a function as [[noreturn]] to tell the compiler that the function does not return (although it can throw an exception). 您現在也可以將各種不同的結構指定為 [[取代]]。Various constructs can now also be specified as [[deprecated]]. 屬性現在可用於命名空間和枚舉器。Attributes are now allowed on namespaces and enumerators. C + + 11、c + + 14 和 c + + 17C++11, C++14, and C++17
  • 使用者定義常值 (udl) 數值和字串常值現在可以有有意義的尾碼,可對常值資料執行自訂計算。User-Defined Literals (UDLs) Numeric and string literals can now have meaningful suffixes that perform customized computations on the literal data. C++11C++11
  • 資料相依性排序****屬性 您現在可以將函式參數、lambda 參數或函式宣告指定為 [[carries_dependency]],以改善經常讀取但不常修改的並行資料結構的優化。Data-dependency ordering attributes You can now specify function parameters, lambda parameters or function declarations as [[carries_dependency]] to improve optimizations for concurrent data structures that are frequently read but seldom modified. C++11C++11
  • 自動搭配括弧的新規則-init 清單 複製清單初始化的自動推算現在會推算 std:: initializer_list,否則會是不正確的格式。New rules for auto with braced-init-lists Auto deduction for copy-list-initializations will now either deduce a std::initializer_list or be ill-formed otherwise. C++17C++17

Visual C++ 程式庫功能Visual C++ Library Features

  • 標準程式庫類型的使用者定義常值 (udl)<Chrono > 、 < string > 和 < complex > 標頭現在會提供 UDL 運算子,方便您參考。User-Defined Literals (UDLs) for Standard Library Types The <chrono>, <string>, and <complex> headers now provide UDL-operators for your convenience. 例如,123ms 表示 std::chrono::milliseconds(123)、"hello"s 表示 std::string("hello") 和 3.14i 表示 std::complex(0.0, 3.14)。For example, 123ms means std::chrono::milliseconds(123), "hello"s means std::string("hello"), and 3.14i means std::complex(0.0, 3.14).
  • Null 正向反覆運算 器標準程式庫現在允許建立不參考容器實例的正向反覆運算器。Null Forward Iterators The standard library now allows the creation of forward iterators that do not refer to a container instance. 已將這類迭代器初始化為值,並比較是否與特定容器類型相等。Such iterators are value-initialized and compare equal for a particular container type. 將已初始化為值的迭代器和未初始化為值的另一個相比較尚未定義。Comparing a value-initialized iterator to one that is not value-initialized is undefined. C + + 14C++14
  • 引號 ( # B1 標準程式庫現在支援引號的 ( # A3 函式,讓您更輕鬆地使用加上引號的字串值和 i/o。quoted() The standard library now supports the quoted() function to make working with quoted string values and I/O easier. 在使用 quoted() 的情況下,會把整個加引號的字串視為單一實體 (如同非空格字元的字串是 I/O 資料流);此外透過 I/O 作業,逸出序列會保留下來。With quoted(), an entire quoted string is treated as a single entity (as strings of non-whitespace characters are in I/O streams); in addition, escape sequences are preserved through I/O operations. C + + 14C++14
  • 異類關聯查閱 標準程式庫現在支援關聯容器的異類查閱函數。Heterogeneous Associative Lookup The standard library now supports heterogeneous lookup functions for associative containers. 只要類型與 key_type 相當,這類函式可讓 key_type 以外的類型查閱。Such functions enable lookup by types other than the key_type as long as the type is comparable to key_type. C + + 14C++14
  • 編譯時期整數序列 標準程式庫現在支援代表可在編譯時期評估之整數值序列的 integer_sequence 類型,可讓您更輕鬆地使用參數封裝,以及簡化特定範本程式設計模式。Compile-Time Integer Sequences The standard library now supports the integer_sequence type that represents a sequence of integer values that can be evaluated at compile time to make working with parameter packs easier and to simplify certain template programming patterns. C + + 14C++14
  • exchange ( # B1 標準程式庫現在支援 std:: exchange ( # A3 公用程式函式,以指派新值給物件,並傳回其舊值。exchange() The standard library now supports the std::exchange() utility function to assign a new value to an object and returns its old value. 針對複雜類型,exchange ( # A1 可避免在移動的函式可供使用時複製舊值、避免複製新值(如果它是暫存或移動的),並接受任何類型做為新值(利用任何轉換指派運算子)。For complex types, exchange() avoids copying the old value when a move constructor is available, avoids copying the new value if it is a temporary or is moved, and accepts any type as the new value taking advantage of any converting assignment operator. C + + 14C++14
  • 雙範圍等於 ( # A1、is_permutation ( # A3、 ( # B5 不相符 標準程式庫現在支援接受兩個範圍的 std::等於 ( # A7、std:: is_permutation ( # A9 和 std::不符 ( # A11 的多載。Dual-Range equal(), is_permutation(), mismatch() The standard library now supports overloads for std::equal(), std::is_permutation(), and std::mismatch() that accept two ranges. 這些多載會處理不同長度的序列。These overloads handle sequences of different lengths. C + + 14C++14
  • 取得 <T > ( # B1 :標準程式庫現在支援 get < T > ( # A3 範本函式,允許以其類型定址元組元素。get<T>() The standard library now supports the get<T>() template function to allow tuple elements to be addressed by their type. 如果元組包含兩個或多個相同類型的元素,則 get < T > ( # A1:該元組無法由該類型定址; 不過,仍可處理其他唯一類型的專案。If a tuple contains two or more elements of the same type get<T>() the tuple cannot be addressed by that type; however, other uniquely-typed elements can still be addressed. C + + 14C++14
  • tuple_element_t 標準程式庫現在支援 tuple_element_t < I,t > 類型別名,這是 typename tuple_element < I,t > :: type 的別名。tuple_element_t The standard library now supports the tuple_element_t<I, T> type alias which is an alias for typename tuple_element<I, T>::type. 這為範本程式設計人員提供一些便利,類似于 type_traits 中的其他中繼函式類型別名 < > 。This provides some convenience for template programmers, similar to the other metafunction type aliases in <type_traits>. C + + 14C++14
  • 檔案系統 "V3" 技術規格 已將內含的檔案系統技術規格執行更新為最終版本。File System "V3" Technical Specification The included implementation of the File System Technical Specification has been updated to the final version.
  • 基本配置器 標準程式庫現在支援最基本的配置器介面;值得注意的修正包括 std:: function、shared_ptr、allocate_shared ( # A1 和 basic_string。Minimal Allocators The standard library now supports the minimal allocator interface throughout; notable fixes include std::function, shared_ptr, allocate_shared(), and basic_string. C++11C++11
  • < chrono > chrono 類型 high_resolution_clock 並修正 steady_clock。<chrono> The chrono types high_resolution_clock and steady_clock have been fixed. C++11C++11
  • constexpr 已在整個 c + + 標準程式庫中執行。constexpr has been implemented throughout the C++ Standard Library. C + + 11、c + + 14 和 c + + 17C++11, C++14, and C++17
  • quick_exit ( # B1 您現在可以藉由呼叫 quick_exit ( # A3 並在 at_quick_exit ( # A5 中執行清除程式碼,來更明確地終止多執行緒處理常式。quick_exit() You can now terminate multithreaded processes more cleanly by calling quick_exit() and run clean-up code in at_quick_exit(). C++11C++11
  • void_t 支援先進的範本元()。void_t supports advanced template metaprogramming. C++17C++17
  • 如果已知為安全,現在允許轉換成 unique_ptr < T [] >Conversions to unique_ptr<T[]> are now allowed if they are known to be safe. C++17C++17
  • invoke ( # B1 可允許函式物件、成員函式的指標,以及要使用統一語法呼叫的資料成員指標。invoke() allows function objects, pointers to member functions, and pointers to data members to be called with uniform syntax. C++17C++17
  • noexcept 標準程式庫已清除在特定函式上使用 noexcept 的功能。noexcept The standard library has cleaned up its use of noexcept on certain functions. C++17C++17
  • uncaught_exceptions ( # B1 報告飛行 (中可能超過 1) 的例外狀況數目。uncaught_exceptions() reports the number of exceptions in flight (which may be more than 1). C++17C++17
  • reference_wrapper 現在完整可複製。reference_wrapper is now trivially copyable. C++17C++17
  • map/unordered_map 現在支援 insert_or_assign ( # B1/try_emplace ( # A3。map/unordered_map now supports insert_or_assign()/try_emplace(). C++17C++17
  • 現在提供了 ( # B1空白 ( # B3資料 ( # B5 非成員函式的大小。size(), empty(), and data() non-member functions are now provided. C++17C++17
  • auto_ptrRandom_shuffle ( # B1舊的 < 功能 > 機制在 c + + 11/14 中已被取代,並已在 c + + 17 中移除。auto_ptr, random_shuffle(), and old <functional> machinery were deprecated in C++11/14 and removed in C++17. Visual Studio 2015 預設會提供它們,但將 _HAS_AUTO_PTR_ETC 定義為0個專案會移除其定義。Visual Studio 2015 provides them by default, but defining _HAS_AUTO_PTR_ETC to 0 project-wide removes their definitions.
  • unique_ptr 指派現在會受到精確的限制。unique_ptr assignments are now precisely constrained. C++17C++17
  • bool_constant 現在支援作為 integral_constant bool 的別名 < > 。bool_constant is now supported as an alias for integral_constant<bool>. C++17C++17

Visual C++ 更快速的組建Visual C++ Faster Builds

  • 漸進式連結時產生程式碼 (LTCG) 現在您可以告訴 LTCG 只重建專案中受到編輯影響的部分。Incremental Link-Time Code Generation (LTCG) Now you can tell LTCG to rebuild only the parts of your project that are affected by an edit. 這可能會大幅縮短使用 LTCG 的應用程式連結時間。This can significantly decrease link times of applications that use LTCG. 使用/LTCG:增量連結器參數來啟用這項功能。Activate this feature by using the /LTCG:incremental linker switch.
  • 靜態程式庫的累加連結 其他程式碼模組所參考之靜態程式庫的變更現在會以累加方式連結。Incremental Linking for Static Libraries Changes to static libraries that are referenced by other code modules now link incrementally.
  • /Debug:FastLink 藉由使用新的 PDB 建立技巧大幅減少連結時間。/Debug:FastLink substantially decreases link times by using new PDB creation techniques.
  • 連結器的演算法已改良,以減少連結時間。Algorithmic improvements have been made to the linker to decrease link times.
  • 已有更快建置範本大量程式碼的改良。Improvements have been made that will allow building template heavy code faster.
  • 快速特性指引優化 (PGO) 檢測 PGO 中已引進遊戲和即時系統的新的輕量檢測模式。Fast Profile Guided Optimization (PGO) Instrumentation A new, lightweight instrumentation mode for games and real-time systems has been introduced in PGO. 搭配其他在 /GENPROFILE 和 /FASTGETPROFILE 連結器參數中的新功能,當您使用 PGO 時,現在您可以在程式碼品質和建置速度之間取得平衡。Together with other new features made available through the /GENPROFILE and /FASTGETPROFILE linker switches you can now balance code quality and build speed when using PGO.
  • 減少物件檔案大小 編譯器和 c + + 標準程式庫的增強功能會大幅縮小物件檔案和靜態程式庫。Object file size reduction Compiler and C++ standard library enhancements result in significantly smaller object files and static libraries. 這些增強功能不會影響動態連結程式庫 (DLL) 或可執行檔 (EXE) 的大小,因為在過去已由連結器移除多餘的程式碼。These enhancements do not affect the size of dynamically-linked libraries (DLLs) or executables (EXEs) because the redundant code has historically been removed by the linker.

Visual C++ 效能和程式碼品質Visual C++ Performance and Code Quality

  • 自動向量化的增強功能Improvements to automatic vectorization. 我們改進了控制流程的向量化, (如果) ,請在/O1 下編譯時進行向量化, () 最小化,以及改善向量程式碼品質,包括支援 Parallel STL、向量化更多範圍架構的 for 迴圈,以及支援 #pragma 迴圈 (ivdep) 。We've improved vectorization of control flow (if-then-else), vectorization when compiling under /O1 (Minimize size), and improved the vector code quality overall, including support for the Parallel STL, vectorizing more range-based for loops, and support for #pragma loop(ivdep).
  • 純量 優化的增強功能Improvements to scalar optimization. 我們新增了較佳的測試程式碼產生、控制流程合併和優化 (迴圈-如果切換) 和其他純量優化 (例如,std:: min 和 std:: max) 有更好的程式碼產生。We've added better code generation of bit-test operations, control flow merging and optimizations (loop-if switching), and other scalar optimizations (for example, better code generation for std::min and std::max).
  • 特性 指引優化 (PGO)Profile Guided Optimization (PGO). 我們對 PGO 進行了許多增強,包括改良的參考集、更佳的資料配置功能,以及重複使用先前建立的內嵌、速度與大小,以及配置決策的能力。We made a number of enhancements to PGO, including improved reference sets, better data layout capabilities, and the ability to reuse previously made inlining, speed vs. size, and layout decisions.
  • 控制流程防護 (CFG)Control Flow Guard (CFG). 我們新增了一項新的安全性功能;只要將新選項新增至您的專案,Visual C++ 編譯器就會在二進位檔中插入額外的安全性檢查,以協助偵測劫持程式碼的嘗試。We added a new security feature; simply add a new option to your project, and the Visual C++ compiler will now inject extra security checks into your binaries to help detect attempts to hijack your code. 當檢查引發時,它會停止執行您的程式碼,劫匪可能會對您的資料或電腦造成損害。When the check fires, it will stop execution of your code before a hijacker can do damage to your data or PC.

注意

我們已更新命令選項。We have updated the command options. 您現在應該使用/guard: cf,而不像舊版一樣使用/d2guard4 參數。Instead of using the /d2guard4 switch as you did in earlier releases, you should now use /guard:cf.

Visual C++ 生產力、偵錯工具和診斷Visual C++ Productivity, Debugging, and Diagnostics

藉由下列功能,我們已加入 C++ 的重構支援:We have added refactoring support for C++ with the following features:

  • 重新命名符號 將所有出現的符號變更為新的名稱。Rename Symbol Changes all occurrences of a symbol to a new name.
  • 函數解壓縮 將選取的程式碼移至它自己的函式。Function Extraction Move selected code into its own function. 這項重整功能可做為延伸模組,以 Visual Studio 在 Visual Studio 資源庫上。This refactoring is available as an extension to Visual Studio on the Visual Studio Gallery.
  • 執行純虛擬函式 針對類別或結構所繼承的純虛擬函式產生函式定義。Implement Pure Virtuals Generates function definitions for pure virtual functions inherited by a class or structure. 支援多個與遞迴的繼承。Multiple and recursive inheritance are supported. 從繼承的類別定義啟用這項重構功能,以實作所有繼承的純虛擬函式,或只從基底類別規範實作該基底類別的純虛擬函式。Activate this refactoring from the inheriting class definition to implement all inherited pure virtual functions, or from a base class specifier to implement pure virtual functions from that base class only.
  • 建立宣告或定義 從現有的定義產生宣告,或從現有的宣告產生預設定義。Create Declaration or Definition Generates a declaration from an existing definition or a default definition from an existing declaration. 從現有的宣告或定義,或從燈泡指示器存取這個重構。Access this refactoring from the existing declaration or definition, or from the light bulb indicator.
  • 移動函式定義 在原始程式碼和標頭檔之間移動函式主體。Move Function Definition Moves the body of a function between the source code and header files. 從該函式的簽章啟用這項重構。Activate this refactoring from the function's signature.
  • 轉換為原始字串常 值將包含 escape 序列的字串轉換成原始字串常值。Convert to Raw String Literal Converts a string containing escape sequences into a raw-string literal. 支援的 escape 序列為 \n (新行) 、\t (tab) 、 ' (單引號) 、 " (雙引號) 和 ?Supported escape sequences are \n (new line), \t (tab), ' (single quote), " (double quote), and ? (問號)。(question mark). 在字串內的任何位置按一下滑鼠右鍵,啟用這項功能。Activate this feature by right-clicking anywhere inside a string.

Visual C++ 中的程式資料庫 (PDB) 增強功能,包括下列各項:Program Database (PDB) enhancements in Visual C++ include the following:

  • 方案掃描速度已改進,特別是針對大型方案。Solution Scanning speed has been improved, especially for large solutions.
  • 除了在第一次開啟新方案時的初始方案掃描期間以外,在方案掃描期間,像是移至定義等的作業不會再受到封鎖。Operations like Go To Definition are no longer blocked during solution scan except during the initial solution scan when a new solution is opened for the first time.

IntelliSense 可讀性改進:已簡化參數說明和 quickinfo 中的複雜範本具現化和 typedef,使其更容易閱讀。IntelliSense Readability Improvements: Complex template instantiations and typedefs are simplified in parameter help and quickinfo to make them easier to read.

C + + 中的偵錯工具視覺效果Debugger Visualizations in C++

將 Natvis 偵錯工具視覺效果新增至您的 Visual Studio 專案,以方便管理和原始檔控制整合。Add Natvis debugger visualizations to your Visual Studio project for easy management and source control integration. 加入至專案的 Natvis 檔案之評估優先順序高於在專案外部的 Natvis 視覺化檢視。Natvis files added to a project take evaluation precedence over Natvis visualizers outside the project. 如需詳細資訊,請參閱 在偵錯工具中建立原生物件的自訂視圖For more information, see Create custom views of native objects in the debugger.

從 RC 開始,您可以在 Android 上的 c + + 進行調試時使用 Natvis 檔。And since RC, you can use Natvis files while debugging C++ on Android. 偵錯工具包含許多常見範本的視覺效果,並支援載入加入 c + + 專案的自訂檔案。The debugger includes visualizations for many common templates, and supports loading custom files that are added to the C++ project.

原生記憶體診斷Native Memory Diagnostics

  • 記憶體診斷會話 (Alt + F2) 可讓您監視原生應用程式的即時記憶體使用狀況。Memory diagnostic sessions (Alt+F2) enable you to monitor the live memory use of your native application.
  • 記憶體快照 集會捕捉應用程式堆積內容的瞬間映射。Memory snapshots capture a momentary image of your application's heap contents. 藉由比較兩個記憶體快照,可檢查堆積狀態中的差異。Differences in heap state can be examined by comparing two memory snapshots. 在停止應用程式之後,檢視物件類型、 執行個體值和每個執行個體的呼叫堆疊配置。View object types, instance values, and allocation call stacks for each instance after stopping the application.

改善死結偵錯與復原 當從監看式和即時運算視窗中呼叫 C++ 函式之時。Improved deadlock detection and recovery when calling C++ functions from the Watch and Immediate windows.

改進編譯器診斷:編譯器提供有關可疑程式碼的增強警告。Improved compiler diagnostics - The compiler provides enhanced warnings about suspicious code. 已加入新的警告 (例如已遮蔽的變數和不相符的 printf 格式字串)。New warnings have been added (for example, shadowed variables and mismatched printf format-strings). 現有的警告訊息已更加清楚。Existing warning messages have been made clearer.

/Wv 旗標-在特定編譯器版本 XX. YY 之後引進的警告。使用/Wv: XX. YY 可以停用 ZZZZ。ZZZZ 旗標。The /Wv flag - Warnings introduced after a specific compiler version XX.YY.ZZZZ can be disabled by using the /Wv:XX.YY.ZZZZ flag. 除了透過 /Wv 旗標指定的警告以外,亦可特別停用其他警告。Other warnings can be specifically disabled in addition to those specified through the /Wv flag.

已針對啟用/Zi、/Zo 或/Z7 旗標的優化程式碼偵錯工具程式碼,改進支援。Improved Support for Debugging Optimized Code - Debug code with the /Zi, /Zo, or /Z7 flags enabled.

Visual C++ 圖形診斷Visual C++ Graphics Diagnostics

已藉由下列功能改善圖形診斷:Graphics Diagnostics has been improved with the following features:

  • 連續捕捉 使用一個 capture 來捕捉最多30個連續的畫面格。Consecutive Capture Capture up to 30 consecutive frames with one capture.
  • 程式 設計捕獲 以程式設計方式起始框架捕獲。Programmatic Capture Initiate frame capture programmatically. 程式設計擷取特別適用於偵錯絕不呼叫存在的程式之計算著色器,或適用於當呈現問題很難手動擷取,但可透過程式設計方式從執行階段的應用程式狀態進行預測時。Programmatic capture is especially useful for debugging compute shaders in programs that never call Present, or when a rendering problem is difficult to capture manually but can be predicted programmatically from the state of the app at runtime.
  • 增強的圖形事件清單 加入新的 [繪製呼叫] 視圖,以顯示依繪製呼叫組織之階層中的捕捉事件和其狀態。Enhanced Graphics Event List A new Draw Calls view is added that displays captured events and their state in a hierarchy organized by Draw Calls. 您可以展開繪製呼叫,以顯示繪製呼叫時的目前裝置狀態,而且可以進一步展開每種狀態類型,以顯示設定其值的事件。You can expand draw calls to display the device state that was current at the time of the draw call and you can further expand each kind of state to display the events that set their values.
  • 支援 Windows Phone 8.1 圖形診斷現在可完全支援在 Phone 模擬器或行動網卡 Phone 上的 Windows 應用程式的偵錯工具。Support for Windows Phone 8.1 Graphics Diagnostics now fully supports debugging Windows apps in Phone emulator or on tethered Phone.
  • 圖形畫面格分析 此工具會收集所捕獲框架的效能測量;此外,它也會執行一組預先定義的實驗,以提供有關套用各種材質技術時之效能影響的深入資訊。Graphics Frame Analysis This tool collects performance measurements on captured frames; in addition, it performs a set of pre-defined experiments that provides insights into how performance would be affected when various texture techniques are applied. 畫面格分析也會從硬體收集效能計數器。Frame Analysis also collects performance counters from hardware.
  • 圖形分析的專用 UI 新的 Visual Studio 圖形分析器視窗是用於分析圖形畫面格的專用工作區。Dedicated UI for Graphics Analysis The new Visual Studio Graphics Analyzer window is a dedicated workspace for analyzing graphics frames.
  • 著色器編輯及 套用查看已捕捉記錄中著色器程式碼變更的影響,而不需要重新執行應用程式。Shader Edit and Apply View the impact of shader code changes in a captured log without re-running the app.
  • 在 [工具]-[選項-圖形診斷] 中設定 [ 抓取選項 ] > > 。Configure capture options in Tools->Options->Graphics Diagnostics.
  • 用來捕捉及播放畫面格的 命令列工具Command-line tool for capturing and playing back frames.
  • 圖形診斷 DirectX 12 的支援Graphics Diagnostics support for DirectX 12. Visual Studio 圖形診斷工具現在支援在 DirectX 12 應用程式中偵測轉譯問題。The Visual Studio Graphics Diagnostics tool now supports debugging rendering problems in DirectX 12 applications.

新的 GPU 使用量工具New GPU Usage tool

Visual Studio 2015 中的 GPU 使用量工具可用來了解 DirectX 應用程式的 GPU 使用量。The GPU Usage tool in Visual Studio 2015 can be used to understand GPU usage of DirectX applications. 即時執行應用程式時,可使用畫面格時間、 畫面播放速率和 GPU 使用率圖表。Frame Time, Frame Rate, and GPU Utilization graphs are available while the applications are running live. 此外,藉由收集和分析詳細的 GPU 使用量資料,這項工具可提供個別 DirectX 事件之 CPU 和 GPU 執行時間的深入資訊,因此有助於判斷 CPU 或 GPU 是否為效能瓶頸。In addition, by collecting and analyzing detailed GPU usage data, this tool provides insights into the CPU and GPU execution time of individual DirectX events, and therefore can be useful to determine whether the CPU or GPU is the performance bottleneck.

啟用 Visual C++ Managed 測試專案的偵錯工具Enabling debugging of a Visual C++ Managed Test Project

此版本的新功能:若要啟用 Visual C++ Managed 測試專案的偵錯工具,請移至 [工具 |選項 |調試 |一般] 窗格,然後核取 [模組載入時隱藏 JIT 優化 (僅限 Managed) ] 選項。New in this release: To enable debugging of a Visual C++ Managed Test Project, go to the "Tools | Options | Debugging | General" pane, and check the "Suppress JIT optimization on module load (Managed only)" option.

C # 和 Visual Basic C# and Visual Basic

語言功能Language Features

在此版本中,有數個新的 c # 和 Visual Basic 語言功能有助於減少日常程式碼中的重複使用和雜亂、鼓勵更宣告的程式設計樣式,並讓兩種語言更緊密結合。In this release, several new C# and Visual Basic language features help reduce boilerplate and clutter in everyday code, encourage a more declarative style of programming, and bring the two languages even closer together. 例如,類型和成員宣告以及 null 檢查都有語法改進。For example, there are syntactic improvements to type and member declarations and to null checking. 此外,區域變數可在運算式內宣告,而 await 可在 catch 和 finally 區塊中使用。In addition, local variables can be declared inside expressions, and await can be used in catch and finally blocks. 其中有許多功能只會針對舊版中的其中一種語言來執行,但最終版本將提供這兩種語言版本。Many of these features are implemented only for one of the two languages in earlier releases, but will be available to both languages in the final release.

  • Nameof 提供重構安全的方式,以字串形式取得參數、成員或類型的名稱。Nameof provides a refactoring-safe way of getting the name of e.g. a parameter, member or type as a string.
  • 使用 null 條件運算子 時,您可以在存取及叫用成員和索引子時取得內建 null 檢查。Using null-conditional operators, you can get a built-in null check while accessing and invoking members and indexers.
  • 字串插補:字串插補可提供簡潔的方式來描述將運算式插入格式字串中的字串範本 (c # 僅在預覽階段,在 RTM) 為 VB 和 c #。String interpolation: String interpolation provides a concise way of describing string templates that insert expressions into format strings (C# only at Preview, both VB and C# at RTM).
  • 方法僅限 getter 屬性 等,現在可以有單一運算式做為其主體,就像 lambda 一樣。Methods, getter-only properties, etc., can now have a single expression as their body, just like lambdas.
  • Auto 屬性 可以有初始化運算式,而不再需要 setter。Auto-properties can have initializers and no longer require setters.
  • 索引初始化運算式:在物件初始化運算式內,您現在可以初始化新物件的特定索引。Index initializers: Inside an object initializer, you can now initialize a specific index of the new object. 僅限 C#。C# only.
  • 例外狀況篩選準則 可讓您查看例外狀況,並決定是否使用指定的 catch 區塊攔截例外狀況。Exception filters let you look at an exception and decide whether to catch it with a given catch block.
  • 使用適用于 靜態類別 的子句會直接將其靜態成員帶入範圍中,因此您可以呼叫 ( # A1 或 Sqrt ( # A3 的範例,而不會在類別名稱前面加上。Using clauses for static classes bring their static members directly into scope, so you can call for example WriteLine() or Sqrt() without prefixing with the class name.
  • Await 現在可在 catch 和 finally 區塊中運作,回避一些很難解決的問題。Await now works in catch and finally blocks, obviating some very tricky workarounds.

程式碼編輯器 UI 和編輯Code Editor UI and Editing

C # 和 Visual Basic 的程式碼編輯器 UI 和編輯體驗,已由 .NET Compiler Platform ( "Roslyn" ) 上建的新體驗取代。The code editor UI and editing experiences for C# and Visual Basic have been replaced with new experiences built on the .NET Compiler Platform ("Roslyn"). 您今天所喜愛的許多功能都已獲得改良或改頭換面。Many of the features you love today have been improved or revamped.

  • Light 燈泡是您在 Visual Studio 編輯器中所採取之所有快速動作的新首頁,包括常見程式碼問題和重構程式碼的修正。Light bulbs are the new home for all quick actions you take in the Visual Studio Editor, including fixes to common code issues and refactoring code. 當您的程式碼發生問題時,燈泡會顯示這些問題的建議修正。When you have issues in your code, a light bulb shows suggested fixes for those issues. 所有重構作業都已移至燈泡。All refactoring operations have been moved to the light bulb. 您可以輸入 Ctrl + < 點 > 隨時存取燈泡。You can access the light bulb any time by typing Ctrl + <dot>.

燈泡顯示建議

  • 有兩個新的核心重構作業: 內嵌暫存變數 ,並 引進本機There are two new core refactoring operations: Inline temporary variable and Introduce local. 以下是新 引進本機 功能的範例:Here is an example of the new Introduce local feature:

引進區域變數燈泡

以及 內嵌暫存變數 的範例:And an example of Inline temporary variable:

內嵌暫存燈泡

  • 第一次新增對 Visual Basic 的重構支援,而且也已移至燈泡。Refactoring support for Visual Basic has been added for the first time, and has also been moved to the light bulb.
  • 重新命名也已改善;現在它會反白顯示您想要重新命名的所有識別碼實例,讓您可以直接在編輯器中,一次輸入所有實例的新名稱。Renaming has also been improved; now it highlights all the instances of the identifier you want to rename, letting you type the new name to all instances at once directly in the editor.

內嵌重新命名的增強功能

  • 您可以在輸入時取得即時程式碼分析和自動修正程式,並提供適用于您目標的 Microsoft 平臺和 NuGet 套件的特定程式碼感知指引。You can get live code analysis and automatic fixes as you type, with specific code-aware guidance for the Microsoft platforms and NuGet packages that you are targeting. 在預覽階段,您需要透過從 NuGet 資源庫取得的 NuGet 套件來加入即時 FxCop 分析器,就像任何其他套件一樣。At Preview, you need to add the live FxCop analyzers through a NuGet package you get from the NuGet Gallery, as you would any other package. 當您提取任何指定的即時規則時,它會取代對等的後置組建 FxCop 規則,因此您不會收到重複的叫用。As you pull in any given live rule, it displaces the equivalent post-build FxCop rule, so you don't get duplicate hits. 以下是來自 Azure 封裝程式 代碼分析 的範例。Here is an example from the Code Analysis for Azure package.

來自 Azure 程式碼分析套件的範例

  • 已重寫 c # 和 Visual Basic 的運算式評估工具。The expression evaluator for C# and Visual Basic has been rewritten. 改進功能包括在 [監看式] 和 [即時運算] 視窗中支援 LINQ 和 lambda 運算式。Improvements include support for LINQ and lambda expressions in the Watch and Immediate Windows.

F# F#

語言和執行時間功能Language and Runtime Features

F # 4.0 包含許多新的語言和執行時間的新增功能,這些專案會填滿間距、更多「工作」,並改善關鍵區域的效能。F# 4.0 contains numerous new language and runtime additions that fill in gaps, make more things "just work," and improve performance in key areas. 許多 bug 和小型效能優化都已在編譯器和執行時間中執行。Numerous bugs and small performance optimizations have been implemented across the compiler and runtime, as well.

  • 當做 一級函式的函式:類別名稱現在可以用為第一級函式值,代表該類別 (s) 的函式。Constructors as first-class functions - Class names can now be used as first-class function values, representing the constructor(s) for that class.
  • 統一 ' mutable ' 與 ' ref ' -' mutable ' 語法現在已可在任何地方使用,編譯器會在必要時,自動將其轉換成堆積的 ' ref ' 值。Unification of 'mutable' and 'ref' - The 'mutable' syntax can now be used everywhere, and captured values will be automatically converted to heap-based 'ref' values by the compiler when needed. 已加入新的選擇性警告,以備開發人員希望在發生這種情況時收到通知。A new optional warning has been added in case a developer wishes to be notified when this occurs.
  • 提供方法的靜態參數 -型別提供者提供的個別方法現在可以指定靜態參數。Static parameters to provided methods - Individual methods provided by type providers can now specify static parameters.
  • 不可為 null 的提供 類型-提供的型別現在可透過標準 [ < AllowNullLiteral (false) ] 指定為不可為 null > 。Non-nullable provided types - Provided types can now be specified as non-nullable through the standard [<AllowNullLiteral(false)>].
  • 方法引數的隱含引號 :類型 Expr 的方法引數 < > 現在可以明確加上引號,並傳遞引數值和產生它的運算式 AST。Implicit quotation of method arguments - Method arguments of type Expr<'t> can now be transparently auto-quoted, passing both the argument value and the AST of the expression that generated it.
  • 擴充預處理器文法 -布林運算子 | |、 && 和!Extended preprocessor grammar - Boolean operators ||, && and ! 現在可在 #if 預處理器指示詞中,搭配 ( ) 群組使用。can now be used, along with ( ) grouping, in #if preprocessor directives.
  • 測量單位中的有理指數 -測量單位現在支援有理指數,有時會用於實體科學(例如電子工程)Rational exponents in units of measure - units of measure now support rational exponents, that are sometimes used in physical sciences such as electrical engineering
  • 利用 ' printf ' 樣式的函式簡化測量單位的使用 -統一單位的數值現在已可無縫搭配數值 printf 格式的規範一起使用,而不需要移除單位。Simplified use of units of measure values with 'printf'-style functions - Unitized numerical values now work seamlessly with numerical printf format specifiers, without requiring the units to be removed.
  • 支援高維度的 .net 陣列 -F # 程式碼現在已可使用排名5或以上的 .net 陣列。Support for high-dimensional .NET arrays - .NET arrays of rank 5 or greater can now be consumed by F# code.
  • 物件初始化運算式中的擴充屬性 -現在可在物件初始化運算式運算式中指派可設定的擴充屬性。Extension properties in object initializers - Settable extension properties can now be assigned in object initializer expressions.
  • 從多個泛型介面具現化繼承 ,現在允許 F # 撰寫的類別繼承自實作為多個泛型介面具現化的類別。Inheritance from multiple generic interface instantiations - F#-authored classes are now permitted to inherit from classes that implement multiple generic interface instantiations.
  • ' StructuredFormatDisplayAttribute ' 中的多個屬性 -% 透過 [>structuredformatdisplay] 指定的格式 < > 現在可以包含多個屬性。Multiple properties in 'StructuredFormatDisplayAttribute' - %A formatting specified through [<StructuredFormatDisplay>] can now include multiple properties.
  • 前置的 ' microsoft ' 命名空間 可省略-從 fsharp.core 使用或開啟模組與命名空間時,領先的 "microsoft"。Leading 'Microsoft' namespace optional - When consuming or opening modules and namespaces from FSharp.Core, the leading "Microsoft." 現在是選擇性的。is now optional.

F# 執行階段F# Runtime

  • 正規化 陣列、清單及 seq 模組-集合處理函式集合現在在陣列、清單及 seq 模組中都是一致的, (不適用特定類型) 的 api,而且每種類型都有專用且優化的實作為。Normalization of Array, List, and Seq modules - the set of collection-processing functions is now consistent across the Array, List, and Seq modules (barring APIs not applicable to certain types), with dedicated, optimized implementations for each type.
  • 優化的結構化雜湊 -已進行大幅優化,以改善基本類型的泛型雜湊比較效能,藉由 api (例如 ' distinct ' 與 ' groupBy ')提升效能。Optimized structural hashing - Significant optimizations have been made to improve the performance of generic hash comparison for primitive types, leading to performance gains by APIs such as 'distinct' and 'groupBy'.
  • 優化的非結構化比較運算子 -fsharp.core 模組現在可以開啟,以更有效率的非結構化運算子取代預設的 F # 結構比較運算子。Optimized non-structural comparison operators - The FSharp.Core.Operators.NonStructuralComparison module can now be opened, replacing the default F# structural comparison operators with more efficient non-structural operators. 當使用自訂運算子實值(特別是實值型別)處理型別時,這可以大幅提升效能。This can provide significant performance gains when processing types with custom operator implementations, particularly value types.
  • 在 f # 清單上切割語法 : f # 清單現在支援切割語法以取得子清單。Slicing syntax on F# lists - F# lists now support slicing syntax for obtaining sub-lists.
  • AsyncDownloadFile 和 AsyncDownloadData 的 非同步擴充 功能現在已可供使用。Async extensions to System.Net.WebClient' - WebClient extensions AsyncDownloadFile and AsyncDownloadData are now available.
  • 更好的非同步堆疊追蹤 -F # 非同步運算中發生的例外狀況現在會提供更容易使用的堆疊追蹤,讓您更輕鬆地診斷問題。Better Async stack traces - Exceptions occuring in F# async computations now carry more user-friendly stack traces, making it easier to diagnose issues.
  • 選項的 Interop api (適用于選項 -各種新的 api)已新增至選項模組,以便在 null 物件和系統的 null 值之間進行轉換。Interop APIs for Option - Various new APIs were added to the Option module for converting to and from null objects and System.Nullable values.
  • Decimal 值的引號現用模式 :目前內建使用中的模式,以符合常數常值 System。引號中的十進位值。Quotation active pattern for System.Decimal values - An active pattern is now built in for matching constant literal System.Decimal values in quotations.

F # IDE 功能F# IDE Features

Visual F# 工具也有新的體驗和功能,以及許多 bug 修正。There are new experiences and features in the Visual F# tools, as well, along with a number of bug fixes.

  • 腳本調試 程式:現在可以直接在 Visual Studio 偵錯工具中調試 F # 腳本。Script debugging - F# scripts can now be debugged directly in the Visual Studio debugger.
  • 專案範本中的元件中繼資料 -所有 F # 專案範本現在都包含 AssemblyInfo 檔案,其中包含萬用群組件層級的中繼資料屬性。Assembly metadata in project templates - All F# project templates now contain a file AssemblyInfo.fs that contains common assembly-level metadata attributes.
  • 整合最新的檢查 -F # 專案現在可在 Visual Studio 中建立時,正確地報告其「最新」狀態。Integrated up-to-date check - F# projects now correctly report their "up-to-date" status when building in Visual Studio.
  • 物件初始化運算式中的 intellisense 完成 -物件初始化運算式運算式現在支援使用 Ctrl + 空格鍵 完成可設定屬性的 intellisense。IntelliSense completion in object initializers - Object initializer expressions now support IntelliSense completion of settable properties, using Ctrl+Space.
  • Intellisense 完成具名引數 -方法和函式呼叫現在支援使用 Ctrl + 空格鍵 自動完成具名引數的 intellisense。IntelliSense completion for named parameters - Method and constructor calls now support IntelliSense auto-completion of named parameters, using Ctrl+Space.
  • 資料夾支援方面的 Bug 修正 -Visual F# 工具不直接支援專案中的資料夾,但已修正數個專案系統 bug,改善 Visual F# Power Tools 擴充功能所新增的資料夾支援。Bug fixes around folder support - Visual F# tools do not directly support folders in projects, but a number of project system bugs have been fixed improve the folder support added by the Visual F# Power Tools extension.

.NET Framework 4。6 The .NET Framework 4.6

.NET Framework 的最新版本為4.6。The newest version of the .NET Framework is 4.6. 它提供許多應用程式開發技術的增強功能,例如 ASP.NET、Windows Communication Foundation 和 Windows Presentation Foundation。It features numerous enhancements in application development technologies such as ASP.NET, Windows Communication Foundation, and Windows Presentation Foundation. 此外,網路功能、.NET Framework 基類程式庫和 common language runtime (都有變更,包括新的64位 JIT 編譯程式、通用 Windows 平臺應用程式的原生程式碼編譯、) 的元件載入器改進。There are also changes in networking, the .NET Framework base class library, and the common language runtime (including a new 64-bit JIT compiler, native code compilation for Universal Windows Platform apps, assembly loader improvements).

只有變更的取樣包括:Just a sampling of the changes include:

  • ASP.NET 模型系結方法現在會傳回工作。ASP.NET Model Binding methods now return tasks.
  • ADO.NET 現在支援 SQL Server 2016 Community Technical Preview 2 (CTP2) 中提供的 Always Encrypted 功能。ADO.NET now supports the Always Encrypted feature available in SQL Server 2016 Community Technology Preview 2 (CTP2).
  • Windows Presentation Foundation (WPF) 針對觸控和改良的 HDPI 配置提供更好的支援。Windows Presentation Foundation (WPF) offers better support for touch and improved HDPI layout.
  • Windows Communication Foundation (WCF) 除了 SSL 3.0 和 TLS 1.0 之外,現在還支援 SSL 版本的 TLS 1.1 和 TLS 1.2。Windows Communication Foundation (WCF) now supports SSL version TLS 1.1 and TLS 1.2, in addition to SSL 3.0 and TLS 1.0.
  • .NET Framework 基礎類別庫包括垃圾收集、以工作為基礎的非同步模式,以及密碼編譯的增強功能。The .NET Framework base class library includes enhancements to garbage collection, to the task-based asynchronous pattern, and to cryptography. 它也會新增啟用 SIMD 的向量類型,以及支援相容性參數,讓開發人員能夠針對其程式庫的新版本所支援的功能提供統一退出機制。It also adds SIMD-enabled vector types, as well as support for compatibility switches that allow developers to provide a uniform opt-out mechanism for functionality supported by a new vesion of their libraries.

如需其他詳細資料,以及新增至 .NET Framework 的新功能完整清單,請參閱 .NET Framework 中的新功能。For additional detail and a complete list of the new features added to the .NET Framework, see What's New in the .NET Framework.

Entity Framework Entity Framework

此版本包含 Entity Framework 7 的預覽版本,以及 Entity Framework 6 的更新,主要包含 bug 修正和社區投稿。This release includes a preview version of Entity Framework 7 and an update of Entity Framework 6 that primarily includes bug fixes and community contributions.

Entity Framework 7Entity Framework 7

新版本的 Entity Framework 可讓新的平臺和新的資料存放區。The new version of Entity Framework enables new platforms and new data stores. Windows Phone、Windows Store、ASP.NET 5 和傳統桌面應用程式現在可以使用 Entity Framework。Windows Phone, Windows Store, ASP.NET 5, and traditional desktop application can now use Entity Framework. 此版本的架構支援關係資料庫,以及非關聯式資料存放區(例如 Azure 資料表儲存體和 Redis)。This version of the framework supports relational databases as well as non-relational data stores such as Azure Table Storage and Redis. 它包含 EF7 執行時間的早期預覽,該執行時間會安裝在新的 ASP.NET 5 專案中。It includes an early preview of the EF7 runtime that is installed in new ASP.NET 5 projects. 如需 EF7 的詳細資訊,請參閱 EF7 的相關資訊。For more information on EF7, see What is EF7 all about.

Entity Framework 6。xEntity Framework 6.x

此版本包含 EF 6.1.3 版本的執行時間和工具。This release includes the EF6.1.3 version of the runtime and tooling. EF 6.1.3 包含 bug 修正和社區投稿;您可以在我們的 Entity Framework CodePlex 網站上,查看 ef 6.1.3 中包含的變更清單。EF6.1.3 includes bug fixes and community contributions; you can see a list of the changes included in EF6.1.3 on our Entity Framework CodePlex site.

Entity Framework 6.1.1 執行時間包含在此版本的數個位置中。The Entity Framework 6.1.1 runtime is included in a number of places in this release.

  • 如果您在尚未安裝 EF 執行時間的專案中使用 Entity Framework Tools 建立新的模型,則會安裝執行時間。The runtime will be installed if you create a new model using the Entity Framework Tools in a project that does not already have the EF runtime installed.
  • 執行時間會預先安裝在新的 ASP.NET 專案中,視您選取的專案範本而定。The runtime is pre-installed in new ASP.NET projects, depending on the project template you select.

Visual Studio IDE Visual Studio IDE

共用帳戶Shared Accounts

這一版的新功能,您可以與其他應用程式共用您在 Visual Studio 中新增的使用者帳戶,例如使用 Blend for Visual Studio 或 Microsoft Test Manager (,反之亦然) 。New in this release, you can share the user accounts that you add in Visual Studio with other apps, such as with Blend for Visual Studio or with Microsoft Test Manager (and vice versa).

共用的專案Shared Projects

在此版本中,您可以使用新的範本,為 Visual Basic、c # 和 JavaScript 建立空白的共用專案。In this release, new templates are available to create empty shared projects for Visual Basic, C#, and JavaScript. 這些共用專案現在可由數種專案類型參考:These shared projects can now be referenced by several project types:

  • 任何未 flavored 的 VB/c # 專案 (例如主控台應用程式、類別庫、Win 表單應用程式) Any un-flavored VB/C# projects (e.g. console apps, class libraries, Win form app)
  • Windows Store 8.1 和 Windows Phone 8.1 (VB/c #/JavaScript) Windows Store 8.1 and Windows Phone 8.1 (VB/C#/JavaScript)
  • Windows Phone Silverlight 8.0/8.1 (VB/c # ) Windows Phone Silverlight 8.0/8.1 (VB/C#)
  • WPF 和 PCLWPF and PCL

您可以在 [共用專案] 索引標籤上,透過參考管理員新增/移除共用專案的參考。共用專案參考會顯示在方案總管的 [參考] 節點底下,但是共用專案中的程式碼和資產會視為連結至主要專案的檔案。You can add/remove references to shared projects through Reference Manager, on the Shared Projects tab. The shared project reference shows up under the References node in the Solution Explorer, but the code and assets in the shared project are treated as if they were files linked into the main project.

程式碼編輯器 (所有語言) Code Editor (All Languages)

[檔案 中尋找] 已經過改善,可讓後續結果附加至先前的結果;您可以刪除累積的結果。Find in Files has been improved by enabling subsequent results to be appended to previous results; accumulated results can be deleted.

您現在可以在 Visual Studio 編輯器中取得 觸控支援,以進行下列手勢:Touch support is now available in the Visual Studio editor for the following gestures:

  • 滾動 (在 [一般] 和 [增強] 捲軸上,在編輯器介面上進行點擊和拖曳) Scrolling (tapping-and-dragging on the editor surface on the regular and enhanced scrollbars)
  • 縮小至縮放比例Pinch-to-Zoom
  • 藉由在編輯器邊界中按一下來選取整行,然後按兩下以選取單字Select a whole line by tapping in the editor margin, and select words by double-tapping them
  • 按下並按住以叫用編輯器內容功能表Invoking the editor context menu by pressing-and-holding

我們注意到觸控的一個問題,那就是點兩下的手勢不一定會在較低的縮放層級上可靠。We are aware of one issue with touch, in that the double-tap gesture is not always reliable at lower zoom levels. 我們想要聽取新觸控支援的意見反應,特別是您可能發現的任何問題。We would like to hear feedback on the new touch support, and in particular any issues you may find.

XAML 設計工具XAML Designer

Visual Studio 客戶現在可以在其使用方式的內容中編輯儲存在外部資源字典中的範本和樣式。Visual Studio customers will now be able edit their Templates and Styles stored in external resource dictionaries within the context of their usage. 這項體驗已經過進一步的調整,可讓您在 XAML 設計工具中使用查看來啟用真正的內部原位資源編輯。This experience has been further refined to use Peek to enable a true in-situ resource editing in the XAML designer.

自訂視窗版面配置Custom Window Layouts

您現在可以從 [視窗] 功能表按一下 [儲存視窗配置],以儲存自訂視窗版面配置,並從 [視窗] 功能表按一下 [套用 視窗 配置],以套用自訂版面配置。You can now save custom window layouts by clicking Save Window Layout from the Window menu, and apply a custom layout by clicking Apply Window Layout from the Window menu. 您也可以使用預先指派的鍵盤快速鍵來套用版面配置。You can also apply a layout by using the pre-assigned keyboard shortcuts. 前九個配置也有鍵盤快速鍵,從 Ctrl + Alt + 1 到 Ctrl + Alt + 9。The first nine layouts also have keyboard shortcuts from Ctrl + Alt + 1 to Ctrl+Alt+9. 您可以執行的其他工作包括刪除、重新命名和重新排列版面配置,方法是從 [視窗] 功能表按一下 [管理視窗配置]。Other tasks you can perform include deleting, renaming, and reordering layouts by clicking Manage Window Layout from the Window menu.

High-Resolution 圖示High-Resolution Icons

當您的裝置以大於100% 的 DPI 縮放比例執行時,Visual Studio 在命令列、工具視窗工具列 (標準) 、主要功能表、錯誤清單、狀態列和某些方案總管專案類型中支援高解析度圖示。Visual Studio supports high resolution icons in command bars, tool window toolbars (standard), the main menus, error list, status bar, and some Solution Explorer project types when your device is running at greater than 100% DPI scaling.

UI 改善UI Improvements

  • 功能表現在以標題大小寫樣式來顯示,而不是全部大寫樣式。Menus now appear in Title Case style instead of ALL CAPS style.
  • 在關閉並重新開啟屬性頁時,[Visual C++] 屬性頁對話方塊的 [設定] 和 [平臺] 下拉式清單值已變更,以記住最後一個使用者選取的專案。The Configuration and Platform dropdown values for the Visual C++ Property Page dialog have been changed to remember the last user selection when the property page is closed and reopened.

Visual Studio 意見反應Visual Studio Feedback

我們加強了 傳送苦臉 的體驗,並提供更好的工具來回報緩慢、停止回應和當機。We enhanced the Send a Frown experience with better tools to report slowness, hangs, and crashes. 您現在可以附加檔案或標記意見反應,以便更妥善地描述問題。You can now attach files or tag your feedback, to better describe the issue as well. 此外,我們也更新了 意見 反應圖示和功能表項目,以改善探索能力。Furthermore, we updated the Feedback icons and menu items to improve discoverability.

Visual Studio 擴充性Visual Studio Extensibility

  • 您現在可以在 Visual Studio 擴充功能中使用高解析度圖示。You can now use high-resolution icons in your Visual Studio extensions.
  • 此版本不再支援增益集。Add-ins are no longer supported in this release. 我們移除了 Visual Studio 的增益集專案範本和增益集管理員。We removed Visual Studio add-in project templates and the Add-in Manager. 建議您將增益集轉換成 VSPackage 擴充功能。We recommend that you convert your add-ins to VSPackage extensions. 如需詳細資訊,請參閱 常見問題:將增益集轉換成 VSPackage 擴充功能For more information, see the FAQ: Converting Add-ins to VSPackage Extensions.
  • 您現在可以開啟擴充性專案,即使您未安裝 Visual Studio SDK 也一樣。You can now open an extensibility project even if you do not have the Visual Studio SDK installed.
  • 此外,您可以使用 Visual Studio 安裝程式來安裝 Visual Studio SDK;您不再需要前往網站。Additionally, you can install the Visual Studio SDK by using Visual Studio setup; you no longer have to go to a website. 若要這樣做:請在 [新增移除程式] 功能表上,以滑鼠右鍵按一下 [Visual Studio 2015],然後選取 [修改]。To do this: On the Add Remove Programs menu, right-click Visual Studio 2015, and then select Modify. 從 Visual Studio 設定] 對話方塊中,檢查 [一般工具] 底下的 Visual Studio 擴充性工具。From the Visual Studio Set-up dialog, check Visual Studio Extensibility Tools under Common Tools.
  • 若要增加擴充專案的可攜性和共用,您可以使用 Visual Studio SDK 參考元件的 NuGet 版本。For increased portability and sharing of extension projects, you can use the NuGet versions of the Visual Studio SDK Reference Assemblies. 如需詳細資訊,請參閱 Visual Studio擴充性所發行的元件。For more information, see assemblies published by Visual Studio Extensibility.

深入瞭解 Visual Studio擴充性。Learn more about Visual Studio Extensibility.

Blend Blend

我們重新設計了 Blend for Visual Studio 2015,以提供更佳的使用者介面開發體驗來建立美觀的 XAML 應用程式。We redesigned Blend for Visual Studio 2015 to provide you with an improved user interface development experience for creating beautiful XAML apps. Blend 具有與 Visual Studio 一致的全新外觀、解決方案和 Team Explorer 的支援,以及擴充的檔案重載體驗,以促進 Blend 和 Visual Studio 之間更好的工作流程。Blend has a sleek new look consistent with Visual Studio, support for Solution and Team Explorer, and an enriched file reload experience to facilitate a better workflow between Blend and Visual Studio. 我們也提供 Blend 最需要的功能,以協助您提高生產力:We also delivered Blend's top most wanted features to help you be more productive:

  • 您現在可以使用 XAML IntelliSense 來更有效率地撰寫 XAML,以提供語句完成和流覽至來源。You can now write XAML more efficiently using XAML IntelliSense that provides statement completion and navigation to source.
  • 您也可以在使用 XAML 查看定義的內容中,查看及編輯 XAML 控制項和資源。You can also view and edit XAML controls and resources within the context in which they are used with XAML Peek Definition.
  • 您現在可以更輕鬆地使用 XAML 偵錯工具的 UI 工具來尋找和修正執行中應用程式的 UI 問題,讓您可以檢查即時視覺化樹狀結構和樹狀結構中任何專案的屬性。Finding and fixing UI issues in your running app is now easier using UI tools for XAML debugging that allow you to inspect the live visual tree and the properties of any elements in the tree.
  • 新增 NuGet 支援後,您就可以在 Blend 中管理 NuGet 套件。With NuGet support added, you can manage NuGet packages in Blend.
  • 我們也以更強大的同步配置功能取代了動畫工作區功能,您可以用來建立許多不同的視窗版面配置,並將它們漫遊到電腦上。We also replaced the Animation Workspace feature with the more powerful Synchronized Layouts feature that you can use to create many different window layout and roam them across machines.
  • 針對要使用鍵盤而不是滑鼠的 power 使用者,我們讓 Blend 設計工具窗格能夠完全存取鍵盤。For power users who would rather use their keyboard instead of mouse, we made the Blend designer panes fully keyboard accessible.
  • 最後,隨著 Microsoft 不斷努力建立通用的可存取軟體,Blend 現在是全螢幕閱讀和高對比的可存取。Finally, as part of Microsoft's ongoing effort towards creating universally accessible software, Blend is now a full screen reader and high-contrast accessible.

若要深入瞭解 Blend 中加入的新功能,請造訪我們的 預覽 blog 文章。To learn more about new features added to Blend, visit our Preview blog post.

偵錯與診斷 Debugging and Diagnostics

附加時的 Managed 編輯後繼續Managed Edit and Continue on Attach

從 RC,您可以在附加至 .NET 應用程式以及環境變數時,編輯並繼續As of RC, you can edit and continue when you attach to .NET applications and when the environment variable

目標進程中的 complus_forceenc 設定為1。complus_forceenc is set to 1 in the target process.

中斷點設定Breakpoint Configuration

新的 [中斷點設定] 視窗可讓您指定中斷點的條件和動作。The new Breakpoint Settings window allows you to specify conditions and actions for your breakpoints. 此視窗包含對中斷點條件和動作的改良 IntelliSense 支援。The window includes improved IntelliSense support for breakpoint conditions and actions. 您可以使用 [復原] (CTRL + Z) 來還原已刪除的中斷點。You can use undo (CTRL+Z) to restore deleted breakpoints.

偵錯工具視窗中的 Lambda 運算式Lambda Expressions in Debugger Windows

您現在可以在 [監看式]、[即時運算] 和其他偵錯工具視窗中,使用 c # 和 Visual Basic 的 lambda 運算式。You can now use lambda expressions in the Watch, Immediate, and other debugger windows in C# and Visual Basic.

效能提示PerfTips

您可以使用效能提示功能來查看當您使用偵錯工具設定中斷點和步驟時,直接在編輯器中執行程式碼所需的時間。You can use the PerfTips feature to see how long code took to execute directly in the editor when you set breakpoints and step with the debugger.

GPU 使用量GPU Usage

您可以使用 GPU 使用量工具,來瞭解 DirectX 應用程式的 GPU 使用量。You can use the GPU Usage tool to understand GPU usage of DirectX applications. 當應用程式即時執行時,可以使用畫面格時間、畫面播放速率和 GPU 使用率圖形。Frame Time, Frame Rate, and GPU Utilization graphs are available when the applications run live. 此外,藉由收集和分析詳細的 GPU 使用量資料,此工具可讓您深入瞭解每個 DirectX 事件的 CPU 和 GPU 執行時間,因此有助於判斷 CPU 或 GPU 是否為效能瓶頸。In addition, by collecting and analyzing detailed GPU usage data, this tool can provide insights into the CPU and GPU execution time of each individual DirectX event, and therefore can be useful to determine whether the CPU or GPU is the performance bottleneck.

C + + 偵錯工具的改善Improvements in the C++ Debugger

當 c + + 偵錯工具在中斷點停止時,它可以執行程式碼以計算結果,例如在監看式和即時運算視窗中顯示您的資料。When the C++ debugger is stopped at breakpoints, it can execute code in order to compute results, such as to show you data in the Watch and Immediate windows. 如果偵錯工具偵測到呼叫的函式已鎖死,則會嘗試解決此問題。If the debugger detects that a called function is deadlocked, it will attempt to resolve the issue.

當 c + + 偵錯工具啟動進程時,視窗現在會使用一般堆積(而非 debug 一般堆積)來配置記憶體。When a C++ debugger launches a process, Windows now allocates memory using the normal heap rather than the debug normal heap. 這會導致更快開始進行偵錯。This results in a faster start for debugging.

XAML 的 UI 偵錯工具UI debugging tools for XAML

我們加入了兩個新工具,也就是即時視覺化樹狀結構和即時屬性瀏覽器,可檢查您執行中的 WPF 應用程式的視覺化樹狀結構,以及樹狀結構中任何專案的屬性。We added two new tools, the Live Visual Tree and the Live Property Explorer that inspects the visual tree of your running WPF application, as well as the properties on any element in the tree. 這些工具可讓您選取執行中應用程式中的任何元素,並顯示最終、計算和轉譯的屬性。These tools allow you to select any element in your running app and show the final, computed, and rendered properties. 這些工具也包含下列各項:The tools also include the following:

  • 即時視覺化樹狀結構。Live Visual Tree. 現在,您可以在偵錯工具期間查看正在執行之應用程式的完整視覺化樹狀結構。Now, you can view the full visual tree of a running application during a debug session. 當您在 Visual Studio 中按下 F5 或附加到執行中的應用程式時,就可以使用 [即時視覺化樹狀結構]。The Live Visual Tree is available when you press F5 in Visual Studio or attach to a running application. 您可以使用 [即時視覺化樹狀] 來選取執行中應用程式中的專案,以便在即時屬性瀏覽器中進行檢查。You can use the Live Visual Tree to select elements in a running application for inspection in the Live Property Explorer. 子系計數隨即顯示,如果來源資訊可用,您可以立即找到專案定義的檔案和位置。Descendant count is displayed, and if the source information is available, you can instantly find the file and location of the element's definition.
  • 即時屬性瀏覽器。Live Property Explorer. 使用這項新工具檢查執行中應用程式的任何專案上設定的屬性,並依設定的範圍分組。Use this new tool to inspect the properties set on any element in a running application, grouped by the scope that they are set. 您可以在偵錯工具期間修改這些屬性,並立即在執行中的應用程式中看到其變更。You can modify these properties during a debugging session and immediately see their changes in the running application.

挑選屬性如何互相覆寫,並找出獲獎的行為,在設計階段會很困難。Picking apart how properties override each other and figuring out winning behavior can prove difficult at design time. 現在,藉由使用新的 XAML UI 偵錯工具,您可以在執行時間執行這些檢查。Now, by using our new UI debugging tools for XAML, you can perform these inspections at runtime.

未來的更新將會發行 Windows Store 應用程式的 (支援。 ) (Support for Windows Store apps will be released in a future update.)

XAML 的 UI 偵錯工具,全螢幕

例外狀況設定Exception Settings

您可以使用 [例外狀況設定] 工具視窗來設定偵錯工具例外狀況設定。You can configure debugger exception settings by using the Exception Settings tool window. 新視窗為非強制回應,包含改良的效能、搜尋及篩選功能。The new window is non-modal and includes improved performance, search, and filter capabilities.

例外狀況設定-擲回時中斷視窗

時間軸工具Timeline Tool

新的時間軸工具為您提供以案例為中心的應用程式所取用資源的觀點,讓您可以用來檢查、診斷及改進 WPF 和 Windows Store 8.1 應用程式的效能。Our new Timeline tool provides you with a scenario-centric view of the resources that your applications consume that you can use to inspect, diagnose, and improve the performance of your WPF and Windows Store 8.1 applications.

效能和診斷中樞的時間軸工具,會顯示您的應用程式在準備 UI 框架以及服務網路和磁片要求時花費了多少時間。The Timeline tool that is in the Performance and Diagnostics hub shows you how much time your application spends in preparing UI frames and in servicing networks and disk requests. 此工具會在應用程式載入和頁面載入等案例的內容中執行此操作。The tool does so in the context of scenarios such as Application Load and Page Load.

新的時間軸工具

診斷工具Diagnostics Tools

我們新增了新的診斷工具視窗,當您啟動偵錯工具時就會出現 (按 F5) 。We added a new Diagnostic Tools window that appears when you start debugging (press F5). [診斷工具] 視窗包含下列功能:The Diagnostics Tools window contains the following features:

  • 使用 IntelliTrace) 的事件 ( Events (with IntelliTrace)
    使用 IntelliTrace (的事件) 可讓您存取在偵測會話期間收集的所有偵錯工具中斷、輸出和 IntelliTrace 事件。Events (with IntelliTrace) gives you access to all Debugger Break, Output, and IntelliTrace events collected during your debugging session. 資料會以時間軸和表格式視圖的形式呈現。The data is presented both as a timeline and as a tabular view. 這兩個視圖會進行同步處理,而且可以彼此互動。The two views are synchronized and can interact with each other.
  • 記憶體使用量 Memory Usage
    記憶體使用量工具可讓您在進行偵錯工具時,監視應用程式的記憶體使用量。The Memory Usage tool allows you to monitor the memory usage of your app while you are debugging. 您也可以採用和比較詳細的原生和受控記憶體快照,來分析記憶體成長和記憶體流失的原因。You can also take and compare detailed snapshots of native and managed memory to analyze the cause of memory growth and memory leaks.
  • CPU 使用量 CPU Usage
    CPU 使用量工具可讓您在進行偵錯工具時,監視應用程式的 CPU 使用量。The CPU Usage tool allows you to monitor the CPU usage of your application while you are debugging.
    (此工具會取代 Visual Studio 2015 的預覽版本中可用的 CPU 時間 PerfTip。 ) (This tool replaces the CPU time PerfTip that was available in the Preview release of Visual Studio 2015.)

在先前的版本中,[診斷工具] 視窗支援下列專案類型和偵錯工具設定:In previous releases, the Diagnostics Tools window supported the following project types and debugging configurations:

  • Managed WPF、WinForms 和主控台專案Managed WPF, WinForms, and Console projects
  • 原生 Win32、Console 及 MFC 專案Native Win32, Console, and MFC projects
  • ASP.NET 4 僅使用 IIS expressASP.NET 4 using IIS express only
  • 在本機執行的受控或原生 Windows Store 專案Managed or Native Windows Store projects running locally
    不支援 (使用 JavaScript 或在手機上執行的 Windows Store 專案) (Windows Store projects that are using JavaScript or are running on a phone are not supported)

RC 版本中的 [診斷工具] 視窗有下列改良功能:The Diagnostic Tools window in the RC release has the following improvements:

  • 它可移至 Visual Studio 內的任何視窗位置,並記住其在偵測會話之間的位置和大小It can be moved to any window location within Visual Studio and remembers its location and size between debugging sessions
  • 當使用 Debug > 附加至進程附加至進程時,會出現並顯示單一進程的資料It appears and shows data for a single process when attaching to a process using Debug -> Attach to process
  • 它會在 ASP.NET 執行于 IIS 上的專案進行調試時顯示It appears when debugging ASP.NET projects running on IIS
  • 它會在調試 ASP.NET 5 個專案時顯示It appears when debugging ASP.NET 5 projects
  • 當您在遠端 Windows 桌面裝置上執行應用程式的偵錯工具時,會出現此情況It appears when debugging an app running on a remote Windows desktop device
  • 當您停止調試之後,可以看到記憶體快照集Memory snapshots can be viewed after you stop debugging
  • 偵錯工具事件 (只在偵測原生專案時,才可使用) 事件Debugger Events (break events only) are available when debugging native projects

我們也新增了 RC 版本的下列新功能:We also added the following new features for the RC release:

Just My CodeJust My Code. 當您按 F5 啟動偵錯工具時,它只會顯示您的程式碼,讓您可以瞭解效能問題和例外狀況,而不會干擾架構和其他程式碼。When you press F5 to launch the debugger, it will show only your code so that you can understand performance issues and exceptions without noise from framework and other code. 因為 IntelliTrace 中這個新的程式碼篩選功能會隱藏系統程式碼,並只公開使用者程式碼,所以可讓您更輕鬆地進行「僅限我的程式碼」。Because this new code filtering functionality in IntelliTrace suppresses system code and exposes only user code, it makes it easier for you to debug "just my code."

網路診斷工具Network Diagnostic Tool. 這種新的網路診斷工具可協助您在建立 Windows store 應用程式,以及在所有 Windows 10 裝置上執行的通用應用程式(從 Windows Phone 到 Xbox 和 Windows Store),以協助您診斷網路相關問題。This new network diagnostic tool can help you diagnose network-related issues when building Windows store apps as well as universal apps that run across all Windows 10 devices, from Windows Phone to Xbox and Windows Store.

網路診斷工具會記錄您應用程式的 HTTP 網路作業資訊,包括 HTTP 要求和回應標頭、要求和回應承載、cookie 和詳細的計時資訊等等。The network diagnostic tool records information about your app's HTTP network operations, including HTTP request and response headers, request and response payloads, cookies and detailed timing information, and more. 網路診斷工具也可以協助回答有關一般案例的問題,例如:The network diagnostic tool can also help answer questions about common scenarios, such as:

  • 驗證相關問題 (例如,您無法存取資源的原因) Authentication related issues (for example, why you are not able to access a resource)
  • 快取相關問題 (例如,為什麼您未取得最新版本的資源) Cache related issues (for example, why you are not getting the latest version of a resource)
  • 執行應用程式的一般工作時下載的位元組數目How many bytes are downloaded when running common tasks of your apps
  • 存取和下載資源時的瓶頸Where are the bottlenecks when accessing and downloading a resource

若要存取網路工具,請在 Visual Studio 2015 中開啟 [診斷工具] 視窗。To access the Network tool, open the Diagnostics Tools window in Visual Studio 2015. 在 [ 調試 ] 功能表上,選取 [ 啟動診斷工具而不進行調試On the Debug menu, select Start Diagnostic Tools without Debugging. 或者,只需按 Alt + F2。Alternatively, just press Alt+F2.

我們對在進行偵錯工具時所顯示的診斷工具視窗進行了下列改善:We made the following improvements to the Diagnostic Tools window that appears while Debugging:

  • 來自您應用程式的事件現在會出現在單一 IntelliTrace 事件追蹤中,而不是在 IntelliTrace 事件和輸出事件追蹤之間進行分割。Events from your app now appear in a single IntelliTrace Events track instead of split between the IntelliTrace Events and Output Events tracks.
  • 您的應用程式中的事件現在會在程式執行時出現;現在您不再需要按 [全部中斷] 來查看事件。Events from your app now appear while your program is running; now you no longer have to press "Break All" to see events.
  • 您現在可以針對已在程式碼中設定的追蹤點啟動歷程記錄偵錯工具,讓您可以查看原始程式碼和呼叫堆疊。You can now activate Historical Debugging for Tracepoints that you have set in your code, allowing you to see the source code and call stack.
  • 您現在可以在記憶體使用量圖表上看到垃圾收集和快照事件,讓您可以查看 managed 垃圾收集發生的時間,以及使用記憶體使用量工具拍攝快照集的時間。You can now see Garbage Collection and Snapshot events on the Memory Usage graph so that you can see when managed garbage collections occurred and when you took snapshots with the Memory Usage tool.

ASP.NET ASP.NET

ASP.NET 4。6ASP.NET 4.6

ASP.NET 模型系結支援工作傳回方法ASP.NET Model Binding supports Task returning methods

先前工作傳回的 ASP.NET 模型系結方法不受支援,且在執行時間擲回例外狀況(如果已設定)。ASP.NET Model Binding methods that were previously Task returning were not supported and threw an exception at runtime if configured. 如果使用這類方法部署應用程式,這些方法現在會正確執行。If applications are deployed with such methods, these methods are now executed correctly. 這種變更只適用于特別以 .NET 4.6 或更新版本為目標的應用程式。This change applies only to applications specifically targeting .NET 4.6 or later.

在 ASP.NET 應用程式中啟用 .NET Compiler Platform ( "Roslyn" )Enabling the .NET Compiler Platform ("Roslyn") in ASP.NET applications

您可以在任何 ASP.NET 4.6 專案中使用 c # 和 VB 的新語言功能。You can use the new language features of C# and VB in any ASP.NET 4.6 project. VS 2015 中的 Web Form 範本已預先安裝 >microsoft.codedom.providers.dotnetcompilerplatform 套件。The Web Forms templates in VS 2015 have the Microsoft.CodeDom.Providers.DotNetCompilerPlatform package pre-installed.

新增 HTTP/2 支援Add support for HTTP/2

在 Windows 10 和 .NET Framework 4.6 中,我們新增了對 HTTP/2的支援。In Windows 10 and .NET Framework 4.6, we added support for HTTP/2. HTTP/2 的主要目標是使用瀏覽器到網站的單一連接,改善效能、延遲和網路使用量。The main goal for HTTP/2 is to improve performance, latency, and network usage by using a single connection from browsers to a Web site.

更新的架構和控制項,以支援 Entity Framework 6Updated Frameworks and controls to support Entity Framework 6

我們已更新動態資料 Framework、實體資料來源控制項和 Universal Providers,讓它們可以與 Entity Framework 6 搭配使用。We updated Dynamic Data Framework, Entity Data Source Control, and Universal Providers so they work with Entity Framework 6.

驗證更新Authentication Updates

ASP.NET 4.6 範本現在會使用 Open Id Connect 中介軟體向 Azure AD 進行驗證。The ASP.NET 4.6 templates now use Open Id Connect middleware to authenticate with Azure AD. 這可讓程式設計模型以更簡單的方式驗證 Azure AD。This makes the programming model to authenticate with Azure AD much easier.

如果您選取 [個別使用者帳戶] 選項,則 ASP.NET 4.6 範本會示範如何使用 ASP.NET Identity 的雙因素驗證和社交登入。If you select the "Individual User Accounts" option, then the ASP.NET 4.6 templates show how to use two-factor authentication and social logins using ASP.NET Identity.

ASP.NET MVC 5.2.3、Web Pages 3.2.3 和 Web API 5.2。3ASP.NET MVC 5.2.3, Web Pages 3.2.3 and Web API 5.2.3

我們已更新範本套件,以使用適用于 MVC 5.2、網頁3.2 和 Web API 2.2 的最新執行時間封裝。We updated the template packages to use the latest runtime packages for MVC 5.2, Web Pages 3.2 and Web API 2.2. 如需這些套件更新的詳細資訊 ,請參閱 ASP.NET MVC 5.2.3、網頁3.2.3 和 WEB API 5.2.3 版本 blog 文章。For details on these packages updates see the ASP.NET MVC 5.2.3, Web Pages 3.2.3 and Web API 5.2.3 Release blog post.

ASP.NET Web API OData 5.3。1ASP.NET Web API OData 5.3.1

我們已更新 Web API OData scaffolder,以使用 ASP.NET Web OData 5.3.1。We updated the Web API OData scaffolders to use ASP.NET Web OData 5.3.1. 如需詳細資訊,請參閱 ASP.NET Web API OData 5.3 中的新功能For more information, see What's New in ASP.NET Web API OData 5.3.

SignalR 2.1。2SignalR 2.1.2

我們已更新範本套件,以使用 SignalR 2.1.2。We updated template packages to use SignalR 2.1.2. 請參閱 GitHub 上的 SignalR 版本 資訊。See the SignalR release note on GitHub.

Microsoft Owin 3.0 套件Microsoft Owin 3.0 package

我們已更新範本套件以使用 Microsoft Owin 3.0 NuGet 套件。We updated template packages to use Microsoft Owin 3.0 NuGet packages. 請參閱此 Katana 3.0 版本注意事項See this Katana 3.0 release note.

ASP.NET Identity 2.2。1ASP.NET Identity 2.2.1

ASP.NET Identity 2.2.1 有許多 bug 修正和效能改善超過2.1。ASP.NET Identity 2.2.1 has many bug fixes and performance improvements over 2.1. 如需詳細資料,請閱讀這 ASP.NET Identity 2.2.1 的 blog 文章。Read this ASP.NET Identity 2.2.1 blog post for more details.

ASP.NET 工具更新ASP.NET Tooling Updates

JSON 編輯器改善JSON Editor Improvements

我們對 JSON 編輯器進行了一些改良,包括效能改進,例如以非同步方式載入 JSON 架構、快取子架構,以及支援更佳的 IntelliSense。We have made some improvements in JSON editor, including performance improvements such as loading JSON schema asynchronously, caching of the child schemas, and supporting better IntelliSense. 此外,還提供下列新功能:Additionally, there are the following new features:

  • JSON 架構驗證。JSON Schema validation. 根據 [架構] 下拉式清單中定義的架構,加入 JSON 架構驗證功能。Add JSON schema validation feature, based on the schema that is defined in the schema drop-down list.
  • 未縮短的內容功能表。Un-minify context menu. 您可以在 JSON 編輯器上按一下滑鼠右鍵,然後選取 [取消縮短內容功能表],以在 JSON 檔案中取消縮短任何長陣列。You can right-click the JSON editor and select Un-minify context menu to un-minify any long arrays in the JSON file.
  • 重載架構內容功能表。Reload Schemas context menu. Visual Studio 將會快取從網際網路下載的架構,即使在重新開機 Visual Studio 之後也會使用快取。Visual Studio will cache the schema that is downloaded from Internet and will use the cache even after you restart Visual Studio. 如果您知道架構已變更,您可以使用內容功能表的 [重載架構] Ctrl + Shift + J,在使用中的 JSON 檔中重新下載目前使用的架構,然後立即在目前的檔上使用它。If you know the schema is changed, you can use the context menu Reload Schemas Ctrl+Shift+J to re-download the current used schema in the active JSON document, and then use it immediately on the current document.
  • package.json/bower.js的 IntelliSense。IntelliSense for package.json/bower.json. 除了證明檔案上 package.js和 bower.js的 IntelliSense 和驗證之外,Visual Studio 也會直接在 JSON 編輯器內提供 Bower 和 npm 套件的即時 IntelliSense。In addition to proving IntelliSense and validation for both package.json and bower.json files, Visual Studio also provides live IntelliSense for both Bower and npm packages directly within the JSON editor.
  • 重複的屬性驗證。Duplicate property validation. JSON 編輯器現在會提供任何重複屬性的驗證。The JSON editor will now provide validation for any duplicate properties. 這有助於攔截 JSON 檔案撰寫的常見問題。This helps catch a common problem with JSON file authoring.
  • 完整支援 JSON 架構草稿 v4 規格,大幅改善 IntelliSense 和 JSON 檔案驗證的支援。The support for both IntelliSense and validation of JSON files has been greatly improved by fully supporting the JSON Schema draft v4 specification. 現在更容易識別所需屬性,且編輯器可讓您輕鬆依字母順序排序屬性。Now it is much easier to identify required properties and the editor lets you easily sort the properties alphabetically. 格式化縮減的 JSON 檔案現在會自動取消縮短它。Formatting a minified JSON file will now automatically un-minify it.
  • 我們新增了對 SchemaStore.org 的支援,這是有用 JSON 架構檔案的開放原始碼集合。We added support for SchemaStore.org, an open source collection of useful JSON Schema files. 這表示,在 Visual Studio 中開啟的任何 JSON 檔案都有與 SchemaStore.org 相關聯的架構,會自動取得 IntelliSense 和驗證。This means that any JSON file opened in Visual Studio that has a schema associated on SchemaStore.org automatically gets IntelliSense and validation.
  • JSON 架構作者的支援已透過更佳的架構例行性驗證另外增強。The support for JSON Schema authors has additionally been enhanced by better schema sanity validation.

HTML 編輯器改善HTML Editor Improvements

HTML 編輯器已針對 web 標準更新 IntelliSense,並引進下列新功能:The HTML editor has updated IntelliSense for web standards and introduced the following new features:

  • 更佳的用戶端範本格式。Better client template formatting. HTML 編輯器不再剖析或格式化雙大括弧的語法 {{...}}。The HTML editor no longer parses or formats double-curly syntax {{…}}. 這是為了確定該語法的內容不會被視為 HTML,因此不會嘗試格式化內容,也無法使用 HTML 格式器正確完成。This is to make sure that the content of that syntax is not treated HTML and therefore invalidated, nor does it try to format the content, that cannot be done correctly by using the HTML formatter. 這很適合用於角度、Handlebars、Mustache 和其他雙大括弧範本語法。This is great for Angular, Handlebars, Mustache, and other double-curly template syntaxes.
  • 支援自訂元素、聚合體元素和屬性。Support for custom elements, polymer-elements and attributes. HTML 編輯器不再驗證自訂元素的未知屬性,因為不同的架構有許多自訂標記。The HTML Editor no longer validates unknown attributes for custom elements, because different frameworks have many custom tags. 未知的元素下將不再有波浪線。There will no longer be squiggles under the unknown elements.
  • Web 元件的基本 IntelliSense。Basic IntelliSense for Web Components. HTML 編輯器有 IntelliSense for < link rel = "import"/屬於 > Web 元件標準的一部分。The HTML Editor has IntelliSense for <link rel="import" /> that is part of the Web Components standard.
  • HTML 元素工具提示。HTML element tooltips. 編輯器中的 HTML 元素會提供工具提示。Tooltips are supplied for HTML elements in the editor.
  • #區域支援。#region support. HTML 編輯器現在支援區域折迭。The HTML editor now supports region folding. 您也可以使用周圍程式碼片段來圍繞目前的選取範圍。You can use the surrounding snippet to surround the current selection as well.
  • 工作清單中的 Todo/駭客批註支援。Todo/Hack comment support in the Task List.
  • 角度圖示。Angular icons. 這兩個角度指示詞 (例如Both Angular directives (ex. <<ng-view >) 和屬性 (例如<<ng-view>) and attributes (ex. ng 控制器) 現在會在 IntelliSense 中顯示具有角度標誌的標誌,讓您輕鬆識別它們。ng-controller) now shows in IntelliSense with an Angular logo to make it easy to identify them.
  • 啟動載入圖示。Bootstrap icons. HTML 類別屬性中提供的 IntelliSense 現在會顯示啟動載入標誌(如果啟動載入 CSS 檔案已定義類別名稱)。The IntelliSense provided in HTML class attributes now shows with the Bootstrap logo if the class name was defined by the Bootstrap CSS file.

CSS/LESS/Sass 編輯器改善CSS/LESS/Sass Editor Improvements

  • 工作清單中的 Todo/駭客批註支援。Todo/Hack comment support in the Task List.
  • @viewport 針對 LESS 編輯器進行修正。@viewport fix for the LESS editor. 在 LESS 編輯器中, @viewport 不再顯示驗證警告。In the LESS editor, @viewport no longer shows verification warnings.
  • 提供更多程式碼片段。Provide many more snippets. CSS/LESS/Sass 編輯器現在提供更多程式碼片段,讓您的開發體驗更輕鬆。The CSS/LESS/Sass editor now provides more snippets to make your developing experience easier.
  • 擴充功能現在可用於 Visual Studio 2015,以編譯 LESS、Scss 和 CoffeeScirpt。An extension is now available for Visual Studio 2015 to compile both LESS, Scss and CoffeeScirpt. 這裡下載。Download it here.

JSX 編輯器 ( # A0)JSX editor (React.js)

Visual Studio 現在支援 JSX 副檔名的 JSX 語法。Visual Studio now supports the JSX syntax of any files with the .jsx file extension. 當您輸入時,在編輯器中同時取得 IntelliSense、格式化與驗證。Get both IntelliSense, formatting and validation in the editor as you type. 此編輯器是與負責 React.js 程式庫的 Facebook 團隊合作建立的。This editor was built in collaboration with the Facebook team that is responsible for the React.js library.

瀏覽器連結Browser Link

CSS 會自動同步處理。CSS is automatically synchronized. 儲存 CSS 檔案或將它變更為外部 (例如,使用 LESS/SASS 編譯器) 會導致在瀏覽器中重載整個 CSS 檔案。Saving the CSS file or changing it externally (for example, by using a LESS/SASS compiler) causes the entire CSS file to reload in the browser. 如果無法自動同步檔案,Ctrl + S 會導致自動重載,而且應該使其回到良好的狀態,而不需要重新整理連結的瀏覽器 (Ctrl + Alt + Enter) 。If the file cannot auto-sync, Ctrl + S causes an automatic reload, and should put it back into a good state without having to refresh the linked browsers (Ctrl + Alt + Enter). 您可以在工具列中停用此功能。The feature can be disabled in the toolbar.

深入瞭解 ASP.NETLearn more about ASP.NET.

ASP.NET 5ASP.NET 5

ASP.NET 5 是一種精簡且可組合的 .NET 堆疊,可為雲端和內部部署伺服器建立現代化的 web 應用程式。ASP.NET 5 is a lean and composable .NET stack for building modern web applications for both cloud and on-premises servers. 其中包含下列功能:It includes the following features:

  • 新的輕量要求管線New light-weight request pipeline
  • 在 IIS 上執行,或自我裝載于您自己的進程中Run on IIS, or self-hosted in your own process
  • 建置於新的 .NET 執行環境 (DNX) ,可在完整 .NET Framework 或 .NET Core 上執行,這是支援真正並存版本控制的新雲端優化執行時間Built on new .NET Execution Environment (DNX) that can run on the full .NET Framework or on .NET Core, a new cloud-optimized runtime that supports true side-by-side versioning
  • 在 Windows、Mac 和 Linux 上跨平臺執行Runs cross-platform on Windows, Mac, and Linux
  • NuGet 一切,甚至是執行時間本身NuGet everything, even the runtime itself
  • 支援 ASP.NET MVC 6-適用于 Web UI 和 Web Api 的統一 Web 架構Supports ASP.NET MVC 6 - a unified Web framework for Web UI and Web APIs
  • 以環境為基礎的設定,可順暢地轉換至雲端Environment-based configuration for a seamless transition to the cloud
  • 現成的相依性插入Dependency injection out-of-the-box
  • 新的 Visual Studio 專案系統和高生產力工具體驗New Visual Studio project system and high productivity tooling experience
  • 透過 .NET Foundation 在 GitHub 上的所有開放原始碼All open source on GitHub through the .NET Foundation

Visual Studio 2015 包括 ASP.NET 5 Beta5 執行時間封裝。Visual Studio 2015 includes the ASP.NET 5 beta5 runtime packages. 這些套件仍處於預覽狀態,不建議用於生產環境。These packages are still in preview and not recommended for use in production. 您可以在 GitHub 上的 已發佈版本 資訊中,找到有關新增的特定增強功能和已修正之問題的所有詳細資料。You can find all the details on the specific enhancements added and issues fixed in the published release notes on GitHub.

Visual Studio 2015 隨附新的專案系統和整合式工具體驗,可用於建立 ASP.NET 5 應用程式和使用 DNX 專案。Visual Studio 2015 comes with a new project system and integrated tooling experience for building ASP.NET 5 applications and for working with DNX projects. 其中一些新的工具功能包括:Some of the new tooling features include:

  • 新的專案系統,用於建立在 Windows、Mac 和 Linux 上建立及執行的跨平臺 DNX 專案。New project system for creating cross-platform DNX based projects that are built and run on Windows, Mac, and Linux.
  • 使用 MVC 6、Identity 3 和 Entity Framework 7 建立 ASP.NET 5 網站及 Web Api 的範本。Templates for creating ASP.NET 5 Web Sites and Web APIs using MVC 6, Identity 3, and Entity Framework 7.
  • 用來建立以 DNX 為基礎的類別庫和主控台應用程式的範本Templates for creating DNX based class libraries and console applications
  • 透過 NuGet 建立及散發跨平臺命令列工具。Create and distribute cross-platform command-line tools through NuGet.
  • 使用 .NET 版本管理員 (DNVM) 從開發人員命令提示字元安裝及管理不同的 DNX 版本。Install and manage different DNX versions using the .NET Version Manager (DNVM) from the Developer Command Prompt.
  • 尋找、安裝及還原 NuGet 套件的整合體驗。Integrated experience for finding, installing, and restoring NuGet packages.
  • 使用 CTRL +。Use CTRL + . 針對 c # 程式碼中無法解析的符號尋找並安裝 NuGet 套件。to find and install NuGet packages for unresolved symbols in your C# code.
  • 使用 NPM、Grunt/Gulp 和 Bower 的用戶端 Web 開發整合式工具,包括套件管理整合及新的工作執行器瀏覽器。Integrated tooling for client-side Web development using NPM, Grunt/Gulp, and Bower, including package management integration and the new Task Runner Explorer.
  • 使用 [執行] 按鈕下拉式功能表,直接從 Visual Studio 內執行專案層級的 DNX 命令。Run project level DNX commands directly from within Visual Studio by using the Run button dropdown menu.
  • 建立啟動 IIS Express 的自訂啟動設定檔,包括自訂環境變數的設定。Create custom launch profiles that launch IIS Express, including setting of custom environment variables.
  • 從以多個架構(包括 .NET Core)為目標的單一專案建立 NuGet 套件。Build NuGet packages from a single project that target multiple frameworks including .NET Core.
  • 從單一專案建立多個目標 framework 時,結合了 IntelliSense。Combined IntelliSense when building for multiple target frameworks from a single project.
  • ASP.NET 5 引進的新 Razor 功能(例如標籤協助程式),現在會在 IntelliSense 和語法醒目提示中亮起。New Razor features introduced by ASP.NET 5, such as Tag Helpers, now light up in both IntelliSense and syntax highlighting.

本版次中的新功能New features in this release

  • 當您開啟的專案需要的 DNX 版本無法使用時 Visual Studio 會提示您安裝所需的 DNX 版本。When you open a project that requires a version of DNX that is not available Visual Studio will prompt to install the required DNX version.
  • 您現在可以使用 [加入參考] 對話方塊,加入參考以失去元件。You can now add references to lose assemblies using the Add Reference dialog.
  • ASP.NET 5 Web 應用程式範本現在支援工作和學校帳戶選項以進行驗證。The ASP.NET 5 Web Application template now supports the Work and School Accounts option for authentication.
  • [新增 ASP.NET 專案] 對話方塊中的 [裝載于雲端] 選項現在適用于 ASP.NET 5 個專案。The Host in Cloud option in the New ASP.NET Project dialog is now available for ASP.NET 5 projects.
  • 使用伺服器總管針對裝載于 Azure 上的 ASP.NET 5 個專案,對 approot 下的檔案進行遠端編輯。Use the Server Explorer to do remote editing of files under approot for ASP.NET 5 projects hosted on Azure.

如需其他詳細資訊,請參閱 GitHub 上的 工具版本 資訊,以及我們的 .net Web 開發和工具的 BlogFor additional details, see the tooling release notes on GitHub, and our .NET Web Development and Tools Blog.

Azure 工具 Azure Tooling

帳戶選擇器整合Account Picker integration

帳戶選擇器會在 Web 發行和 Web 應用程式建立/選取對話方塊中使用,以啟用對多個帳戶的單鍵存取。The Account Picker is used throughout the Web Publishing and Web App creation/selection dialogs, to enable one-click access to multiple accounts. 您可以登入多個帳戶,並在發佈資源時輕鬆快速地存取選取個別帳戶。You can log in once to multiple accounts, and have quick and easy access to select individual accounts as you publish resources.

API AppsAPI Apps

API Apps 預覽範本、發佈支援和伺服器總管可見度都已遷移至 Visual Studio 2015。The API Apps preview template, publishing support, and Server Explorer visibility have all been migrated to Visual Studio 2015. 現在您可以使用最新版本的 Visual Studio 來建立和部署 Azure API Apps。Now you can create and deploy Azure API Apps using the latest version of Visual Studio. 此外,我們也改進了 Swagger 輸出功能,讓 API 應用程式開發人員有更好的現成支援,可從 ASP.NET Web API 動態產生 Swagger。In addition, we improved the Swagger output functionality so that API app developers have better out-of-the-box support for dynamically generated Swagger from ASP.NET Web API.

Webjob 工具WebJobs Tooling

您現在可以透過下列方式,在 Azure 網站內的伺服器總管 WebJob 節點上控制 web 工作:You can now control web jobs on the Server Explorer WebJob node inside an Azure Website in the following ways:

  • 伺服器總管中網站節點下方的 Webjob 節點。WebJobs nodes underneath Website nodes in Server Explorer.
  • 從伺服器總管啟動/停止持續 Webjob。Start/Stop Continuous WebJobs from Server Explorer.
  • 從伺服器總管執行隨選或排程工作。Run On-demand or Scheduled jobs from Server Explorer.
  • 從伺服器總管查看 WebJob 儀表板。View WebJob Dashboard from Server Explorer.
  • [View 儀表板] 內容功能表;您可以使用它來移至 Azure 網站的 WebJob 儀表板。The View Dashboard context menu; use it to go to the Azure website's WebJob dashboard.

WebJobs SDKWebJobs SDK

Azure WebJob 專案範本已預先安裝 Webjob SDK。Azure WebJob project templates have the WebJobs SDK pre-installed.

NuGet NuGet

NuGet 2.8.3NuGet 2.8.3

我們已新增對獲得 devextreme 專案和 BizTalkProject 2.8.3 的支援。We added support for DevExtreme project and BizTalkProject 2.8.3. 如需詳細資訊,請參閱 NuGet 2.8.3 版本資訊。For detailed information, see NuGet 2.8.3 release notes.

NuGet 套件管理員NuGet Package Manager

我們更新了 NuGet 套件管理員使用者介面,讓您可以更輕鬆地在 Visual Studio 2015 的整個解決方案中管理套件。We updated the NuGet Package Manger user interface to provide easier management of packages across an entire solution in Visual Studio 2015. 透過單一視圖,在您的專案中安裝套件,您可以從 NuGet 元件庫、已安裝的套件,以及有可用更新的套件,篩選可用套件的清單。With a single view across packages installed in your projects, you can filter the list of available packages from the NuGet gallery, your installed packages, and the packages that have updates available.

NuGet 資源庫NuGet Gallery

我們使用新的 web 服務和整合式用戶端來改善 NuGet 資源庫的效能。We improved performance of the NuGet gallery with a new web service and integrated client. 如需 NuGet 更新的詳細資訊,請參閱 http://docs.nuget.orgMore details about NuGet updates can be found at http://docs.nuget.org.

JavaScript JavaScript

JavaScript 編輯器支援JavaScript Editor Support

我們更新了 JavaScript 編輯器,讓它更加實用。We updated the JavaScript editor to make it even more useful.

  • AngularJS 的工具支援Tooling support for AngularJS. 現在,當您使用 AngularJS 撰寫應用程式時,IntelliSense 會提供角度控制器、服務、處理站、指示詞及動畫的建議。Now, when you are writing apps using AngularJS, IntelliSense provides suggestions for Angular controllers, services, factories, directives, and animations.
  • 支援從 ES6 版本的 JavaScript) (新的 javascript 語言功能,包括類別、箭號函式及範本字串。New JavaScript language features (from the ES6 version of JavaScript) are supported, including classes, arrow functions, and template strings.
  • Nav bar 共用專案支援Nav bar shared project support. 您現在可以在適用于 Windows 通用應用程式專案的共用專案中使用巡覽列。You can now use the navigation bar in the Shared project for Windows Universal App projects.
  • 新巡覽列New navigation bar. 新的導覽列可讓您更輕鬆地在 JavaScript 原始程式碼的主要元素之間流覽。The new navigation bar makes it easier to navigate between major elements in JavaScript source code.
  • JSDoc 批註JSDoc comments. 使用 IntelliSense 時,現在會顯示以 JSDoc 格式撰寫的檔批註。Documentation comments written in the JSDoc format are now shown when using IntelliSense. (如需 JSDoc 批註的詳細資訊,請參閱 http://usejsdoc.org 。 ) (For more information about JSDoc comments, see http://usejsdoc.org.)
  • 物件常值 IntelliSenseObject literal IntelliSense. 當您將物件常值傳遞給使用 JSDoc 記載的函式時,JavaScript 編輯器會提供您 IntelliSense 的建議。The JavaScript editor provides you with IntelliSense suggestions when passing an object literal to functions documented using JSDoc.
  • 展開/ 折迭。Expand/collapse. 您可以展開和折迭 JavaScript 程式碼的更多區段,包括多行批註、多行陣列及所有多行區塊。You can expand and collapse more sections of your JavaScript code, including multi-line comments, multi-line arrays, and all multi-line blocks.
  • 工作清單支援Task List support. 您可以使用工作清單功能,在您的 JavaScript 程式碼中檢查工作批註,例如//TODO。You can use the Task List feature to review task comments, such as // TODO, in your JavaScript code.

TypeScript TypeScript

Visual Studio 2015 包含 TypeScript 工具的 1.5 版本Visual Studio 2015 includes the 1.5 release of the TypeScript tools. 此版本為 ECMAScript 6 新增了豐富的支援,包括模組、解構,以及。、散佈、符號、計算屬性、let/const for ES3/ES5 和 ES3/ES5 的標記字串範本。This release adds rich support for ECMAScript 6, including modules, destructuring, for..of, spread, symbols, computed properties, let/const for ES3/ES5, and tagged string templates for ES3/ES5. 除了支援 ES6 之外,TypeScript 1.5 也新增了實驗性 ES7 裝飾提案提案、UMD 和 System.js 模組輸出的支援,以及新的輕量、可攜的專案檔,稱為「tsconfig.js開啟」。In addition to the support for ES6, TypeScript 1.5 also adds support for the experimental ES7 decorator proposal, UMD and System.js module outputs, and a new lightweight, portable project file called "tsconfig.json".

IntelliTest IntelliTest

在 Visual Studio 2015 中,我們新增了 IntelliTest 來探索您的 .NET 程式碼,以產生測試資料和單元測試套件。In Visual Studio 2015, we added IntelliTest that explores your .NET code to generate test data and a suite of unit tests. 其會為程式碼中的每一個陳述式產生一個用以執行該陳述式的測試輸入。For every statement in the code, a test input is generated that will execute that statement. 程式碼的每個條件分支都會執行大小寫分析。A case analysis is performed for every conditional branch in the code. 例如,For example,

所有可擲回例外狀況的作業(例如,如果語句和判斷提示)都會進行分析。All operations that can throw exception, such as, if statements and assertions, are analyzed. 這項分析會用於為每個方法的參數型單元測試產生測試資料,從而建立盡可能能夠涵括所有程式碼的單元測試。This analysis is used to generate test data for a parameterized unit test for each of your methods, creating unit tests with maximum code coverage. 您可以發揮您的專業知識來改良這些單元測試。Then you bring your domain knowledge to improve these unit tests.

我們也將下列功能新增至 IntelliTest:We also added the following functionality to IntelliTest:

  • 參數化單元測試Parameterized Unit Tests. IntelliTest 啟用 API 的支援,您可以使用此 API 來引導測試資料產生、指定受測程式碼的正確性屬性,以及直接探索受測程式碼。IntelliTest enables support for an API that you can use to guide test data generation, specify correctness properties of the code under test, and direct the exploration of the code under test. 這個 API 可在 Pex 命名空間中使用,並可用於測試方法 (參數化單元測試,) 由 IntelliTest 所產生的 factory 方法。This API is available in the Microsoft.Pex.Framework namespace and can be used in the test methods (parameterized unit tests, factory methods) generated by IntelliTest. 因此,現在也可以從產生的測試方法中使用 "IntelliTest" 內容功能表命令。Consequently, the "IntelliTest" context menu command is now available from the generated test methods as well.
  • 建立建立存根的測試Test stubs creation. [建立單元測試] 現在可以在內容功能表上提供,做為可讓您建立及設定測試專案、測試類別和測試存根的命令。"Create Unit Tests" is now available on the context menu as a command that provides the ability to create and configure a test project, a test class, and a test stub.

如需 IntelliTest (先前稱為「智慧型單元測試」 ) 的詳細資訊,請參閱 使用 IntelliTest 為您的程式碼產生單元測試For more information about IntelliTest (formerly known as "Smart Unit Tests"), see Generate unit tests for your code with IntelliTest.

Application Insights Application Insights

除了各種效能增強功能和 bug 修正之外,Application Insights 現在還包含下列更新:Along with various performance enhancements and bug fixes, Application Insights now includes the following updates:

  • Visual Studio 中的 Application Insights 工具現在是 Visual Studio 已連線的服務的一部分。Application Insights tools in Visual Studio is now part of Visual Studio Connected Services. (若要新增 Application Insights,請開啟已連線的服務對話方塊,然後從服務清單中選擇 [Application Insights]。 ) (To add Application Insights, open the Connected Services dialog and choose Application Insights from the list of services.)
  • 此更新與已在 Visual Studio 2013 Update 3 或 Visual Studio 2013 Update 4 中新增 Application Insights 的專案完全相容。This update is fully compatible with projects that had Application Insights added in Visual Studio 2013 Update 3 or in Visual Studio 2013 Update 4.
  • ASP.NET 5 名開發人員、Windows 10 通用應用程式開發人員,以及 Windows 8.1 通用應用程式開發人員可以直接從 Visual Studio 將 Application Insights 新增至其專案。ASP.NET 5 developers, Windows 10 Universal Apps developers, and Windows 8.1 Universal Apps developers can add Application Insights to their projects right from Visual Studio.
  • Windows 10 通用應用程式開發人員不需要登入 Azure,即可新增 Application Insights SDK;相反地,他們可以使用 Visual Studio 中的 Application Insights 工具加以新增。Windows 10 Universal Apps developers do not have to be signed in to Azure to add the Application Insights SDK; instead, they can add it by using the Application Insights tools in Visual Studio.
  • 由於 Application Insights 使用 Visual Studio 中的通用帳戶選擇器,因此您可以在 Visual Studio 間使用相同的帳戶。Because Application Insights uses the global account picker in Visual Studio, you can use the same account across Visual Studio.
  • 現在您可以從專案的 [服務參考] 資料夾中,直接查看 Application Insights 的「使用者入門」資訊;只要按一下消費者入門資料夾即可。Now you can view "getting started" information for Application Insights right from the Project's Service Reference folder; simply click the Getting Started folder.

從專案的 [服務參考] 資料夾中,查看 Application Insights 的消費者入門資訊。

Release Management Release Management

您可以使用這項功能來改善管理應用程式發行的程式、將應用程式部署到每個不同階段的特定環境,以及管理程式中的步驟,並針對每個步驟進行核准。With this feature, you can improve the process of managing the release of your app, deploy your app to a specific environment for each separate stage, and manage the steps in the process with approvals for each step. 您可以設定從簽入到部署的發行管線,而不需要使用 Release Management 服務來安裝和維護內部部署 release management 伺服器,以進行 Visual Studio Online。You can set up a release pipeline from check-in through to deployment without having to install and maintain an on-premises release management server using the Release Management service for Visual Studio Online.

Release Management 的更新版本適用于 Visual Studio 2015。An updated version of Release Management is available for Visual Studio 2015. 這與現有的 Visual Studio Release Management 2013 非常類似,但在下列領域中提供改善的效能:This is very similar to the existing Release Management for Visual Studio 2013, but provides improved performance in the following areas:

  • 發行管理用戶端啟動頁面,其中顯示發行程式和通知的總覽。The release management client launch page that shows an overview of the release process and notifications.
  • 透過其他快取,在其他 release management 用戶端頁面中轉譯和互動。Rendering and interactivity in other release management client pages, through additional caching.
  • Active Directory 和 TFS 安全性群組的同步處理。Synchronization of Active Directory and TFS security groups.
  • 建立新版本。Creation of new releases.

您現在可以針對 Team Foundation Server 2015 中包含的新組建系統,定義組建定義的元件和發行定義。You can now define components and release definitions for build definitions of the new build system included in Team Foundation Server 2015. 在定義元件時,您也可以使用與 (相同的元件名稱來指定元件的成品,或在組建定義中包含) 已發佈成品名稱的專案。While defining the component, you can also specify the artifact for the component by using a component name that is same as (or contains) the name of the published artifact from the build definition.

如需發行管理的詳細資訊,請參閱 持續整合和傳遞For more information about release management, see Continuous Integration and Delivery.

Git 版本控制 Git version control

您可以更輕鬆地使用分支,並查看歷程記錄分歧中的變更。It is easier to work with branches and see how the changes in your history diverged.

分支Branches

您可以藉由指定前置詞,以階層方式組織您的分支:You can organize your branches hierarchically by specifying a prefix:

本機分支和遠端分支 (包括您尚未在本機建立的分支) 會分別顯示在樹狀檢視中。Local branches and remote branches (including those you have not created locally) are shown separately in a tree view.

Git 分支

在 RC 中,我們已修改 [分支] 頁面:And as of RC, we reworked the Branches page:

  • 您現在可以從遠端分支及本機分支合併。You can now merge from remote branches, as well as local branches.
  • 您正在合併的分支現在已固定到目前簽出的分支。The branch that you are merging into is now fixed to the branch that is currently checked out.
  • 您現在可以從最新分支到任何本機或遠端分支進行重定基底。You can now rebase from the current branch onto any local or remote branch.
  • 您可以按兩下遠端分支,或以滑鼠右鍵按一下它,然後選取 [簽出],以簽出遠端分支。You can checkout a remote branch by double-clicking it, or right-clicking it and then selecting Checkout.

遠端系統管理Remotes management

您現在可以在 Team Explorer 中設定您的 Git 遠端。You can now configure your Git remotes in Team Explorer. 在 [存放庫設定] 中,有一個新的 [遠端] 區段會顯示目前設定的遠端,您可以在其中新增、編輯或移除遠端。In Repository Settings, there is a new Remotes section that shows the currently configured remotes where you can add, edit, or remove remotes. 例如,如果您需要變更原始遠端的 URL,您可以按一下 [編輯],然後變更提取和/或推送 URL。For example, if you need to change the URL of the origin remote, you can click Edit and change the fetch and/or push URL.

詳細歷程記錄Detailed history

您現在可以在歷程記錄中看到認可分歧的方式。You can now see how commits diverged in the history.

歷程記錄的詳細觀點

在圖形中,合併認可是灰色,而非合併認可則是較亮的色彩。In the graph, merge commits are gray and non-merge commits are a brighter color. 您可以在簡單視圖和詳細觀點之間來回切換。You can switch back and forth between the simple view and the detailed view. 如果已截斷圖形,您可以調整其大小。If the graph is truncated, you can resize it.

我們對 RC 版本中的歷程記錄圖表進行了幾項更新:We made several updates to the History graph in the RC release:

  • 我們新增了工具列,可讓您控制在圖形中看到的詳細資料層級。We added a toolbar that allows you to control the level of detail that you see in the graph.
  • 我們現在會反白顯示歷程記錄行,以指出哪些認可哥從目前選取的認可連線。We now highlight history lines to indicate which commits are reachable from the currently selected commit.
  • 如果本機和遠端分支不同,我們現在會顯示這兩行歷程記錄。We now show both lines of history if the local and remote branch differ. 這在重定基底本機分支之後特別有用。This is especially useful after rebasing a local branch.

Team Explorer 中的重定基底Rebase in Team Explorer

我們現在支援 Team Explorer 中的重定基底。We now support rebase in Team Explorer. 若要起始重訂基底,請按一下 [分支] 頁面上的重定基底飛出視窗,或以滑鼠右鍵按一下分支,然後選取 [重定基底到 ...]。To initiate a rebase, click on the rebase flyout on the Branches page, or right click on a branch and select "Rebase Onto..."

VSO 儲存機制VSO repositories

我們已改善建立 VSO 存放庫時的「開始使用」體驗,而且有更多變更可簡化建立新存放庫的程式。We improved the "getting started" experience when creating a VSO Repo, and there are a lot more changes coming to streamline the creation of a new repo. 針對 RC,我們進行了少許變更,讓您更輕鬆地將新的程式碼新增至現有的存放庫:如果您使用 Team Explorer 連線到任何存放庫,然後選取 [檔案 > 新增專案],對話方塊就會從該連線存放庫的根目錄開始。For RC, we made a small change to make it easier to add new code to an existing repo: If you connect to any repo using Team Explorer, then select File > New Project, the dialog will now start out in the root of that connected repo.

發佈至 Visual Studio OnlinePublish to Visual Studio Online

[發佈至 Visual Studio 線上] 功能大幅簡化了將本機儲存機制放到 Visual Studio Online 的流程。The Publish to Visual Studio Online feature dramatically simplifies the process of getting your local repository onto Visual Studio Online. 過去12個步驟的工作,現在需要2個。What used to take 12 steps now takes 2. 在 [Team Explorer 同步] 頁面中,新的 [發佈至 Visual Studio 線上] 區段可讓您選取 [Visual Studio 帳戶管理員] 中的任何使用者帳戶。From the Team Explorer Sync page, the new Publish to Visual Studio Online section lets you select any of the user accounts in the Visual Studio account manager. 您的 Visual Studio 線上帳戶會自動在清單中提供;不需要記住 Url。Your Visual Studio online accounts are automatically available in a list; there is no need to remember URLs. 當您準備要共用程式碼時,只要挑選新的或現有的 team 專案來裝載您的儲存機制,然後按一下 [發佈] 就大功告成了。When you are ready to share your code, simply pick a new or existing team project to host your repository, click publish, and you're done.

[發行至 Visual Studio Online] 對話方塊

單一登入 Single sign-in

您與現今許多其他開發人員一樣,在開發您的應用程式時,會利用多個雲端服務。You, like many other developers today, take advantage of multiple cloud services when developing your applications. 例如,您可能已將雲端後端新增至您的應用程式,以儲存資料、將原始程式碼儲存在雲端,或將應用程式發佈至存放區。For example, you probably have added a cloud backend to your applications to store data, stored your source code in the cloud, or published an application to a store.

在過去,每個服務都需要個別的登入程式,而且每個服務會分別管理已登入的使用者狀態。In the past, each of these services required a separate sign-in process, and each service managed the signed-in user state separately.

在此版本中,我們將減少存取 Visual Studio 中許多整合式雲端服務所需的驗證提示。With this release, we are reducing the authentication prompts required to access many integrated cloud services in Visual Studio. 現在,當您驗證 Visual Studio 中的第一個雲端服務時,我們會自動將您登入,或減少其他整合式雲端服務的驗證提示。Now, when you authenticate to the first cloud service in Visual Studio, we will automatically sign you in, or reduce the authentication prompts for other integrated cloud services.

CodeLens CodeLens

深入瞭解您的程式碼,並將焦點放在編輯器中的工作。Find out more about your code, while staying focused on your work in the editor. 尋找程式碼參考、程式碼變更、相關 TFS 專案和單元測試-全都不需要離開程式碼。Find code references, changes to your code, related TFS items, and unit tests – all without looking away from the code.

在此版本中,我們已將 CodeLens 「作者」指標取代為新的「小組啟用時間軸」和「作者與變更」歷程記錄指示器。In this release, we have replaced the CodeLens "Authors" indicators with the new "Team Activity Timeline" and "Authors and Changes" history indicators.

  • 小組啟用時間軸 指標會顯示最後的作者,以及上次進行變更的時間。The Team Activity Timeline indicator shows the last author, and when the last change was made. 選擇此指標會開啟 [ Team 活動 View],您可以在其中尋找程式碼變更的模式。Choosing this indicator opens Team Activity View, where you can look for patterns in changes to the code. 這可協助您評估變更一段時間的影響。This can help you to assess the impact of changes over time.
  • 作者和變更 指標會顯示已變更檔案的作者人數和變更數目。The Authors and Changes indicator shows the number of authors that have changed the file, and the number of changes. 選擇此指標會開啟所有變更的清單、變更的詳細資料,以及取得詳細資訊的連結,並查看先前的版本。Choosing this indicator opens a list of all the changes, details of the changes, and links to get more information and see the previous versions.

當您的程式碼裝載于 Team Foundation Server 和 Visual Studio Online) 和 Git 存放庫中的 Team Foundation 版本控制 (時,指標的所有資訊都可供使用。All the information from the indicators is available when your code is hosted in Team Foundation Version Control (in both Team Foundation Server and Visual Studio Online) and in Git repositories. 當您在 Team Foundation Server 或 Visual Studio Online 工作時,也可以取得工作專案的相關資訊。When you are working in Team Foundation Server or Visual Studio Online, you can also get information about work items.

這些指標和先前版本中可用的指標,會顯示在 c # 和 Visual Basic 檔案的程式碼元素 (方法、欄位或類別) 層級。These indicators, together with the indicators available in previous versions, are displayed at the code element (method, field, or class) level for C# and Visual Basic files. 以下是 c # 檔案的「小組啟用時間軸」指標範例:The following is an example of the Team Activity Timeline indicator for a C# file:

C # 檔案的「小組啟用時間軸」指標

以下是 c # 檔案的作者和變更指標範例:The following is an example of the Authors and Changes indicator for a C# file:

C # 檔案的「作者與變更」指標

不過,指標現在會顯示在所有其他檔案類型的檔案層級 (例如,c + +、SQL、JavaScript 和其他類型的檔) 。However, the indicators are now displayed at file level for all other types of files (for example, C++, SQL, JavaScript, and other types of files). 以下是非 c # 或 Visual Basic 程式碼檔案的「Team 啟用時間軸」指標範例:The following is an example of the Team Activity Timeline indicator for a file that is not a C# or Visual Basic code file:

非 c # 或 Visual Basic 程式碼檔案之檔案的「小組啟用時間軸」指標

架構、設計與模型化 Architecture, Design, and Modeling

Code Map 和相依性圖形Code maps and dependency graphs

當您想要瞭解程式碼中的特定相依性時,請建立 code map 將其視覺化。When you want to understand specific dependencies in your code, visualize them by creating code maps. 然後,您可以使用出現在您程式碼旁邊的對應來流覽這些關聯性。You can then navigate these relationships by using the map that appears next to your code. Code map 也可在工作或偵錯工具代碼時,協助您追蹤程式碼中的位置,如此一來,當您深入瞭解程式碼的設計時,就會讀取較少的程式碼。Code maps can also help you keep track of your place in the code while you work or debug code, so you will read less code while you learn more about your code's design.

在最終的 RTM 版本中,我們讓程式碼專案和連結的快捷方式功能表更容易使用,方法是將命令組成與選取、編輯、管理群組,以及變更群組內容版面配置相關的區段。In the final RTM release, we made the shortcut menus for code elements and links much easier to use by grouping commands into sections related to selecting, editing, managing groups, and changing the layout of group contents. 另外也請注意,測試專案會以與其他專案不同的樣式來顯示,而我們將地圖上元素的圖示更新為更適當的版本。Notice also that test projects display in a different style from other projects and that we updated the icons for elements on the map to more appropriate versions.

Code map 中的新群組

我們也變更了程式碼專案內容的顯示方式,因此您現在可以選取一個以上的群組,並將您想要的版面配置樣式套用至所有群組。We also changed the way that contents of code elements are displayed, so you can now select more than one group and apply the layout style you want to all of them. 現在,當您展開元件、命名空間或 code map 上的型別時,您一律可以取得實用的相依性圖表。Now, you can always get a useful dependency diagram when you expand an assembly, a namespace, or a type on a code map.

選取多個群組,並在 Code Map 中套用一個版面配置

在舊版的 Visual Studio 2015 的預覽和發行候選版本中,我們進行了一些變更,讓您能夠:In the earlier preview and release candidate versions of Visual Studio 2015, we made changes that allow you to:

  • 取得改良的由上而下圖表Get improved top-down diagrams. 針對中大型 Visual Studio 方案,您現在可以使用簡化的 [架構] 功能表,取得對方案更實用的 Code Map。For medium to large Visual Studio solutions, you can now use a simplified Architecture menu to get a more useful code maps for your solution. 您解決方案的元件會依方案資料夾分組,因此您可以在內容中看到這些元件,並利用您放置於結構化解決方案的工作。The assemblies of your solution are grouped by the solution folders, so you can see them in context and leverage the effort you have put in structuring the solution. 您會立即看到專案和元件參考,然後顯示連結類型。You will immediately see project and assembly references, and then the link types appear. 此外,方案的外部組件也會以更精簡的方式分組。In addition, the assemblies external to your solution are grouped in a more compact way.
  • 更快取得反應靈敏的 Code MapGet reactive code maps more quickly. 拖放作業會產生立即的結果,而節點之間的連結會更快速地建立,而不會影響後續使用者起始的作業,例如展開節點或要求更多節點。Drag and drop operations produce an immediate result and the links between nodes are created more quickly, without affecting subsequent user-initiated operations such as expanding a node or requesting more nodes. 尤其是,[略過重建方案] 選項可讓您在建立及編輯圖表時獲得更好的效能。In particular, the "Skip rebuilding your solution" option lets you get better performance when creating and editing diagrams. 當您建立 code map 但未建立方案時,現在會處理所有的角落案例,例如非建立的元件。When you create code maps without building the solution, all the corner cases, such as non-built assemblies, are now processed.
  • 篩選程式碼項目節點和群組Filter code element nodes and groups. 您可以根據程式碼項目的類別來顯示或隱藏程式碼項目,也可以依照方案資料夾、組件、命名空間、專案資料夾和類型分組程式碼項目,以快速地整理對應。You can quickly unclutter your maps by showing or hiding code elements based on their category, as well as by grouping code elements by solution folders, assemblies, namespaces, project folders, and types.
  • 篩選關聯性以更容易閱讀圖表Filter relationships to make diagrams easier to read. 這包括跨群組連結,讓使用篩選視窗的侵入性比舊版低。This includes cross group links, which makes working with the filter window less intrusive than it was in previous releases.
  • 「向內切入相依性連結」會將篩選納入考量'Drill-in into dependency links' takes filters into account. 當您展開以了解相依性連結的比重時,可以獲得一目暸然的實用圖表。You get a useful, clear diagram when expanding it to understand the contributions to a dependency link. 此圖表比較不整齊,而且會將您選取的連結篩選選項列入考慮。The diagram is less cluttered, and it takes into account the link filtering options you selected.
  • 從類別檢視和物件瀏覽器建立圖表Create diagrams from the Class View and Object Browser. 將檔案和組件從類別檢視和物件瀏覽器拖放到新的或現有的對應中。Drag and drop files and assemblies into a new or an existing map from the Class View and Object Browser windows.

總而言之,我們對 code map 所做的完整改良清單包括:Overall, the comprehensive list of improvements we made to code maps includes:

  • 測試專案已有不同的樣式並可篩選Test Projects are styled differently and can be filtered. 您現在可以快速識別地圖上的測試專案,因為它們的樣式不同。You can now quickly identify test projects on a map because they are styled differently. 此外,您可以將它們篩選掉,以便將焦點放在應用程式的工作程式碼上。Additionally, they can be filtered out so that you can focus on the application's working code.
  • 程式 代碼專案會連同其內容一起加入Code elements are added with their context. 因為圖表現在會顯示其內容 (到您可以視) 需要篩選出的元件和方案資料夾,所以您可以從方案總管、類別檢視和物件瀏覽器拖放程式碼專案,以取得更有用的圖表;或選取方案總管中的專案,然後選擇 [在 Code Map 上顯示]。Because diagrams now appear with their context (up to the assembly and solution folder that you can filter out if required), you get more useful diagrams when dragging and dropping code elements from Solution Explorer, Class View, and Object Browser; or when selecting elements in Solution Explorer and choosing Show on Code Map.
  • 簡化外部相依性連結Simplified external dependency links. 相依性連結不再繼承自 System.Object、System.ValueType、System.Enum 和 System.Delegate,因此您可以在 Code Map 中更輕鬆地查看外部相依性。Dependency links no longer represent the inheritance from System.Object, System.ValueType, System.Enum, and System.Delegate, which makes it easier to see external dependencies in your code map.

此版本中的其他設計和模型變更Other design and modeling changes in this release:

  • 圖層圖表Layer diagrams. 使用類別檢視和物件瀏覽器來更新這些圖表。Update these diagrams using the Class View and Object Browser. 為了達到軟體設計需求,請使用分層圖來描述軟體所需的相依性。To meet software design requirements, use layer diagrams to describe the desired dependencies for your software. 尋找不符合這些條件約束的程式碼,並使用這個基準來驗證未來的程式碼,讓程式碼與這個設計保持一致。Keep code consistent with this design by finding code that does not meet these constraints and validating future code with this baseline.
  • UML 圖表UML diagrams. 您已無法再從程式碼建立 UML 類別圖和循序圖。You can no longer create UML class diagrams and sequence diagrams from code. 不過,您還是可以使用新的 UML 元素來建立這些圖表。However, you can still create these diagrams using new UML elements.
  • 架構瀏覽器Architecture Explorer. 您已無法再使用架構總管來建立圖表。You can no longer use Architecture Explorer to create diagrams. 不過,您仍然可以使用方案總管。However, you can still use Solution Explorer.

XAML 語言服務 XAML Language Service

我們已在 .NET Compiler Platform ( "Roslyn" ) 上重建 XAML 語言服務,讓我們可以為您提供快速、可靠且現代化的 XAML 編輯體驗,其中包含 IntelliSense。We rebuilt the XAML language service on top of .NET Compiler Platform ("Roslyn") so that we can provide you with a fast, reliable, and modern XAML editing experience that includes IntelliSense.

這使得 XAML 編寫體驗等於 Visual Studio 中的其他第一級語言。This makes the XAML authoring experience equal to other first-class languages in Visual Studio. 我們也會以更快的速度提供跨語言重構的強大功能集。We will also deliver powerful feature sets around cross-language refactoring to you at a much faster cadence.

其他 Miscellaneous

Visual Studio 2015 的代理程式不再需要測試控制器Agents for Visual Studio 2015 no longer require a Test Controller

在 Visual Studio 2015 的代理程式中,您不需要個別的測試控制器,因為代理程式可以透過與 TFS 2015 或線上 Visual Studio 進行通訊來處理協調流程。In Agents for Visual Studio 2015, you do not need a separate test controller because the agents can handle the orchestration by communicating with TFS 2015 or Visual Studio Online.

在所有新的 Visual Studio 2015 和 TFS 2015 案例中,我們建議您將代理程式用於 Visual Studio 2015。In all the new Visual Studio 2015 and TFS 2015 scenarios, we recommend that you use Agents for Visual Studio 2015.

但是,如果您需要測試代理程式或測試控制器才能使用 TFS 2013,建議您將代理程式用於 Visual Studio 2013 Update 5 並設定測試控制器。However, if you do need the Test Agent or Test Controller to work with TFS 2013, we recommend that you use Agents for Visual Studio 2013 Update 5 and configure the Test Controller.

測試控制器與 TFS 2015 以及 TFS 2013 相容。The Test Controller is compatible with TFS 2015 as well as TFS 2013. 不過,Visual Studio 2015 中的負載測試支援並非代理程式的一部分,因此我們建議您安裝 Visual Studio 2013 Update 5 的代理程式,並設定控制器。However, Load Testing support in Visual Studio 2015 is not part of the agents, hence our recommendation that you install Agents for Visual Studio 2013 Update 5 and configure the controller.

已連線的服務Connected Services

Visual Studio 2015 中新增的 [加入已連接服務] 對話方塊可讓您輕鬆地將應用程式連接到 Azure 應用程式 InsightsAzure 儲存體Azure 行動服務、Office 365 和 Salesforce。The new Add Connected Service dialog in Visual Studio 2015 enables you to easily connect your application to Azure Application Insights, Azure Storage,Azure Mobile Services, Office 365, and Salesforce. 若要加入已連接服務,請以滑鼠右鍵按一下 [參考] 節點,然後選取 [ 加入已連接服務 ...]。To add a Connected Service, right-click the References node and then select Add Connected Service....

新增已連線的服務

[加入已連接服務] 對話方塊包含目前已安裝的所有已連接服務提供者,並提供取得提供者詳細資訊的方法、所使用的技術,以及目前專案中是否支援該提供者。The Add Connected Service dialog contains all of the Connected Service providers currently installed and provides a way to get more information about the provider, the technologies it uses, and if it is supported in the current project. 您可以使用 [ 尋找更多服務 ... ] 連結,在 [擴充功能和更新] 資源庫中探索其他提供者。Other providers are discoverable in the Extensions and Updates gallery using the Find more services... link. [ 加入已連接服務 ] 對話方塊也是可擴充的。The Add Connected Service dialog is also extensible. 如果您是服務開發人員,您可以使用我們的 已連線的服務 SDK 來建立提供者,以改善您的服務的可搜尋性和磁片使用量。If you are a service developer, you can use our Connected Services SDK to build a provider that can improve discoverability and drive usage of your services.

企業單一登入Enterprise Single Sign-On

商務應用程式的常見工作是使用 Azure Active Directory 設定企業單一登入的應用程式。A common task for business application is to configure the application for enterprise single sign on using Azure Active Directory. 您現在可以在應用程式的結構中,以滑鼠右鍵按一下您的應用程式,然後選取 [ 設定 Azure AD 驗證],輕鬆地執行這項作業。這會顯示類似 [加入已連接服務] 體驗的 wizard,引導您完成設定應用程式以使用 Active Directory 的程式。You can now do this easily at any point during the construction of your application by right-clicking on your application and selecting Configure Azure AD Authentication.... This will bring up a wizard similar to the Add Connected Service experience to guide you through the process of configuring your application to work with Active Directory. 在嚮導中指定 Active Directory 網域將會向該 Active Directory 註冊您的應用程式,並設定您的應用程式以提示登入。Specifying an Active Directory Domain in the wizard will register your application with that Active Directory and configure your application to prompt for sign-in.

在嚮導中指定 Active Directory 網域

適用于 Visual Studio 2015 RC 的 IIS 10 ExpressIIS 10 Express for Visual Studio 2015 RC

此 RC 版本包含新版的 IIS 10 Express;它的新功能包括對 HTTP 2.0 的支援,以及與 Windows 10 的 bits 同步。The RC release included a new version of IIS 10 Express; its new functionality includes support for HTTP 2.0, as well as a sync up of bits with Windows 10.

其他變更: Bug 修正和已知問題 Other Changes: Bug Fixes and Known Issues

如需這個版本的技術改善、Bug 修正及已知問題的完整描述,請參閱下列知識庫 (KB) 文章。For a complete description of technology improvements, bug fixes, and known issues in this release, see the following Knowledge Base (KB) article.

適用于 .Net 的 Azure SDK 2。7 Azure SDK 2.7 for .NET

Azure SDK 2.7 是 Visual Studio 2015 最終版本的第一個支援的 Azure SDK。Azure SDK 2.7 is the first supported Azure SDK for the final release of Visual Studio 2015. 以下是一些可協助改善 Azure 開發體驗的新功能和更新:Here are some of the new features and updates that will help improve your Azure development experience:

  • Visual Studio 2015 的登入改良:適用于 Visual Studio 2015 的 Azure SDK 2.7 現在包含透過 角色型存取控制、雲端解決方案提供者、 DreamSpark,以及其他帳戶和訂用帳戶類型存取 Azure 的帳戶支援。Sign-in improvements for Visual Studio 2015: Azure SDK 2.7 for Visual Studio 2015 now includes support for accounts accessing Azure through Role-Based Access Control, Cloud Solution Providers, DreamSpark, and other account and subscription types.
  • 適用于 Visual Studio 2015 的 Cloud Explorer: Azure SDK 2.7 包含 Visual Studio 2015 的 Cloud Explorer,可提供高效能、可擴充的工具來搜尋和查看您的 Azure 資源、檢查其屬性,以及從 Visual Studio 內執行重要的開發人員和診斷動作。Cloud Explorer for Visual Studio 2015: Azure SDK 2.7 includes Cloud Explorer for Visual Studio 2015 that provides a highly performant, scalable tool for searching and viewing your Azure resources, inspecting their properties, and performing key developer and diagnostic actions from within Visual Studio.
  • Visual Studio 2015 中虛擬機器的遠端偵錯程式:在使用 Azure Resource Manager 堆疊建立的虛擬機器上執行的遠端偵錯程式。Remote debugging for Virtual Machines in Visual Studio 2015: Remote debug processes running on Virtual Machines created using the Azure Resource Manager stack.
  • Azure Resource Manager 工具:我們更新了 Azure Resource Manager 的工具,讓您更輕鬆地使用新的 Visual Studio 線上組建工作。Azure Resource Manager Tools: We updated the Azure Resource Manager Tools to make working with the new Visual Studio Online build tasks easier. 此外,我們也新增了使用角色型存取控制 (RBAC) 和新訂用帳戶類型的增強功能。Additionally, we added improvements for working with Role Based Access Control (RBAC) and new subscription types.
  • Azure App Service 工具: App Service 工具現在也可在 Visual Studio 2015 中取得。Azure App Service Tools: App Service Tools are now also available in Visual Studio 2015. 這項更新為 Web Apps 提供遠端程式碼剖析支援、API Apps 的 Swagger 產生改進,以及多個帳戶登入支援。This update brings Remote Profiling support for Web Apps, improvements to the Swagger generation for API Apps, and multiple account sign-in support. App Service 工具現在使用 Azure 資源管理 Api 來提供所有功能,並可支援 DreamSpark 和雲端服務提供者。App Service tools now use the Azure Resource Management APIs for all features, and enables support for DreamSpark and Cloud Service Providers. 此外,我們也在此更新中新增了適用于 Visual Studio 2015 開發人員的 Azure API Apps 預覽版本的支援。We also added support for the Azure API Apps preview release for Visual Studio 2015 developers in this update.
  • HDInsight 工具:在此版本中,我們已針對在 Tez 上執行的 Hive 作業新增執行圖形的視圖、擴充了 Hive DML IntelliSense 支援、新增 SCP.Net 的 NuGet、升級我們的風暴範本,以及新增 Pig 的範本。HDInsight Tools: In this release, we have added views of execution graphs for Hive jobs running on Tez, expanded our Hive DML IntelliSense support, added NuGet for SCP.Net, upgraded our Storm templates, and added new templates for Pig.
  • Azure Data Factory 工具:現在已包含在 Azure SDK 中 Azure Data Factory 工具。Azure Data Factory Tools: Now included in the Azure SDK are the Azure Data Factory Tools. 我們的目標是要簡化 Azure Data Factory 的編寫體驗,並移除內部和部署的挑戰。Our goal is to simplify the Azure Data Factory authoring experience and remove on-boarding and deployment challenges. 我們在 Azure Data Factory 工具中量身打造的體驗和豐富的工具,可提高新使用者和先進使用者的生產力和效率。Our tailored experiences and rich tooling in the Azure Data Factory Tools improve productivity and efficiency for both new and advanced users. 在此版本中,客戶可以使用 Visual Studio 介面,以互動方式撰寫及部署資料管線。With this release, customers can interactively author and deploy data pipelines by using the Visual Studio interface. 如需這些工具的詳細資訊,請參閱 Azure Data Factory 的 blog 文章See the Azure Data Factory blog post for more information about these tools.

Windows 10 SDK Windows 10 SDK

這項工具會將更新 Visual Studio 2015,為執行通用 Windows 平臺的任何 Windows 裝置提供建立、偵測及提交應用程式所需的一切。This tools release updates Visual Studio 2015 to provide everything you need to build, debug, and submit apps for any Windows device running the Universal Windows Platform. 重點包括:Highlights include:

  • 以您選擇的語言(c #、VB、c + + 或 JS)建立通用 Windows 應用程式,並部署到 Windows 10 裝置。Create a Universal Windows app in the language of your choice – C#, VB, C++ or JS – and deploy to a Windows 10 device.
  • 新的偵錯工具和診斷工具,包括 XAML 應用程式和網路分析工具的 UI 偵錯工具。New debugging and diagnostic tools, including UI debugging tools for XAML apps and a network profiler.
  • 建立應用程式套件以提交至整合的存放區。Create app packages for submission to the unified Store.
  • Windows 10 行動裝置版模擬器現在會利用您電腦的圖形硬體 (GPU) 來加快螢幕轉譯的速度。The Windows 10 Mobile Emulator now takes advantage of your PC's graphics hardware (GPU) to make the screen render faster. 它使用 Microsoft RemoteFx,提供更快速且更有回應的調試環境。It provides a faster and more responsive debugging environment using Microsoft RemoteFx.
  • 您現在可以使用 Windows 10 行動裝置版模擬器中的 NFC 模擬功能,來建立及測試已啟用 NFC/近接的通用應用程式。You can now use the NFC simulation feature in the Windows 10 Mobile Emulator to build and test NFC/proximity-enabled universal apps.
  • 豐富的 XAML 設計工具支援建立為裝置量身打造的使用者體驗。Rich XAML designer support for creating user experiences tailored for the device.
  • 在雲端中 .NET Native .NET 應用程式的編譯。.NET Native compilation of .NET apps in the cloud.

如需 Windows 10 開發人員工具的詳細資訊,請參閱 您的世界和應用程式的升級時間For more information about Windows 10 developer tools, see It's time to upgrade your world, and your apps.

適用於 Visual Studio 的 Python 工具2。2 Python Tools for Visual Studio 2.2

Visual Studio 內完全免費的 Python 支援。Completely free Python support within Visual Studio.

  • CPython、PyPy、IronPython 等等CPython, PyPy, IronPython and more
  • 詳細的 IntelliSenseDetailed IntelliSense
  • 互動式偵錯Interactive debugging
  • 與 Visual Studio 功能整合Integrated with Visual Studio features
  • 免費且開放的原始碼Free and open-source

如需詳細資訊,請參閱 適用於 Visual Studio 的 Python 工具For more information, see Python Tools for Visual Studio.

Visual Studio Tools for Unity 2。0 Visual Studio Tools for Unity 2.0

將 Visual Studio 變成功能強大的 Unity 開發環境。Turn Visual Studio into a powerful Unity development environment.

  • 組建多平臺遊戲Build multi-platform games
  • Visual Studio 的 DebugDebug from Visual Studio
  • 在 Visual Studio 中建立 Unity 腳本Create Unity scripts in Visual Studio
  • 使用 Visual Studio 體驗增強的生產力Experience enhanced productivity with Visual Studio

如需 Visual Studio Tools for Unity 的詳細資訊,請參閱 使用 Visual Studio 的遊戲開發For more information about Visual Studio Tools for Unity, see Game Development with Visual Studio.

適用于 Visual Studio 1.1 (RC 的 Node.js 工具) Node.js Tools for Visual Studio 1.1 (RC)

將 Visual Studio 變成功能強大的 Node.js 開發環境。Turn Visual Studio into a powerful Node.js development environment.

  • 免費且開放的原始碼Free and open source
  • 智慧型程式碼完成Intelligent code completion
  • 先進的偵錯工具和分析Advanced debugging and profiling
  • 與其他 Visual Studio 功能和協力廠商工具整合Integration with other Visual Studio features and third-party tools
  • Node.js、io.js、JavaScript、TypeScript、HTML、CSS 和 JSON 支援Node.js, io.js, JavaScript, TypeScript, HTML, CSS, and JSON support

深入瞭解 Visual Studio 的Node.js 工具Learn more about Node.js Tools for Visual Studio.

Visual Studio 2015 的 Office Developer Tools Office Developer Tools for Visual Studio 2015

使用 Office 365 Api 進行開發Development with Office 365 APIs

  • Office 365 API 工具使用 Visual Studio 2015 中的新已連線的服務,提供開發人員將 Office 365 Api 整合到專案的引導式體驗。Office 365 API Tools uses the new Connected Services in Visual Studio 2015 to provide a guided experience for developers to integrate Office 365 APIs into the project.
  • 現在您可以在已連線的服務 wizard 中選取 [使用 Azure AD 設定單一 Sign-On],讓 Office 365 API 工具自動設定 ASP.NET MVC web 應用程式中的單一 Sign-On。Now you can let Office 365 API Tools auto-configure Single Sign-On in your ASP.NET MVC web applications by simply selecting "Configure Single Sign-On using Azure AD" in the Connected Services wizard.
  • 當您將 Office 365 Api 整合到專案中時,Office 365 API Tools 現在會從 NuGet.org下載並安裝最新版本的 OFFICE 365 API 用戶端程式庫 NuGet 套件。When you integrate Office 365 APIs into your project, Office 365 API Tools now downloads and installs the latest version of the Office 365 API client library NuGet packages from NuGet.org.

SharePoint 增益集開發SharePoint add-in development

  • 建立 SharePoint 增益集時,工具會將目標 SharePoint 版本設定為您在專案建立嚮導中指定的偵錯工具 SharePoint 網站版本。When creating a SharePoint add-ins, the tools set the target SharePoint version to be the version of the debugging SharePoint website that you specify in the project creation wizard. Wizard 會顯示選取的 SharePoint 版本,並可讓您覆寫該預設值。The wizard shows the selected SharePoint version and allows you to override that default. 您可以使用 [專案設計工具] 中的 [SharePoint] 索引標籤,在建立專案之後變更目標版本。You can change the target version after creating the project by using the SharePoint tab in Project Designer.
  • 這些工具現在會在目標版本為 SharePoint Online 時,安裝包含 Sharepoint Online 用戶端物件模型 (SPO CSOM) 至專案的 NuGet 套件。The tools now install a NuGet package containing the SharePoint Online Client Side Object Model (SPO-CSOM) into your project, when the target version is SharePoint Online. 這些工具會將 SharePoint Online CSOM 元件的參考加入至專案。The tools add references to the SharePoint Online CSOM assemblies to the project. 這些工具不再依賴 Microsoft 下載中心所發行的 SharePoint Online 用戶端元件 SDKThe tools no longer rely on the SharePoint Online Client Component SDK that is released in the Microsoft Download Center. 這可讓您更輕鬆地使用 Visual Studio 中的 NuGet 封裝管理員,在未來升級 CSOM 元件。This makes it easier for you to upgrade the CSOM assemblies in the future by using the NuGet Package Manager in Visual Studio.
  • 您現在可以使用 SAS 或 ACS 連接字串進行 Microsoft Azure 服務匯流排,以對 SharePoint 增益集中的遠端事件接收器進行 debug 和疑難排解You can now use either SAS or ACS connection strings for Microsoft Azure Service Bus to debug and troubleshoot a remote event receiver in SharePoint add-ins.

Office 增益集開發Office add-in development

  • 在此版本中,這些工具一律會以 v1.1 資訊清單(而不是 v1.0)為 Office 建立新的應用程式,讓您的應用程式可以支援 Office web 應用程式和 Office 2013 用戶端中的新功能。In this release, the tools always create new apps for Office with a v1.1 manifest instead of v1.0, so that your apps can support the new capabilities in Office web apps and Office 2013 clients. 針對使用 v1.0 資訊清單的 Office 現有應用程式,當使用需要 v1.1 資訊清單的任何新功能時,這些工具會將資訊清單升級為 v1.1。For existing apps for Office that use a v1.0 manifest, the tools upgrade the manifest to v1.1 when any new capability is used that requires a v1.1 manifest.

深入瞭解 Visual Studio 的 Office Developer ToolsLearn more about Office Developer Tools for Visual Studio.

適用于 Visual Studio 2015 的 GitHub 擴充功能 GitHub Extension for Visual Studio 2015

在 Visual Studio 中連接到您的 GitHub 存放庫的最簡單方式。The easiest way to connect to your GitHub repositories in Visual Studio.

  • 容易安裝Easy to install
  • 在 Visual Studio 中連接到 GitHubConnect to GitHub in Visual Studio
  • 建立存放庫Create repositories
  • 按一下即可複製存放庫Clone repositories with one click
  • 將您的本機工作發行至 GitHubPublish your local work to GitHub

深入瞭解 Visual Studio 的 GitHub 延伸模組。Learn more about the GitHub Extension for Visual Studio.

雲端負載測試 Cloud-based Load Testing

從全球 Azure 資料中心進行雲端式負載測試Cloud-based load testing from Azure datacenters worldwide

設定執行負載測試所需的基礎結構變得更容易:現在,您可以從世界各地任何支援的 Azure 資料中心執行雲端式負載測試。Setting up the infrastructure required to run load testing just got easier: Now, you can perform cloud-based load testing from any of the supported Azure datacenters around the world.

以雲端為基礎的負載測試現在支援 advanced agent 診斷Cloud-based Load Test now supports advanced agent diagnostics

在此版本中,我們新增了針對雲端負載測試執行測試代理程式診斷的功能。For this release, we added the capability to carry out test agent diagnostics for a cloud-based load test.

在雲端中進行偵錯工具很難,因為無法存取電腦,因此不一定可以從測試代理程式收集記錄檔或任何其他資訊。Debugging in the cloud is difficult because the machines are not accessible, and therefore, collecting logs or any other information from the test agents is not always possible. 然而,使用 advanced agent 診斷,您可以從測試代理程式收集記錄,並將它們附加至雲端負載測試結果。Nevertheless, with advanced agent diagnostics, you can collect logs from the test agents and have them attached to the cloud-load test results.


Visual Studio 2015 版本Visual Studio 2015 Releases

您可以查看 Visual Studio 2015 版本資訊的所有版本:You can view all versions of Visual Studio 2015 release notes:


頁首
Top of Page