Brian Hamilton They didn't give up on it. It was officially unveiled at Build 2016. And, they will only be supported starting with the Windows 10 Anniversary edition. It will allow you to package a Win32/desktop application, inside a UWP app package for distribution in the app store. Your Win32/desktop application will still only run on a Win32 desktop, as it always has. It will allow you to add support for some of the UWP platform features to your Win32/desktop application, i.e.: live tile, notifications, etc...
The main goal(that was outlined at Build 2016) of this bridge is to allow the developer to gradually migrate their application from Win32/desktop to a UWP app. You would be able to migrate the GUI from Win32/desktop to UWP, while still keeping the business logic in the Win32/desktop section of the app. And, once you have the GUI migrated, you can then start migrating the business logic from Win32/desktop to UWP. And, then once the app is fully UWP, and no Win32/desktop(full trust) portion, it can be deployed on any Windows 10 device(desktop, laptop, tablet, phone, embedded/IOT, Hololens, Xbox One, etc...).
I like the "Reach every Windows device" part, which means "reach exactly the same devices that you can reach today using Win32/64". Or they still think that this year will be the year of Windows Phone? LOL
I think they will merge this with Windows Containers in 2017. This would make it possibly to have a Win32 app running on a XBox if it supported the base image by using a VM (like they do with linux containers). However I'm not convinced there is really a use case fpr running a Win32 App on anything different than a notebook or a desktop.
i thought MS had sort of given up on the bridge...they must have made some progress?
ReplyDelete/sub
ReplyDeleteBrian Hamilton They didn't give up on it. It was officially unveiled at Build 2016. And, they will only be supported starting with the Windows 10 Anniversary edition. It will allow you to package a Win32/desktop application, inside a UWP app package for distribution in the app store. Your Win32/desktop application will still only run on a Win32 desktop, as it always has. It will allow you to add support for some of the UWP platform features to your Win32/desktop application, i.e.: live tile, notifications, etc...
ReplyDeleteThe main goal(that was outlined at Build 2016) of this bridge is to allow the developer to gradually migrate their application from Win32/desktop to a UWP app. You would be able to migrate the GUI from Win32/desktop to UWP, while still keeping the business logic in the Win32/desktop section of the app. And, once you have the GUI migrated, you can then start migrating the business logic from Win32/desktop to UWP. And, then once the app is fully UWP, and no Win32/desktop(full trust) portion, it can be deployed on any Windows 10 device(desktop, laptop, tablet, phone, embedded/IOT, Hololens, Xbox One, etc...).
i might have been confused with the bridge for windows phone?
ReplyDeleteI like the "Reach every Windows device" part, which means "reach exactly the same devices that you can reach today using Win32/64". Or they still think that this year will be the year of Windows Phone? LOL
ReplyDeleteBrian Hamilton They did suspend development of Project Astoria(the Android bridge). That might be the one that you were thinking about.
ReplyDeleteI think they will merge this with Windows Containers in 2017. This would make it possibly to have a Win32 app running on a XBox if it supported the base image by using a VM (like they do with linux containers). However I'm not convinced there is really a use case fpr running a Win32 App on anything different than a notebook or a desktop.
ReplyDeleteDaniel Rail yes, that is what I was thinking of
ReplyDelete