7 ms·
Opps. Yah I messed up the naming, I meant exes, but just started typing 64 vs 32 which really is only a memory thing, if you simplify it. Converting a Win32 ex
by kalcode 9y ago
Opps. Yah I messed up the naming, I meant exes, but just started typing 64 vs 32 which really is only a memory thing, if you simplify it.
Converting a Win32 exe using UWP Desktop Bridge is stupid easy though. Older exe with a lot of legacy dependencies may be more difficult or lack of source code. In which case they need a virtualization to run those legacy app.
So even though all games/apps fall into this category most companies could have a UWP build ready very quickly.
- dmitrygr 9y agoYou do not understand how said "bridge" works... It just wraps the app, but underneath still calls those same win32 APIs. If you remove the APIs, "bridged" apps won't work. Hence why TFA mentions that not all win32 API can be removed and it isn't clear which will be. So "bridging" your win32 app will not somehow make it immune to win32 api going away.