PSF Tool @ TIMOTHY MANGAN - any limitation of size to Inject Fixups to the MSIX package

%3CLINGO-SUB%20id%3D%22lingo-sub-2641166%22%20slang%3D%22en-US%22%3EPSF%20Tool%20%40%20TIMOTHY%20MANGAN%20-%20any%20limitation%20of%20size%20to%20Inject%20Fixups%20to%20the%20MSIX%20package%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2641166%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20%3CSPAN%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F146612%22%20target%3D%22_blank%22%3E%40TIMOTHY%20MANGAN%3C%2FA%3E%2C%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EDo%20we%20have%20any%20limitation%20of%20size%20to%20inject%20the%20fixups%20into%20the%20MSIX%20package.%20Right%20now%20we%20are%20working%20on%20one%20application%20of%20size%203GB%20which%20contains%20around%2040%2B%20shortcuts%2C%20most%20of%20the%20entry%20points%20were%20exe%20with%20arguements%2C%20when%20we%20run%20the%20PSFTool%20of%20after%20installation%20phase%20of%20the%20application.%20the%20psf%20tool%20suggested%20only%20psflauncher%20and%20fire%20redirection%20fixups%2C%20later%20when%20we%20ran%20to%20%22check%20for%20new%20components%22%20option%2C%20here%20in%20this%20section%20corresponding%20to%20SHORTCUTS%20it%20showed%20only%203%20shortcuts%20out%20of%2040%2B%20shortcuts%20and%20once%20after%20creating%20the%20package%2C%20if%20I%20open%20the%20config.json%20file%2C%20it%20has%20around%203.7%20lakh%20lines.%20which%20is%20very%20huge%2C%20most%20of%20the%20lines%20belongs%20to%20File%20Redirection%20Fixups%20along%20with%20dll%20information.%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3EAnd%20one%20more%20thing%2C%20this%20particular%26nbsp%3Bapplications%20installation%20directory%20is%20like%20C%3A%5Cabc%2C%20it%20is%20not%20installing%20the%20application%20to%20c%3A%5Cprogram%20files.%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3ECould%20you%20please%20advise%20how%20to%20handle%20this%20situation%3F%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2641676%22%20slang%3D%22en-US%22%3ERe%3A%20PSF%20Tool%20%40%20TIMOTHY%20MANGAN%20-%20any%20limitation%20of%20size%20to%20Inject%20Fixups%20to%20the%20MSIX%20package%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2641676%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F1099635%22%20target%3D%22_blank%22%3E%40Siva116%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EObvious%20answers%3A%3C%2FP%3E%0A%3CUL%3E%0A%3CLI%3EThere%20should%20not%20be%20a%20limitation%20on%20size%20of%20either%20individual%20files%20or%20total%20file%20size%20in%20MSIX%20in%20general.%3C%2FLI%3E%0A%3CLI%3EThese%20shouldn't%20be%20one%20in%20PsfTooling%20either%2C%20but%20bugs%20do%20happen.%3C%2FLI%3E%0A%3CLI%3EThe%20json%20created%20by%20PsfTooling%20is%20certainly%20not%20optimized%20as%20it%20attempts%20to%20be%20very%20specific.%26nbsp%3B%20The%20json%20created%20by%20TMEditX%20would%20be%20much%20smaller%20as%20we%20now%20see%20that%20when%20we%20apply%20fixes%20we%20almost%20always%20want%20to%20apply%20them%20to%20any%20process%20running%20in%20the%20container.%26nbsp%3B%20Eventually%20I%20may%20migrate%20that%20method%20into%20PsfTooling%2C%20but%20I%20am%20waiting%20to%20see%20if%20I%20get%20any%20complaints%20that%20this%20method%20is%20too%20simple.%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3CP%3ELess%20obvious%2C%20and%20maybe%20not%20answers%3A%3C%2FP%3E%0A%3CUL%3E%0A%3CLI%3EThere%20is%20an%20open%20bug%20in%20PsfTooling%20against%20an%20app%20installing%20to%20a%20private%20folder.%26nbsp%3B%20Unfortunately%20I%20was%20unable%20to%20reproduce%20the%20issue%20so%20it%20is%20on%20hold.%26nbsp%3B%20Quite%20possibly%20there%20is%20a%20bug%20there%20as%20Psf%20Support%20for%20VFS%5CAppVPackagingDrive%20changed%20at%20some%20point%2C%20and%20it%20would%20be%20advised%20to%20cajole%20the%20install%20into%20a%20Program%20Files%20folder.%3C%2FLI%3E%0A%3CLI%3EThe%20additional%20shortcuts%20should%20have%20shown.%20What%20version%20of%20PsfTooling%20was%20used%3F%3C%2FLI%3E%0A%3C%2FUL%3E%3C%2FLINGO-BODY%3E
Contributor

Hi @TIMOTHY MANGAN,

 

Do we have any limitation of size to inject the fixups into the MSIX package. Right now we are working on one application of size 3GB which contains around 40+ shortcuts, most of the entry points were exe with arguements, when we run the PSFTool of after installation phase of the application. the psf tool suggested only psflauncher and fire redirection fixups, later when we ran to "check for new components" option, here in this section corresponding to SHORTCUTS it showed only 3 shortcuts out of 40+ shortcuts and once after creating the package, if I open the config.json file, it has around 3.7 lakh lines. which is very huge, most of the lines belongs to File Redirection Fixups along with dll information.

And one more thing, this particular applications installation directory is like C:\abc, it is not installing the application to c:\program files.

Could you please advise how to handle this situation?

4 Replies

@Siva116 

Obvious answers:

  • There should not be a limitation on size of either individual files or total file size in MSIX in general.
  • These shouldn't be one in PsfTooling either, but bugs do happen.
  • The json created by PsfTooling is certainly not optimized as it attempts to be very specific.  The json created by TMEditX would be much smaller as we now see that when we apply fixes we almost always want to apply them to any process running in the container.  Eventually I may migrate that method into PsfTooling, but I am waiting to see if I get any complaints that this method is too simple.

Less obvious, and maybe not answers:

  • There is an open bug in PsfTooling against an app installing to a private folder.  Unfortunately I was unable to reproduce the issue so it is on hold.  Quite possibly there is a bug there as Psf Support for VFS\AppVPackagingDrive changed at some point, and it would be advised to cajole the install into a Program Files folder.
  • The additional shortcuts should have shown. What version of PsfTooling was used?

Thanks for the Reply @TIMOTHY MANGAN
I am using the latest version 4.13 from Microsoft Store.

What is the app? I'd like to reproduce the issue.
Hi @TIMOTHY MANGAN,
Please find the below mentioned app name.
Name: WebFOCUS 82 App Studio
Version : 8.2.0.7
Author: Information Builders, Inc

Thanks a lot for the time that you are spending in resolving issues on MSIX.