What's new in Windows 10 for developers, build 10586
Windows 10 build 10586 (also known as the November Update or version 1511), in combination with Visual Studio 2017 and the updated SDK, provide the tools, features, and experiences to make remarkable Universal Windows Platform apps. Install the tools and SDK on Windows 10 and you’re ready to either create a new Universal Windows app or explore how you can use your existing app code on Windows.
Windows 10 build 10586 - November 2015
|User Experience||The new Windows.UI.StartScreen.JumpList and Windows.UI.StartScreen.JumpListItem classes provide apps with the ability to programmatically select the type of system-managed jump list they want to use, to add custom task entry points to their jump list, and to add custom groups to their jump list.|
|Input||Keyboard delivery interceptor. Enables an app to override the system processing of raw keyboard input, including shortcut keys, access keys (or hot keys), accelerator keys, and application keys, but excluding secure attention sequence (SAS) key combinations. Secure attention sequence (SAS) key combinations, including Ctrl-Alt-Del and Windows-L, continue to be processed by the system.
Cross-process chaining of pointer input for both UWP apps and Classic Windows apps. New pointer events that enable cross-process chaining of input.
Ink Presenter for Classic Desktop apps. The ink presenter APIs enable Microsoft Win32 apps to manage the input, processing, and rendering of ink input (standard and modified) through an InkPresenter object inserted into the app's DirectComposition visual tree.
|Networking||For WebSockets users: MessageWebSocket.OutputStream.FlushAsync and StreamWebSocket.OutputStream.FlushAsync have been fully implemented, and wait for previously-issued WriteAsync calls to complete. Note that this may cause existing code to throw an exception if the WebSocket is in an invalid state when you call FlushAsync.
A new property CookieUsageBehavior was added to the existing Windows.Web.Http.Filters.HttpBaseProtocolFilter class. This allows developers to have control of how cookies are handled by the system.
|Microsoft Edge F12 Developer Tools||Microsoft Edge introduces great new improvements to F12 developer tools, including some of the most requested features from UserVoice. Explore new features in the DOM Explorer, Console, Debugger, Network, Performance, Memory, Emulation, and a new Experiments tool, that allows you to try out powerful new features before they're finished. The new tools are built in TypeScript, and are always running, so no reloads are required. In addition, F12 developer tools documentation is now part of the Microsoft Edge Dev site and fully available on GitHub. From this point on, the docs will not only be influenced by your feedback, but you're invited to contribute and help shape our documentation. For a brief video introduction to the F12 developer tools, visit Channel9’s One Dev Minute.|
|Windows Hello||Windows Hello provides your app the ability to enable facial or fingerprint recognition to log on to a Windows system or device. The Providers APIs allow IHVs and OEMs to expose depth, infrared, and color cameras (and related metadata) for computer vision into UWP, and to designate a camera as participating in Windows Hello face authentication. The Windows.Devices.Perception namespace contains the client APIs that allow a UWP application to access the color, depth, or infrared data of computer vision cameras.|
|New Gaming API||Use the new Windows.Gaming.UI.GameBar class to receive notifications when Game bar is shown or dismissed.|
|Bluetooth APIs||Several APIs were added and updated to extend support for Bluetooth LE, device enumeration, and other features in Bluetooth. See Windows.Devices.Bluetooth namespace.|
|Smart Card APIs||Several SmartCardCryptogram APIs were added to the Windows.Devices.SmartCards namespace to support secure cryptogram payment protocols. Payment apps using host card emulation to support tap-to-pay can use these APIs for additional security and performance. Apps can create a key and protect limited-use transaction keys using the TPM. Apps can also leverage the NGC (Next Generation Credentials) framework to protect the keys with the user’s PIN. These APIs delegate cryptogram generation to the system for enhanced performance. This also prevents any access to the keys and cryptograms by other apps.|
|Updated Storage APIs||In the Windows.Storage.DownloadsFolder class, your app can now create a file or create a folder inside the Downloads folder for a specific User. In the Windows.Storage.StorageLibrary class, your app can now get a specified Library for a specific User.|
|Windows App Certification Kit||The Windows App Certification Kit has been updated with improved tests. For a complete list of updates, visit the Windows App Certification Kit page.|
|Design downloads||Check out our new UWP app design templates for Adobe Photoshop. We also updated our Microsoft PowerPoint and Adobe Illustrator templates and made a PDF version of our guidelines available. Visit the Design downloads page.|
We'd love to hear your thoughts. Choose the type you'd like to provide:
Our feedback system is built on GitHub Issues. Read more on our blog.