Open neo42dhh opened 8 months ago
What do you think about including AppX as InstallMethod and UninstallMethod (maybe it needs to be called MSIX), so we can include it as another standard procedure of Install-NxtApplication and Uninstall-NxtApplication (without the complexity of the Teams package - just normal install and uninstall)? Such setup files might be called .appx, .msix or *.msixbundle (like WindowsApps) ... anything else?
here some additional links: https://learn.microsoft.com/en-us/windows-hardware/manufacture/desktop/sideload-apps-with-dism-s14?view=windows-11#add-apps
here you find a list of returncodes: https://learn.microsoft.com/en-us/windows/win32/appxpkg/troubleshooting here is the describtion of the Log Commandlet: https://learn.microsoft.com/en-us/powershell/module/appx/get-appxlog https://learn.microsoft.com/en-us/powershell/module/appx/get-appxlasterror
I like the idea and would see this as the major feature for the next release.
At the moment we use native powershell commandlets like Add-AppxProvisionedPackage, Get-AppxProvisionedPackage, Get-AppxPackage, Remove-AppxPackage and Remove-AppxProvisionedPackage for handling the installation and uninstallation of AppX Packages. However, this is complex as success checks, error handling and logging have to be done manually. For examples you can refer to MSTeams Package. As we expect to have more and more Appx packages in the future, an NXT function would be useful for this. Maybe it would also be a good idea to make AppX usable as installer type in neo42packageconfig.json in the future.