7 ms·

Our reps wanted to push us into enterprise. We went with LTSC against their advice because the upgrade cycle is much better. IoT Core looks interesting but I a

Our reps wanted to push us into enterprise. We went with LTSC against their advice because the upgrade cycle is much better. IoT Core looks interesting but I am not sure if we are ready for App Store only. Does it even support WPF or only UWP?

naikrovek 8y ago
There is NO graphical Win32 stuff; UWP only. There are some non-graphical Win32 APIs but not like full Windows. It's basically .net core and UWP and all the old familiar Windows stuff is gone. IoT Core is either the best possible Windows or the worst possible Windows, depending on your point of view. For some things, it's a perfect fit. If you can't fit into a .net core & UWP ecosystem entirely then it won't be a good fit if you need a GUI.
- maxxxxx 8y ago
  UWP is a no-go already. No way we can port our WPF code.
  - naikrovek 8y ago
    Well, UWP and WPF are close cousins, so it probably isn't as bad as one would think if they didn't know that. They're both XAML, though they are not quite the same. The main thing is that with WPF you can use the same Win32-type logic you've always been using. UWP is it's own API entirely. It's not all that different, but it is different. Things are organized better and APIs make more sense in UWP-land to me. So the gui would probably port over relatively easily. The application logic probably wouldn't.
    - maxxxxx 8y ago
      The GUI would be the easy part but our applications have a lot of background logic. Going to UWP would be almost a complete rewrite without actually improving anything. From what I have seen so far UWP is just different but not really better than WPF.
      - naikrovek 8y ago
        Can't argue with any of that. Presumably, at some point in the future UWP support will extend beyond WPF's support window, and right now they are both supported, so it would be silly to switch solely for the sake of making IoT Core a viable deployment platform for you.

naikrovek 8y ago

There is NO graphical Win32 stuff; UWP only. There are some non-graphical Win32 APIs but not like full Windows. It's basically .net core and UWP and all the old familiar Windows stuff is gone. IoT Core is either the best possible Windows or the worst possible Windows, depending on your point of view. For some things, it's a perfect fit. If you can't fit into a .net core & UWP ecosystem entirely then it won't be a good fit if you need a GUI.

maxxxxx 8y ago
UWP is a no-go already. No way we can port our WPF code.
- naikrovek 8y ago
  Well, UWP and WPF are close cousins, so it probably isn't as bad as one would think if they didn't know that. They're both XAML, though they are not quite the same. The main thing is that with WPF you can use the same Win32-type logic you've always been using. UWP is it's own API entirely. It's not all that different, but it is different. Things are organized better and APIs make more sense in UWP-land to me. So the gui would probably port over relatively easily. The application logic probably wouldn't.
  - maxxxxx 8y ago
    The GUI would be the easy part but our applications have a lot of background logic. Going to UWP would be almost a complete rewrite without actually improving anything. From what I have seen so far UWP is just different but not really better than WPF.
    - naikrovek 8y ago
      Can't argue with any of that. Presumably, at some point in the future UWP support will extend beyond WPF's support window, and right now they are both supported, so it would be silly to switch solely for the sake of making IoT Core a viable deployment platform for you.