Sharing the ideas and feature requests put forth during the packaging workshop. First three are the ideas listed in the subject line and following two are more of a feedback than ideas. First idea relates to shortcut management – advance options. Being aware of Shortcut management support to be included in upcoming release, will look forward to see the following supported in future releases It will be helpful to address customer requirements in enterprise domain if advance options are provided in the packaging wizard under shortcut section to Pin them to Taskbar OR Start Menu In absence of which administrators will have to deploy a custom script as a different program along with MSIX installation to accomplish the same Next idea is relating to certificate management. In 9/10 cases, the DEV environment or the MSIX packaging tool will be setup in the customer environment Provided an option under Settings menu to have a Standard certificate selected (which would remain persistent unless engineer changes) reduces one step in the process Last set of idea is to have a File Type Association (FTA) tab. List the file type associations of a package in group by the Executable name Have all the FTAs listed under respective executable, provided two ticker options to each FTA – Enable and Enforce Enable option would be to enable the FTA if the checkbox is ticked Enforce option would be to make that the Default program for that specific file type/extension upon install Following are the feedback on features. Include a Launch button in First Launch wizard screen (though the double click action works) Check with relevant teams if the definition for “Reset” option under “Apps & features” in Windows setting can be rephrased as the statement “Application will be re-installed” is not in-line with the actions performed in the background on selection of this option Will look forward for your response and support.
... View more
Sharing the ideas and feature requests put forth during the packaging workshop. First idea relates to enabling of Process Isolation as an optional feature for enterprise for a limited period and phase out the same once MSIX adaptation grows widely. Consider a scenario where in the organization would like to upgrade to version 2.0 of an application Sample_app for a new feature it introduced; However, a modification package Sample_mod of version 1.0 is not compatible with latest version of the application It will be very helpful to have Process Isolation enabled for the version 2.0 of Sample_app for a limited period of time until there is an upgraded version 2.0 of the modification package Sample_mod is made available with all fixes This would enable execution of two executables (Processes) with same name (but different version) Second idea, which is also a request, is to introduce capability to run Post-Install script. There could be scenarios such as – an application INI file contains Localhost address which is dynamically written at the time of application deployment Understanding the purpose of MSIX, which is to eliminate the necessity to have custom actions, scenarios such as above turn out to be challenging without installation time actions Having Post-Install script execution supported in MSIX will ease its adaptation for minority of applications as well which required such customizations Last idea is more of a wish list item. For the Packaging engineers, it will be a much helpful part if an optional Debug Shortcut (preferably a Command Prompt shortcut) option be provided (by default within the tool) Engineers can use this option to debug and identify cause for issues using ProcMon, RegMon etc. Once the Fix is developed, build the Final MSIX packaging with Fix by unselecting the Debug Shortcut option and release the Final build for end users Will look forward for your response and support.
... View more