December 3, 2015 7:23 pm

Windows 10 SDK Build 10586 breakdown

By / Senior Technical Product Manager

This week we released a new Windows 10 SDK. Let’s dive deeper into some of the Universal Windows Platform (UWP) improvements in the SDK update:

Visuals, Effects, and Animations

Introducing Windows.UI.Composition, a new API family that directly targets the UI foundation layer. The UI Foundation layer sits below the framework (e.g. XAML) and above the DirectX graphical layer. A set of samples on GitHub is also available. The new APIs provide:

  • Fast graphical rendering of lightweight Visuals in 3D coordinate space
  • A new declarative animation engine built for scale, with innovative Expression animations along with key-frame animations that all run independent of the UI thread
  • High performance, real-time UI effects system. Effects applied on Visuals can be customized, chained, and have their properties animated

SQLite

SQLite data access library now ships with the Universal Windows Platform for local data access needs across all Windows 10 device families. SQLite implements a self-contained, serverless, zero-configuration, transactional SQL database engine. Developers can reference the SDK SQLite instead of packaging their own library with their app. UWP How to: Data Access was updated to help developers with SQLite with UWP apps.

Input & Ink

The update includes improvements in ink and keyboard.

  • Direct Ink for Win32 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. Now Win32 apps can use the same ink as UWP apps
  • 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. Note that 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. Enabled via new pointer events (for both UWP apps and Classic Windows applications)

More Efficient and Flexible AppX Installation

The update provides more flexibility to app installation on devices:

  • Reduced Installation Footprint. Until now, we have required disc space on the device of twice the AppX package size to install an app. So a 1GB app package would require 2+GB of disk to complete the install. Now we require only a small amount of incremental space, so a 1GB app package would require about 1.1GB on disk.
  • Secondary drives on desktop. On desktop secondary drives are now supported for app installs so you can install apps to D: by changing the location in settings under storage.  On mobile, the storage setting similarly allows apps to be installed on a SD card if one is present

XAML Updates

The SDK now includes several updated APIs for beautiful UI:

  • Jump Lists. The new Windows.UI.StartScreen.JumpList and Windows.UI.StartScreen.JumpListItem classes provide apps with the ability to programmatically select the type of jump list they want to use, add custom task entry points, and add custom groups.
  • XAML Updates. These include the ability to specify the clipboard format via updated API on RichText, better navigation with updated Maps APIs, and improvements to the default menu size via a few primitive APIs

Bluetooth and Networking

The updated SDK includes improvements for Bluetooth and networking:

Sensors

Window 10 introduced several improvements to Contextual Sensing including the ability to detect activities (e.g. walking, running, biking, in vehicle), to count steps, to detect altitude and barometric pressure, and the ability to detect the presence/absence of a user close to the device. A good summary is provided in this blog post. In addition, this blog post describes some more advanced sensor features including the ability to do Sensor Batching for the accelerometer, a ReadingTransform to make it easy to maintain proper app orientation across devices, and the ability to define and use Custom Sensors. With these changes, the full range of sensor APIs are available to all devices running Windows and depreciated the (Lumia-only) SensoreCore APIs that were their predecessor.

The November update continues this trajectory with the ability to get the current reading from sensors and to use sensors as background triggers. For details, check out the extensive collection of Devices and Sensors UWP samples in our sample repository on GitHub.

Windows.Devices.Perception namespace

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.

Device Storage

Developers now have additional flexibility for storing files and associating them to specific users:

Windows App Certification Kit (Windows ACK)

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 Kit (Photoshop)

To make it easier to design apps, we recently introduced 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.

Start developing and @WindowsDev would love to see what you create. If you find bugs or issues, please use the Windows Feedback tool, MSDN forums.

Join the conversation

  1. Is there any information on changes to the W10M App deployment to devices (ie. via WinAppDeployCmd/etc). On previous SDK (10240?) only WiFi deployment was working + USB deployment was broken. On this new SDK it’s the other way around – USB deployment is working but the WiFi deployment is broken (confirmed this on 2 x dev machines with W10M device running OS Build 10.0.10586.11).
    Not sure if this an SDK issue/compatibility problem (with SDK vs mobile OS build) – is a fix needed for the SDK or do we need to wait for a new mobile build for this to work?

  2. Great,
    but please take this idea to reality too:

    http://visualstudio.uservoice.com/forums/121579-visual-studio-2015/suggestions/8912350-bring-windows-10-universal-apps-to-android-and-ios

    Bring Windows 10 Universal Apps to Android and iOS

    Create something like what Xamarin is doing in order to help developers to code once and run EVERYWHERE (Wndows 10, windows 10 mobile, android and ios).

    If Microsoft could not buy Xamarin, at least do what they are doing by your own. Make something that enable us to archive real NATIVE cross platform development. It could dramatically increase the numbers of developers using .net to create mobile applications as well as increasing the number of apps created to wp too, since app could be compiled to ios, android AND WINDOWS PHONE. Hibrid apps like apache Cordova has a lot of potential but right now it is limited to offer a bad user experience when compared to the native apps you could build native with native objective-c on iOS, java on Android or C# (on Xamarin.Forms o WP and Windows 8). Porting .net to others platforms is good, but go further MS, create something that help us to “code once and run everywhere. And by EVERYWHERE I mean, not just windows, I mean: Native apps on Android, iOS, Windows PC, Windows Mobile, Xbox, HoloLens and to on. Bring us a tool that enable us to make Visual Studio Universal Apps REALLY UNIVERSAL (running as well on android and iOS).

    We want a Framework that enable us to build NATIVE.
    By the way Xamarin Starter edition has a very limited package size so is almost impossible to create even small apps with an organised architecture (multi layers) and its licences fees is very expensive too.
    Hey M$ look to the opportunity a tool like Xamarin could bring to the windows ecosystem. It could help you to resolve the app gap Windows Phone suffers so far. With a tool that can help developers to build native applications to windows as well as to android and iOS could bring the apple and android developers interest to use it and since it will be able to compile to windows phone then they will not have why to do not do so. It will also bring mobile developers from other platforms (android and iOS) to Visual Studio and .NET and the Windows Ecosystem.

    • And cut off the 30% royalty until windows apps market share will be acceptable for a company (not inly students) to invest in your ecosystem..

  3. What happens when a user with Windows 10240 tries to install an app built with the 10586 SDK?
    Is it not allowed? If so, it would become like Windows 8.0 vs 8.1 where we have to maintain the app for both versions (if that’s even possible). That would be terrible.

    I’m hoping that the SDK (update) is actually embedded in the app so the user’s version of Windows doesn’t matter.

      • I had the same question. How the heck do we “import” something in C#?
        I’m going to attempt switching to the native SQLite in a few weeks, if no one else has provided some documentation by that time, I’ll write a blog post. Hopefully I can figure it out (and I hope you can too).

  4. How do I update the SDK?
    I can’t choose anything but Build 10240 in my Project settings.
    System is up to date. VS doesn’t show me any updates related to the Windows UAP SDK.

    • I had the same question – I thought perhaps if I build a New Project I’ll look to see if it has new project settings there. When I chose New Project – I saw that the New Project window now had a new Install Windows Universal Tools item at the bottom of the list. Very strange place to put an update. ( I’ve already been building UWP apps with previous SDK release ).

      • You can also download the Windows SDK and install it. It installs the newest SDK.
        A shame that it doesn’t say that on the webpage though. So when you expect a new SDK to be released you have to download and start the installer a few times until it has the new version.
        However I’m kinda interested how downwards compatibility is done.
        I mean you can specify a minimum SDK version and a target like in android but what happens if you use functions that the minimum SDK doesn’t have?
        I guess I’ll have to do some research on that side.

  5. Still waiting for:

    MultiBinding
    CollectionViewSource
    Binding.StringFormat property

    You know, THE BASICS. Oh, and will we have to wait until Windows 18 to get DataGrid back?

  6. Hello, I want to know why the Windows.Devices.Perception API does not work in Windows 10 Mobile? If in the official documentation I see that this is allowed its use in UWP applications. When I try to access the infrared camera this returns me “Denied by System”. If it can not be used on telephones, the information should be updated indicating that limitation. Thanks.