Specifying the install directory in the MPT

%3CLINGO-SUB%20id%3D%22lingo-sub-810062%22%20slang%3D%22en-US%22%3ESpecifying%20the%20install%20directory%20in%20the%20MPT%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-810062%22%20slang%3D%22en-US%22%3E%3CP%3EI%20finally%20had%20time%20to%20track%20this%20one%20down.%3C%2FP%3E%0A%3CP%3EWhen%20using%20the%20MSIX%20Packaging%20Tool%2C%20there%20is%20an%20option%20to%20specify%20an%20installation%20directory.%26nbsp%3B%20It%20seems%20that%20it%20is%20necessary%20to%20specify%20a%20directory%20that%20already%20exists%20before%20you%20get%20into%20the%20monitoring%20mode.%26nbsp%3B%20I%20have%20found%20that%20if%20I%20specify%20a%20directory%20that%20doesn't%20exist%20(using%202019.701)%2C%20the%20following%20occurs%3A%3C%2FP%3E%0A%3CUL%3E%0A%3CLI%3E%26nbsp%3BThe%20app%20is%20captured%20as%20VFS%20anyway%3C%2FLI%3E%0A%3CLI%3E%26nbsp%3BNo%20shortcut%20is%20automatically%20detected%20(in%20my%20test%20the%20shortcut%20was%20placed%20in%20Common%20Appdata%5Cvendorname%20folder.%20The%20lnk%20file%20was%20captured%2C%20but%20no%20shortcut%20detected.%3C%2FLI%3E%0A%3CLI%3E%26nbsp%3BIf%20you%20manually%20ask%20to%20add%20a%20shortcut%2C%20the%20tool%20noticies%20the%20program%20exe%20and%20offers%20to%20make%20a%20shortcut%20for%20that.%26nbsp%3B%20If%20you%20do%2C%20it%20places%20that%20shortcut%20on%20the%20desktop%20(however%20that%20doesn't%20matter%20as%20it's%20just%20looking%20for%20a%20shortcut%20and%20isn't%20going%20to%20place%20it%20on%20the%20desktop%20when%20the%20package%20is%20deployed).%3C%2FLI%3E%0A%3CLI%3E%26nbsp%3BThe%20resulting%20package%20has%20only%20the%20store%20logo%20in%20the%20assets%20folder.%3C%2FLI%3E%0A%3CLI%3E%26nbsp%3BThe%20resulting%20package%20has%20no%20icon%20for%20the%20AppInstaller%2C%20so%20you%20see%20an%20empty%20blue%20square.%3C%2FLI%3E%0A%3CLI%3E%26nbsp%3BAfter%20the%20package%20is%20installed%2C%20there%20will%20be%20no%20shortcut%20anywhere.%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3CP%3EWhile%20there%20is%20question%20in%20my%20mind%20as%20to%20if%20VFS%20should%20be%20the%20default%2C%20this%20behavior%20is%20problematic.%20The%20packaging%20tool%20should%20either%20scold%20me%20when%20I%20type%20in%20a%20non-existent%20directory%20or%20(better)%20just%20make%20it%20for%20me%20before%20entering%20monitoring%20mode.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-810398%22%20slang%3D%22en-US%22%3ERe%3A%20Specifying%20the%20install%20directory%20in%20the%20MPT%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-810398%22%20slang%3D%22en-US%22%3E%3CP%3EI've%20submitted%20this%20in%20the%20feedback%20hub%20as%20a%20bug%202%20weeks%20ago%20(no%20answer%20yet).%20Good%20to%20know%20I%20am%20not%20the%20only%20one%20with%20this%20problem.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-811512%22%20slang%3D%22en-US%22%3ERe%3A%20Specifying%20the%20install%20directory%20in%20the%20MPT%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-811512%22%20slang%3D%22en-US%22%3E%3CP%3EThanks%20for%20reporting%20this%20issue!%3C%2FP%3E%0A%3CP%3EWe%20will%20be%20looking%20into%20it%20for%20future%20releases%20of%20the%20tool.%20For%20now%2C%20please%20continue%20to%20use%20the%20manual%20workaround%20you%20mentioned%20of%20ensuring%20the%20directory%20exists.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3ESorry%20for%20the%20inconvience!%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThanks!%3C%2FP%3E%0A%3CP%3EJames%3C%2FP%3E%3C%2FLINGO-BODY%3E
MVP

I finally had time to track this one down.

When using the MSIX Packaging Tool, there is an option to specify an installation directory.  It seems that it is necessary to specify a directory that already exists before you get into the monitoring mode.  I have found that if I specify a directory that doesn't exist (using 2019.701), the following occurs:

  •  The app is captured as VFS anyway
  •  No shortcut is automatically detected (in my test the shortcut was placed in Common Appdata\vendorname folder. The lnk file was captured, but no shortcut detected.
  •  If you manually ask to add a shortcut, the tool noticies the program exe and offers to make a shortcut for that.  If you do, it places that shortcut on the desktop (however that doesn't matter as it's just looking for a shortcut and isn't going to place it on the desktop when the package is deployed).
  •  The resulting package has only the store logo in the assets folder.
  •  The resulting package has no icon for the AppInstaller, so you see an empty blue square.
  •  After the package is installed, there will be no shortcut anywhere.

While there is question in my mind as to if VFS should be the default, this behavior is problematic. The packaging tool should either scold me when I type in a non-existent directory or (better) just make it for me before entering monitoring mode.

 

2 Replies

I've submitted this in the feedback hub as a bug 2 weeks ago (no answer yet). Good to know I am not the only one with this problem.

Thanks for reporting this issue!

We will be looking into it for future releases of the tool. For now, please continue to use the manual workaround you mentioned of ensuring the directory exists.

 

Sorry for the inconvience!

 

Thanks!

James