Desktop Bridge – The Migrate phase: invoking a Win32 process from a UWP app

In the last posts we’ve seen, so far, three different approaches to use the Desktop Bridge: Taking an existing Win32 installer and converting it into an AppX package through the Desktop App Converter tool or by leveraging manual conversion Taking an existing Win32 application and enhancing it, by adding UWP APIs to send toast notifications,…

48

Call Remote Assist from your HoloLens App

Unity Application screenshot
Unity Application screenshot

We annonced, in September 2018, new 1st party Mixed Reality business applications from Microsoft: We recognize that many employees need information in context to apply their knowledge and craft. Not only on a 2-D screen — but information and data in context, at the right place, and at the right time, so employees can produce…

37

Desktop Bridge – Converting an installer with Desktop App Converter

Hopefully, thanks to the previous post, you have now a better picture of the scenario where the Desktop Bridge fits: it helps Win32 developers to start moving their first steps in the UWP world and getting benefits of some of his advantages, without having to rewrite the app from scratch. In this article we’ll start…

30

Handling auto updates for sideloaded UWP and Desktop Bridge apps

If your goal is to reach the widest possible audience for your Windows application, the Microsoft Store is without any doubt your best choice. Other than being available to every Windows 10 user on the planet, it allows to forget about all the processes related to application development which aren’t actually “development”. I’m talking about…

29

Move your first steps with .NET Core 3.0 for desktop development

Warning! This post is dedicated to highly experimental technologies 😃 If you’re into development in the Microsoft ecosystem, I’m sure you’re familiar with .NET Core. It’s a new framework, built from scratch, to bring all the goodies of the .NET Framework into the new modern world. Unlike the full .NET Framework, which has its roots…

24

Supporting “launch at startup” in a desktop app converted with the Desktop Bridge

One of the common requirements that many traditional desktop apps have is to support the “launch at startup” option: when the user logs in into his Windows PC, the application is automatically started, without requiring him to manually open it. It’s a way to speed up the workflow of the user and it’s leveraged especially…

18

Desktop Bridge – Multiple desktop processes, a single UWP container

In the previous post we have learned how to expand a desktop application with a background task, which is a component that belongs to the Universal Windows Platform. For the first time, we didn’t have just a single process running inside the UWP container (like we’ve seen in this post, where we were leveraging some…

11

An easier way to generate the packages for a Desktop Bridge converted app

In one of the posts on this blog we’ve seen how to use the manual approach to generate a converted app starting from a regular desktop app. This approach is perfect when you have a simple executable or a self-packaged app, which doesn’t need an installer that you can process through a tool like the…

9

Desktop Bridge – Expanding a desktop application with a UWP component

In one of the previous posts we have seen how the Desktop Bridge can be helpful to take an existing desktop application and expanding it with some APIs from the Universal Windows Platform, without having to immediately rewrite it completely as a native UWP app. When a Win32 application is running, in fact, inside the…

9