Forum Discussion
How to create url shortcut in MSIX
I tried to send email and wanted a good repro....guess what..it works now. Pff...did probably something wrong myself in the first place. This is my config which is working.
<Application Id="PSFLAUNCHERThree" Executable="PsfLauncher3.exe" EntryPoint="Windows.FullTrustApplication">
<uap3:VisualElements AppListEntry="default" BackgroundColor="transparent" Description="Google url" DisplayName="Google url" Square150x150Logo="Assets\Edge-Square150x150Logo.scale-400.png" Square44x44Logo="Assets\Edge-Square44x44Logo.scale-400.png" VisualGroup="Test"></uap3:VisualElements>
</Application>
"applications": [
{
"id": "PSFLAUNCHERThree",
"executable": "https://www.google.com/",
"arguments": "",
"workingDirectory": ""
}
]
To update this old post, there are two possibilities these days to achieve your goal:
- Microsoft has added an extension to the AppXManifest to support URL launches. This would use the default browser on the end user system. This is the most appropriate path for a developer, but can be used in repackaging if you manually edit the AppXManifest file.
- The Package Support Framework can launch the URL using either the default FTA (e.g. the same default browser), or you can provide a path to the default browser. This is supported when repackaging via the Microsoft MSIX Packaging Tool and PsfTooling or TMEditX (although I suggest the soon to be released versions of those external tools PsfTooling 5.2 or TMEditX 2.2). This is probably also possible through various other third party repackaging tools.
Hi Tim,
Thanks for this post.
Would it be possible to pass the port numbers as well along with URL ?
Could please share the steps and sample syntax if possible.
I don't have any shortcuts, files and icons. Just have url details and port number (to pass it as a parameter)
Thanks in Advance.
- I'm unsure if arguments are permitted in the Microsoft AppXManifest extension for URL Launches.
As to using the PSF, yes this can be done. If the port is specified in the .url file, then I believe TMEditX will detect and use it. If I am wrong, you can manually edit the config.json file in the TMEditX tool, after applying the PSF fix, to add the port number.- HI Tim,
Thanks for the reply.
Is there any sample manifest file sysntax to call url using psflauncher ? could you please help me if any.
Thanks in advance.- The AppXManifest file application entry is really the same as any other application being handled by the PSF; you'll point the executable to a copy of PsfLauncher in the package. Here is a part of the syntax of the config.json file that has the important stuff:
"applications": [
{
"id": "PSFLAUNCHEROne",
"executable": "VFS\\ProgramFilesX86\\Math Mechanixs\\Math Mechanixs\\Bin\\MMLicManager.exe",
"arguments": "",
"workingDirectory": "VFS\\ProgramFilesX86\\Math Mechanixs\\Math Mechanixs\\Bin"
},
{
"id": "PSFLAUNCHERTwo",
"executable": "VFS\\ProgramFilesX86\\Math Mechanixs\\Math Mechanixs\\MathMechanixs.exe",
"arguments": "",
"workingDirectory": "VFS\\ProgramFilesX86\\Math Mechanixs\\Math Mechanixs"
},
{
"id": "PSFLAUNCHERThree",
"executable": "VFS\\ProgramFilesX86\\Math Mechanixs\\Math Mechanixs\\Help\\MathMechanixs.chm",
"arguments": "",
"workingDirectory": ""
},
{
"id": "PSFLAUNCHERFour",
"executable": "VFS\\ProgramFilesX86\\Math Mechanixs\\Math Mechanixs\\Website.url",
"arguments": "",
"workingDirectory": ""
},
{
"id": "PSFLAUNCHERFive",
"executable": "VFS\\ProgramFilesX86\\Math Mechanixs\\Math Mechanixs\\Readme.txt",
"arguments": "",
"workingDirectory": ""
}
PsfLauncher4.exe in the AppXManifest file mapps to the entry above.