Building Devices with Windows 10 IoT

Play Building Devices with Windows 10 IoT
Sign in to queue


As component costs decrease and connectivity increases, the demand for intelligent IoT devices continues to accelerate rapidly. Windows 10 IoT offers solutions enabling everything from small, low-cost devices, to ruggedized portable handhelds, to powerful, graphics-rich systems. In this session, you will learn about the capabilities of these editions, their interoperability, and how to leverage them to create more secure and manageable enterprise class devices. Topics include: Overview of the Windows 10 IoT editions, their features, and capabilities, Supported hardware and SoCs to build your device, Rich developer tooling to build universal drivers and applications for your devices, How to leverage security and manageability features to build more secure enterprise devices, and Case study on building a more secure device from a hardware partner. Intended Audience: OEMs, ODMs, IDHs, IHVs, ISVs, Peripheral Manufacturer, Driver Developer.



Session Type:





Grand Ballroom I



The Discussion

  • User profile image

    Is there a step-by-step guide to downloading and using the  Image configuration designer.

  • User profile image

    Ideally you would show the computer screen (Powerpoint, Visual Studio, ...) full screen most of the time, and a view of the presenter sometimes.

    As it is the slides and the screen are washed up and unreadable.

    Also more working demos would be great.

    Still, so looking forward to Windows 10 IoT !

    I wish we could access a preview of Windows 10 on Raspberry 2


  • User profile image

    How can we read the code at e.g. 0:25:15?

  • User profile image

    Wow, strange to choose here the CeSetThreadPriority mapped to Win32's SetThreadPriority. It would be worth to mention the difference in parameters, yet alone the differences in thread scheduling.  Ever stopped to think why there is the CeSetThreadPriority API in WinCE in _addition_ to SetThreadPriority in the first place? (and calling SetThreadPriority "modern api", really?).

    The bottom line is that anything WinCE or even Win32 is rather not portable to UAP and would end up as big re-architecting exercise for anything not trivial. So why would one choose Win10 IOT over anything else (esp. given experience with support and commitment to WinCE)? What's MS business model here? Is it another "strategic" MS move that may get abandoned/dead ended?

    Also, standardizing GUI on ~WPF/XAML implies high res displays and mucho CPU/GPU (vector rendering) => $$$ & power.


  • User profile image

    What device were using in the demo SensorInfo, a Raspberry Pi 2?

Add Your 2 Cents