Forum Discussion

shreedharghare's avatar
shreedharghare
Copper Contributor
Sep 09, 2020
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 ...
  • Pollewops's avatar
    Pollewops
    Dec 16, 2024

    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": ""
        }
      ]

TIMOTHY_MANGAN's avatar
TIMOTHY_MANGAN
MVP
May 05, 2023
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.
ramprasadb1986's avatar
ramprasadb1986
Copper Contributor
May 05, 2023
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.
  • TIMOTHY_MANGAN's avatar
    TIMOTHY_MANGAN
    MVP
    May 24, 2023
    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.

Resources