You still have to by a windows license , or buy from an OEM who has paid for the license.
Are you sure? I think Ms distributed the S version for free if you wanted.
Though it's possible that the upgrade option is more expensive if you haven't acquired from a OEM, but in that case, worst case scenario you are paying as much as you were before (the OEM version license from OP + the upgrade fee is the same as the previous OEM license ($150) from a google search)
Do you have a list of disallowed things in the wrapper (not Store policies, the part regarding i.e. services) handy? This sounds very vague, last time I heard of this it was supposed to be rather restrictive for everything but UI.
I'll try to find some documentation on that, but at least the information they presented on Build was:
- There are no code changes required to convert desktop apps (it used to take a few extra steps, but what they presented was precisely how you can now just change the installer to make the changes)
- The full win32 api is available to converted apps + uwp apis, and how you could easily migrate your codebase to uwp and keep the win32 funcionality either while you convert or even as a desktop only feature while there isn't a uwp equivalent api.
- There are some stuff that are either forbidden or that the system tricks the app into think it broke free of the container but it didn't.
Mind you the wrapper for win32 apps might be the same as uwp, but in the very least they allow more apis to break through the container than they do with uwp. (In fact some of the uwp changes from last year was allowing uwp to have some of those breaking points)