User Profile
KumarOne
Copper Contributor
Joined 6 years ago
User Widgets
Recent Discussions
How to handle MSIX application shortcut Arguments using MSPT + PSF Files
Hi, I’m working on MSIX application shortcut Arguments for Mozilla Firefox to build some understanding on the process of how it works. I’m facing the issue as in below. Note: I have tested the same using Advanced Installer and PSFTooling it works as expected, but when i’m trying to do same with PSF files i’m having issue. Steps Performed In MSPT Monitoring phase installed the firefox application via VFS Not launched the shortcuts Copied the 32 bit (PSFLauncher32, psfruntime32,psfrundll32) files downloaded from https://github.com/microsoft/MSIX-Labs/tree/master/MSIXLab/Tools and copied in “C:\ProgramFilesX86\Mozilla Firefox” Renamed PSFLauncher32 to PSFLauncher1 Modified the Shortcut Target to "C:\Program Files (x86)\Mozilla Firefox\PsfLauncher1.exe" Created a Json file referenced from PSFTooling and copied in “C:\ProgramFilesX86\Mozilla Firefox” { "enableReportError": true, "applications": [ { "id": "PSFLAUNCHEROne", "executable": "VFS\\ProgramFilesX86\\Mozilla Firefox\\firefox.exe", "arguments": "-devtools", "workingDirectory": "VFS\\ProgramFilesX86\\Mozilla Firefox", "stopOnScriptError": false } ], "processes": [] } Here is my Application manifest file details <!--Package created by MSIX Packaging Tool version: 1.2019.1220.0--> <Identity ProcessorArchitecture="x64" Version="1.0.0.0" Publisher="CN=Contoso Software (FOR LAB USE ONLY), O=Contoso Corporation, C=US" Name="Firefox-MSPT-PSF-X86"/> -<Properties> <DisplayName>Firefox-MSPT-PSF-X86</DisplayName> <PublisherDisplayName>MS</PublisherDisplayName> <Description>Firefox-MSPT-PSF-X86</Description> <Logo>Assets\StoreLogo.png</Logo> </Properties> -<Resources> <Resource Language="en-us"/> </Resources> -<Dependencies> <TargetDeviceFamily Name="Windows.Desktop" MaxVersionTested="10.0.18335.0" MinVersion="10.0.17763.0"/> </Dependencies> -<Capabilities> <rescap:Capability Name="runFullTrust"/> </Capabilities> -<Applications> -<Application EntryPoint="Windows.FullTrustApplication" Executable="VFS\ProgramFilesX86\Mozilla Firefox\PsfLauncher1.exe" Id="PSFLAUNCHEROne"> -<uap:VisualElements Description="Firefox" Square44x44Logo="Assets\Square44x44Logo.png" Square150x150Logo="Assets\Square150x150Logo.png" DisplayName="Firefox" BackgroundColor="transparent"> <uap:DefaultTile Square71x71Logo="Assets\Square71x71Logo.png" Square310x310Logo="Assets\Square310x310Logo.png" Wide310x150Logo="Assets\Wide310x150Logo.png"/> </uap:VisualElements> </Application> </Applications> </Package> Upon testing the package i get below error I’m struggling hard to overcome this issue but no luck, Any Assistance/Guidance/direction will be much appreciatedMSIX : Modification Package Challenges
Hi, As part of MSIX Assessments we are trying to explore the option of Applications Redundancy, so we testing few MSIX Modification packages in our environment and having some challenges. Below are the few scenario's will keep updating as and when found issues. Environment Details: MSIX Packaging Tool Version - 1.2019.1018.0 Packaging Machine Windows Version - 1809(OS Build 17763.914) Testing machine Windows Version - 1809(OS Build 17763.1098) 1) Modification package not getting applied Properly. Main Package - Firefox ESR 68.5.0 Modification Package - Customization(Homepackage settings, browser Cache setting via Moziall.cfg) 2) Identified an issue when Both Main and Modification packages have same file name, New version File which is in Modification Package does not get's applied, tried with Some Inhouse apps 3) As part of Rollback testing - Modification Package Installation/Uninstallations are working fine manually, but when trying to removed from Sccm applicaiton in Software center it shows as uninstall, but still availiable in 'App add-on & downloadable Content' on client machine. 4) In our environment we have few Inhouse apps which are environment based apps, source will be the same for across environments with config files and Environment specific shorcuts(Few users will be part of Multiple environments). As Modification packages does not support Shortcuts, this is not going to work as expected. This is also a quiet common scenario's in enterprises. How can we handle like this apps ? 5) When ever we create an Newer Version package for the Main Package upgrade, everytime we also need to update the Modification package(Dependency details changes), unless we use same name for MainPackage for each and every updates/upgrades . I believe this is common across the enterprises. How is it helping from Packaging Paralysis ? as we need to update Modification Package, re-distribution & re-deployments Any Assistance/Guidance would be much Appreciated.
