Tech Community Live: Windows edition
Jun 05 2024, 07:30 AM - 11:30 AM (PDT)
Microsoft Tech Community

PSF and desktop shortcuts created by Microsoft.WindowsAppRuntime opens wrong entry from config.json.

Brass Contributor
When creating a desktop shortcut that points to the PSFLauncher.exe, the application launched is not the one that is named after the <Application> we are in (in this case Admin, and which works when called via the Application Alias), but rather the last in the list (LEX) in the config.json.  Removing all other entries from the config.json and the desktop shortcut launches fine.



<Dependencies>
......
<PackageDependency Name="Microsoft.WindowsAppRuntime.1.4" MinVersion="4000.1010.1349.0" Publisher="CN=Microsoft Corporation, O=Microsoft Corporation, L=Redmond, S=Washington, C=US" />
</Dependencies>



.....
<Application Id="Admin" Executable="PSFLauncher64.exe" EntryPoint="Windows.FullTrustApplication">
<uap3:VisualElements DisplayName="Administration" Description="Launch Administration" BackgroundColor="#3a0951" Square150x150Logo="Assets\Square150x150Logo.png" Square44x44Logo="Assets\Square44x44Logo.png">
<uap:DefaultTile Wide310x150Logo="Assets\Wide310x150Logo.png" Square310x310Logo="Assets\LargeTile.png" Square71x71Logo="Assets\SmallTile.png">
<uap:ShowNameOnTiles>
<uap:ShowOn Tile="wide310x150Logo" />
<uap:ShowOn Tile="square310x310Logo" />
</uap:ShowNameOnTiles>
</uap:DefaultTile>
</uap3:VisualElements>
<Extensions>
<uap4:Extension Category="windows.sharedFonts">
<uap4:SharedFonts>
<uap4:Font File="VFS\Fonts\DRAWSymbol.ttf"/>
</uap4:SharedFonts>
</uap4:Extension>
<uap3:Extension Category="windows.appExecutionAlias" EntryPoint="Windows.FullTrustApplication" Executable="PSFLauncher64.exe">
<uap3:AppExecutionAlias>
<desktop:ExecutionAlias Alias="admin.exe" />
</uap3:AppExecutionAlias>
</uap3:Extension>
<desktop7:Extension Category="windows.shortcut">
<desktop7:Shortcut File="[{Desktop}]\Administration.lnk" Icon="[{Package}]\Assets\LargeTile.png" Description="Launch Administration" />
</desktop7:Extension>
</Extensions>
</Application>
.........


PSF Config.json.


{
"applications": [
{
"id":"Admin",
"executable":"VFS\\ProgramFilesX64\\Administration\\mon.exe",
"arguments":"PROD ADMIN init \"%MsixPackageRoot%\\VFS\\ProgramFilesX64\\Administration\\admin.init\"",
"inPackageContext": true
},
{
"id":"Admin.exe",
"executable":"VFS\\ProgramFilesX64\\Administration\\Admin.exe",
"inPackageContext": true
},
{
"id":"ADM",
"executable":"VFS\\ProgramFilesX64\\Administration\\adm.exe",
"inPackageContext": true
},
{
"id":"LEX",
"executable":"VFS\\ProgramFilesX64\\Administration\\lex.exe",
"inPackageContext": true
}
]
}
1 Reply
Which version of the MSIX Packaging Tool is this happening with? I noticed that 1.2023.1212 introduced the dependency of the Windows Desktop App Runtime requirement to a lot of applications which didn't need it before, and have also experienced some issues with the Packaging Tool not saving the accelerator PSF configuration or manual saving of the PSF not being retained after being saved by the tool.