![]() ![]() Still in the shortcut properties, take advantage and change the values of the target and start in properties para %localappdata%\Microsoft\WindowsApps\contosoexpenses.exe e %localappdata%\Microsoft\WindowsApps respectively: Now, it is possible to change the shortcut icon to the %localappdata% path: This will be automated later using PSF scripts. To change the application shortcut, for now, it is needed to manually copy the icon to that folder. One way to solve this, is to copy the icon from the package to the %appdata% used by the MSIX application, i.e., the %localappdata%\Packages\ContosoExpenses_3z09h3y28h0qg\LocalCache\Roaming_ folder that doesn't have version number. ![]() Create the application shortcutĬreate a new application shortcut in a folder of your preference using the alias contosoexpenses.exe, as follows:īy default, the shortcut will be a generic icon:Ĭhanging the shortcut is straightforward but the challenge here is to avoid using the full application path that has the version number and that may change in a future update. Now that the alias is created, it is possible to proceed to the next steps. Once the package is created, install the package and start the application through the alias, for example, by pressing Win R and typing contosoexpenses: Switch back to the MSIX Packaging Tool and generate a new package. Include the application's execution alias after the element: įollows the manifest with the modifications: Include the value uap3 and desktop in the IgnorableNamespaces element: IgnorableNamespaces="uap uap3 desktop rescap build" Include the following namespaces, that will be used to create the alias, as follows: xmlns:uap3="" xmlns:desktop="" Create the application aliasĬlick on the Package information menu item and click on Open File, available on the bottom of UI, to edit the application manifest: Otherwise, Windows Explorer will not recognize the alias and it will not allow us to create the shortcut. Therefore, before create the shortcut, define the alias in the application manifest. The AppExecutionAlias allows it to launch the application with the value defined in the alias session of the application manifest, so there is no need to specify the full application path. To avoid having to change the application shortcut every time the application is updated, create the shortcut by pointing to the AppExecutionAlias. Example of the Contoso Expenses installation path:Ĭ:\Program Files\WindowsApps\ContosoExpenses_ 1.0.0.0_x86_3z09h3y28h0qg ![]() ![]() At the same time, the MSIX application path can change, once it has the version number specified in the installation folder.The MSIX application must be installed before creating the shortcut, so that we can specify the MSIX application path during the shortcut creation.The goal is to not clutter the user's desktop. Only create a shortcut if they are absolutely necessary.There are a couple of things to keep in mind: The idea is to copy the application shortcut, that will be available inside the package, to the user's Desktop through the PSF scripts. This document will show you how to create application shortcuts using Package Support Framework (PSF) that run scripts via the MSIX Packaging Tool and the Contoso Expense WPF application. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |