Re:Microsoft and the UWP for Enterprise Delusion
by cm2187 on Tuesday January 16, 2018 @10:36PM
(#16165257)
The problem of WPF in my opinion is the absence of strong typing (all binding is based on magic strings) and the fact that if you want to customise a little bit a control you are left rewriting it from scratch. WPF could be a lot better and easier to use than it is.
Re:Microsoft and the UWP for Enterprise Delusion
by m0ther on Wednesday January 17, 2018 @01:24PM
(#16170342)
That binding system is XAML specific. If you bypass XAML, you bypass the magic string binding as well.
I found interfaces a lot easier to build when I ditched the declarative markup and interfaced with the control system directly. XAML as far as I can tell was introduced as an attempt to woo web developers; but it's a thin layer ON TOP of WPF. It seems like a lot of people believe it IS WPF. WPF goes very deep.
Re:Microsoft and the UWP for Enterprise Delusion
by vitorgrs on Wednesday January 17, 2018 @07:43PM
(#16173600)
The same thing happens on UWP. People see XAML and thing that UWP is just that.
Re:Microsoft and the UWP for Enterprise Delusion
by shoover on Tuesday January 16, 2018 @11:56PM
(#16165576)
I thought UWP Desktop Bridge might allow enough desktop access to support packaging a Windows service. Nope, the Bridge is not designed for that purpose and Windows services are explicitly not allowed.
https://docs.microsoft.com/en-us/windows/uwp/porting/desktop...
Elsewhere the docs talk about registering background tasks through another interface, but it seems like proper integration with services is a legitimate use case for people trying to embrace the blessed desktop path.
Re:Microsoft and the UWP for Enterprise Delusion
by pjmlp on Wednesday January 17, 2018 @04:07AM
(#16166534)
The desktop bridge is only thought as a way to package legacy desktop applications as a stepping stone to port them into fully UWP ones.
That is the workflow all Microsoft sessions about it focus on.
Re:Microsoft and the UWP for Enterprise Delusion
by vitorgrs on Wednesday January 17, 2018 @07:44PM
(#16173608)
I think you can do the other way, too! A UWP app, + Win32 project app with service, full trust capabilities declared on manifest of this project then.
I was skeptical about WPF at first, as I didn't like XAML at all. I'm happy I stuck with it. Under XAML is a really elegant engine that you can interface with directly (few of my WPF projects have any XAML in them at all).
I skipped UWP for the same reasons as OP, and because you can't (as far as I have been able to figure out) distribute windows services with it. Win2D looked like an answer to a lot of my design issues, but I got a sense that the team building and maintaining it was smaller than mine.
If Microsoft heavily re-invested in the desktop I would be very happy.