4 ms·

My concern is first off, this seems like it is going to break a massive number of applications. It also seems that they are pushing this layer of access manage

My concern is first off, this seems like it is going to break a massive number of applications. It also seems that they are pushing this layer of access management that doesn't have proper support on any platform but UWP. I see this as Microsoft taking yet another step to force people to move to their new Appstore model. by choking the access to the operating system away from any other platform, which I find really amusing because their own top tier applications aren't built on these platforms (office, visual studio, etc..).

ctrlaltdestroy 9y ago
I imagine Office, VS etc are too big to "port" to Appstore model. Also people still use these applications in Windows 7 and so that would mean having two parallel versions of the same app and release features and support for both.
- pjmlp 9y ago
  Office will be "store only" on the upcoming version for Windows 10, check Build presentations.
  - cube00 9y ago
    Isn't that just wrapped for the store in their AppV model not a true UWP app?
    - WorldMaker 9y ago
      The distinction of what makes a "true UWP app" certainly gets blurrier with the "Centennial" desktop bridge, but it's still rather more "true UWP" than AppV is/was.
    - pjmlp 9y ago
      While it isn't a pure UWP app, it is a step into that direction and already a big difference from being a standard desktop app.
pjmlp 9y ago
Better update yourself. The next version of Office and Note for Windows 10 are going to be store only. At Build they also had people from Adobe, Cakewalk and Kodi showing their desktop apps ported to the UWP via the Desktop Bridge. Like they did with WPF and Visual Studio, they are pushing everyone into the train by dragging their own devs into it.
- 0xffff2 9y ago
  > Like they did with WPF and Visual Studio Except Visual Studio isn't using anything newer than WPF yet, is it?
  - pjmlp 9y ago
    You completely missed the mark. .NET developers only started taking WPF seriously after the performance improvements Microsoft did to WPF, which took place after Visual Studio team adopted WPF to prove its quality. If you intended to do any remark regarding UWP, first WPF is not going anywhere as communicated to those that care to learn what goes at Build, and second the architecture between WPF, Silverlight and UWP is almost the same, just a few differences regarding XAML features and .NET APIs.

ctrlaltdestroy 9y ago

I imagine Office, VS etc are too big to "port" to Appstore model. Also people still use these applications in Windows 7 and so that would mean having two parallel versions of the same app and release features and support for both.

pjmlp 9y ago
Office will be "store only" on the upcoming version for Windows 10, check Build presentations.
- cube00 9y ago
  Isn't that just wrapped for the store in their AppV model not a true UWP app?
  - WorldMaker 9y ago
    The distinction of what makes a "true UWP app" certainly gets blurrier with the "Centennial" desktop bridge, but it's still rather more "true UWP" than AppV is/was.
  - pjmlp 9y ago
    While it isn't a pure UWP app, it is a step into that direction and already a big difference from being a standard desktop app.

pjmlp 9y ago

Better update yourself. The next version of Office and Note for Windows 10 are going to be store only. At Build they also had people from Adobe, Cakewalk and Kodi showing their desktop apps ported to the UWP via the Desktop Bridge. Like they did with WPF and Visual Studio, they are pushing everyone into the train by dragging their own devs into it.

0xffff2 9y ago
> Like they did with WPF and Visual Studio Except Visual Studio isn't using anything newer than WPF yet, is it?
- pjmlp 9y ago
  You completely missed the mark. .NET developers only started taking WPF seriously after the performance improvements Microsoft did to WPF, which took place after Visual Studio team adopted WPF to prove its quality. If you intended to do any remark regarding UWP, first WPF is not going anywhere as communicated to those that care to learn what goes at Build, and second the architecture between WPF, Silverlight and UWP is almost the same, just a few differences regarding XAML features and .NET APIs.