I see many articles regarding the handling and packaging of existing applications, but I cannot find anything along the lines of “if you want to change your code for MSIX, this is how” (or how to code for MSIX from day 1).  How about an example of a product that was coded in VB .Net (or similar language) and was subsequently packaged in a MSI installer.  Now show the new version of that same code with the changes to fit MSIX, (registry, whatever else).  If the exe is being executed by the installer and it puts up a dialog that the user needs to respond to, how to handle that (in that custom actions are only available at the beginning and end of the MSIX packaging, and not while installing).

Something along the lines of “This must change”, if you want to write code for MSIX packaging.

​I see many articles regarding the handling and packaging of existing applications, but I cannot find anything along the lines of “if you want to change your code for MSIX, this is how” (or how to code for MSIX from day 1).  How about an example of a product that was coded in VB .Net (or similar language) and was subsequently packaged in a MSI installer.  Now show the new version of that same code with the changes to fit MSIX, (registry, whatever else).  If the exe is being executed by the installer and it puts up a dialog that the user needs to respond to, how to handle that (in that custom actions are only available at the beginning and end of the MSIX packaging, and not while installing). Something along the lines of “This must change”, if you want to write code for MSIX packaging.    Read More

​