Shortcut pointing to Batch script (.bat file) - PSF Tool not worked.

sidharthverma 

• PsfTooling contains a version of the PSF, so you might not need to get your own.
• The latest versions of the PSF that I maintain on my fork can be downloaded in binary form from the Github repository https://github.com/TimMangan/MSIX-PackageSupportFramework (See releases on the right side of the page.
• PsfTooling 4.15.2.1 contains the PSF Release 2021.12.07

The PSF Release 2022.1.19 should appear in the next PsfTooling release (target version 5). There is no set date for the next PsfTooling release, other than soon.

Hi sidharthverma,

The Express edition is a fully free version, all you need to do is to register with an email when you start using it. It shouldn't go into trial mode. Do you also have a separate version of Advanced Installer (Pro/Enterprise or Architect) installed on your machine? Maybe there is a license conflict between the Express edition and the commercial edition.

Regarding the option to select a BAT file - when you try to configure/select your application do you see the following option in the file picker? It should allow you to pick EXE and BAT file, as shown in the screenshot.

Tested by colleague of mine and new psflauncher seems to work and BAT/CMD files can be started directly by psflauncher32.exe in json file

TIMOTHY_MANGAN related to your answer, you posted: Thanks for posting the json. I'm not sure why the main bat file is started via cmd inside a powershell, but the scripting portion looks fine.

Is there another way of starting the BAT file, which is located in the bubble and should be run in the bubble? This seems to be the only way we could find. Another way was to use CMD.exe, but then it works only when we used a cmd.exe copy added to the package. When we ran c:\windows\system32\cmd.exe it seems the BAT file does not start in the bubble, but outside 😞

TIMOTHY_MANGAN thanks for your responses.....we have Zulu Java 1.8 version installed in the package. The current config.json we use looks like:

{
               "applications": [{
                              "id": "PSFLAUNCHERSIXFOUR",
                              "executable": "c:\\windows\\system32\\WindowsPowerShell\\v1.0\\powershell.exe",
                              "arguments": "-ExecutionPolicy Bypass -Command \"& {Invoke-CommandInDesktopPackage Test-0607.01-ENG_fg0t8wag126gc PSFLAUNCHERSIXFOUR cmd.exe '\/c c:\\progra~1\\Test\\Test\\bin\\runclient.bat' -PreventBreakaway}\"",
                              "workingDirectory": "",
                              "stopOnScriptError": true,
                              "startScript": {
                                            "scriptPath": "AppLauncher.ps1",
                                            "scriptArguments": "",
                                            "runInVirtualEnvironment": true,
                                            "showWindow": false,
                                            "waitForScriptToFinish": true,
                                            "runOnce": false
                              },
                              "endScript": {
                                            "scriptPath": "AppLauncher.ps1",
                                            "scriptArguments": "",
                                            "runInVirtualEnvironment": true,
                                            "showWindow": false,
                                            "waitForScriptToFinish": true,
                                            "runOnce": false
                              }
               }]
}

AppLauncher.ps1 is just a dummy file since without a startScript it seems to fail.

runclient.bat is a command file which starts the java.exe with arguments.

Above seems to work although it looks terrible due to the popup boxes of PowerShell and CMD.

But maybe you have some additional tips to make this easier configured. The final situation should be that the JAVA.EXE should be started in the bubble.