In Build '16, Microsoft announced a technology which is going to convert desktop applications into Universal Windows Applications and this technology is going to be shipped with the Windows 10 Anniversary update, which is about to be released soon. This technology is known as the "Desktop Bridge" or "Project Centennial," and it will be the best thing that will happen for desktop application developers who want to use all the features that are available for the Universal Windows platform like Cortana and live tiles. Now you can prepare your applications like Win32 and WPF to convert to Universal Windows Applications by using the Desktop Bridge (Desktop App Converter).

So in this discussion I am going to explain why Microsoft wants this bridge between desktop and UWP, and we are also going to dive into the process of how it will work. So let's start rolling.
Why Microsoft Wanted this Project
Making the Windows Store better
There are a huge number of developers who just learn C# or Vb.net like me and start developing desktop applications, and the number of desktop applications created so far are more than 16 million. Now when Microsoft started shifting towards bringing all the technologies onto one platform they just skipped over these 16 million+ desktop applications and the desktop developers were like "Ooooooh gooosh!! What can we do to take advantage of this universal platform and the features involved in it?"
Easy Installation and Uninstallation of Application
When we buy a new laptop/ personal computer, it runs so fast. It boots fast, it opens every file very fast and all of the features are pretty much fast. But with time, it get slower and all of the functionality which was very fast, periodically get slowed down. What is the reason for that? You will get this answer shortly.
When you install an application to the desktop through an installer, what the installer does is that it goes to the registries of Windows and adds some new files there, and then there is an Application Folder App_Data, it includes all the files that the application stores while running and there are some other files which get piled into the memory. Now when we re-install an application, it is impossible to remove all of the files associated with that application, and even if you want to remove those -- let's say we want to remove the registries of that application -- the operating system will give you a big dialog box saying something like, "if you delete or modify this registry you will never be able to reboot or blah blah blah your system." So what the system eventually has to do is that when the system reboots it has to load all those registry files and it starts taking time, giving you a latency period in the functionalities. For example, every developer will have installed Visual Studio at some time, and this studio saves about one million registry files in the system and it's around 30 megabytes of just registries.
As compared to the Desktop Applications, UWP Applications has nothing to do with all of the above mentioned processes, and their uninstallation removes the whole application from the system, leaving no extra files, because the Universal Windows Applications have all of these files in their respective folders, so removing those isn't a big issue. So this is how the desktop applications when being converted to the Universal Windows Applications are going to be left with no extra files, hence not causing the system to have latency. I will discuss later how it happens.
Solving Performance Issues
Desktop applications don't have application life cycle events like the Universal Windows Applications have, like onNavigatedTo and onNavigatedFrom. So let's create a mock scenario. You have a desktop application running which is doing some heavy CRUD operations using Entity Framework and when you put your computer to sleep, what actually happens is that your desktop application also goes to sleep with the system staying in memory. Now notice that there is no mechanism that tells the application that our system is going to sleep so please release the resources, or in this case close out all the connections of the Database. So UWP addresses this problem. The applications there have an Application Lifecycle which can determine if the application is paused or stopped etc, and we can perform the related operations accordingly resulting in less usage of the resources and giving some extra performance.
Runtime Memory Optimization
As stated above, in the case of Windows Desktop Applications when the system reboots it has to load all the registry files first. In the case of UWA, the applications work with all the registry files when they are started, not when the system is started. So UWP offers the runtime optimization as compared to the desktop applications. So this gives Microsoft another strong reason to have this project underway.
Deep Dive Into Working of Desktop Bridge
I know by now there will be some obvious questions and some strange feelings about how it will fix the registries or how Universal Windows Applications will allow the third party components to get embedded into it. All of these questions will be answered when you understand the workings of this project.
Now there are basically three main steps of converting your Application using the Desktop Bridge,

Vignesh ManiPosted Jun 28, 2016, 8:32 AM
Nice
Basil HowitsonPosted Jun 27, 2016, 4:26 AM
Thank you very much for this. I am still a novice developer but reading articles like this definitely adds value to expanding my knowledge of the field.
Debasis SahaPosted Jun 27, 2016, 2:54 AM
Nice one..
Mahesh ChandPosted Jun 27, 2016, 2:03 AM
Interesting. Being a Windows developer, I definitely would love to check it out this tool. Can't wait. Thanks for sharing.
kalu singh raoPosted Jun 27, 2016, 1:44 AM
Nice...
RajaPosted Jun 27, 2016, 1:20 AM
Good one...
Prasanna MuraliPosted Jun 26, 2016, 9:12 PM
Nice one...