Forum Discussion
Solved
How to create url shortcut in MSIX
"Hello MSIX support team,
We are working on MSIX POC project in which requirement is to create a shortcut which is pointing to client home page URL.
But I am unable to create MSIX package with above requirements,
1. Application only has 1 icon file and 1 shortcut which is pointing to client home page
2. Once we complete the installation and selects "First launch task" window we are not able to find the url shortcut as entry point.
Could you please suggest is how to create entry point which is pointing to url. Let us know if you need more information on this.
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": ""
}
]
ChaconMicrosoft
It is currently not possible to create a tile (shortcut) which directly points to an URL with an MSIX package. One thing you can do is create an application which opens the URL when it is launched.
If you are creating a new application it is recommended that you package it directly when you build it, for example using a Windows Application Packaging Project in Visual Studio. The MSIX Packaging Tool is intended for packaging existing applications for which you do not have access to the source.
Chacon The Package Support Framework PsfLauncher can be used to target a URL. You just Add PsfLauncher64.exe and PsfRuntime64.dll in your package, point your shortcut to Psflauncher, and enter the URL in the target application field in the Config.Json file's Application section..
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.
