Bring your desktop apps to UWP and the Windows Store using the Desktop Bridge

Sign in to queue


Learn how the latest Windows 10 platform and tooling improvements make it easy to use the Universal Windows deployment technology for your desktop applications, modernize them with Windows 10 features, and migrate them to the Universal Windows Platform. Distribute and monetize your Delphi, Electron, MFC, Winforms, or WPF apps with the Windows Store. Take advantage of new Windows 10 features like Cortana and Live Tiles in your apps while still maintaining Windows 7 compatibility in your code base. We also cover how you can keep utilizing your existing Win32 code investments while migrating to the Universal Windows Platform.
For more information, check out this course on Microsoft Virtual Academy:



Session Type:





TCC L3 Tahoma 5 (200)



The Discussion

  • User profile image

    UWP is not a viable solution for many mission critical applications that need to run with unrestricted access to the file system as well as perform inter-process communication and long running background operations. How does the desktop bridge address these issues ? For example, a UWP app gets suspended every time the app is minimized or loses focus - this is not acceptable for desktop apps that have continuously running background threads performing critical tasks. Although UWP maybe good for consumer facing apps, it seems that Microsoft is not focusing enough on supporting desktop apps that could benefit from the modern XAML UI without sacrificing core desktop functionality. For example, it should be possible to use the UWP touch friendly XAML controls to build a desktop app so that it has the best of both worlds - smooth, fluid UI with full support for conventional desktop scenarios such as long running background tasks, file system access, inter process communication, etc.

  • User profile image

    @aceguy2017:  I think the video explains this pretty well.

    The desktop bridge allows you to run mixed components.  You can write your UI in a UWP executable, couple it with a desktop executable for anything that UWP doesn't allow, and package all that up as one application.  As more and more Win32 APIs are ported to UWP, the amount of code in the desktop executable can decrease (perhaps even go away at some point).

    For cases where the application needs more power/trust than even a Centennial app would allow (such as a driver or system service), you could make that part available as a separate download and let the Store app communicate with it when necessary.

  • User profile image

    @aceguy2017: You can now ask for the ability for your app to run in the background without suspension and do all the stuff you mention.  The UWP API is quite complete these days.

Add Your 2 Cents