MSIX vs MSI - How Do I Know If My App is a Good Candidate for MSIX?

MaWa316 A topic far to complex to answer in a single post.

We are unlikely to see additional support for custom actions beyond what we can do using the run once script.  Many custom actions in existing MSIs are doing things at a system level that we'd really want to see done inside the container to avoid impacting other apps and the OS and making cleanup really be clean.  So generally, if the purpose of a custom action is to configure your app based on local conditions, you should be able to do that.  Custom actions intending to affect the OS and other apps may prove more problematic, but if we ever get the equivalent to connection groups these may be possible as well.

The licensing question is easier to handle and I'll take my attempt to answer it as someone that doesn't work for Microsoft.  Perhaps not a concrete answer, but my opinions. The Windows Store may be well accepted for consumers, but enterprise scale customers often don't want to acquire their apps from there.  Also, vendors with their own licensing solution might not see the need for it, and Microsoft Store licensing might not have all of the licensing options that you use today.  Microsoft has a licensing solution via the store that supports vendors without their own licensing and wanting to use this as a distribution chain.  But vendors can still use existing style licensing, and may still distribute via other means. 

If the package goes through the Windows Store it must use the Windows store license, but you can also have your own licensing on top of that.  I'm guessing that vendors that distribute themselves (such as via their own website and an AppInstaller file) and also through the Windows Store would be likely to remove their licensing from the package uploaded to the store and rely on Microsoft, while retaining it in the package self-deployed.