Comment by garganzol
20 hours ago
My favorite example of that was when WinRT app .exe files could not be launched from the command line. Only via some Windows Store voodoo dance with approvals, signatures and "security" that made WinRT for developers essentially a dead-on-arrival technology.
I would not be surprised if you still cannot launch a fricking .exe.
This was sorted out in Windows 10 with the unification of WinRT programming models under UWP.
Nope, it wasn't solved in UWP days, neither it's solved today.
To satisfy my interest, I've tried creating WinUI app (aka UWP/WinRT) in Visual Studio 2026. And this is what I've got on the first app launch after compilation:
"This device needs to be set up correctly to develop this type of app for Windows. If you don't, then you can't install and test your app before you submit it to Windows Store"
I don't want to install/submit, I just want to be able to run my fricking .exe.
Why you call this issue solved? It's still right there - the same voodoo dances and disillusional expectations of subordination to Windows Store.