MSIX Packaging Tool: Installation Location issue

%3CLINGO-SUB%20id%3D%22lingo-sub-225388%22%20slang%3D%22en-US%22%3EMSIX%20Packaging%20Tool%3A%20Installation%20Location%20issue%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-225388%22%20slang%3D%22en-US%22%3E%3CP%3EI%20used%20the%20packaging%20tool%20to%20package%20up%20FileZilla.%26nbsp%3B%20When%20in%20the%20wizard%20of%20the%20packaging%20tool%2C%20I%20specified%20an%20installation%20location%20of%20%22C%3A%5CProgram%20Files%5CFileZilla%22.%26nbsp%3B%20But%20then%20I%20let%20the%20FileZilla%20installer%20install%20to%20its%20default%20location%20of%20%22C%3A%5CProgram%20Files%5CFileZilla%20FTP%20Client%22.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EMy%20bad%20on%20not%20looking%20that%20up%20first%2C%20but%20the%20package%20creation%20fails%20as%20a%20result.%20In%20the%20log%20file%20(attaching%20log%20directory)%20we%20can%20see%20that%20the%20tool%20cannot%20validate%20the%20AppXManifest.xml%20file.%20%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIn%20the%20Application%20element%20the%20Executable%20parameter%20is%20now%20%22%20FTP%20Client%5CFilezillaclient.exe%22%20and%20the%20validation%20fails%20due%20to%20the%20leading%20space%20character.%20But%20the%20real%20problem%20is%20how%20the%20packaging%20tool%20created%20that%20entry%2C%20blindly%20stripping%20off%20the%20installation%20location%20without%20considering%20this%20case%2C%20which%20should%20have%20been%20treated%20as%20a%20VFS%20path.%3C%2FP%3E%3C%2FLINGO-BODY%3E
MVP

I used the packaging tool to package up FileZilla.  When in the wizard of the packaging tool, I specified an installation location of "C:\Program Files\FileZilla".  But then I let the FileZilla installer install to its default location of "C:\Program Files\FileZilla FTP Client". 

 

My bad on not looking that up first, but the package creation fails as a result. In the log file (attaching log directory) we can see that the tool cannot validate the AppXManifest.xml file.  

 

In the Application element the Executable parameter is now " FTP Client\Filezillaclient.exe" and the validation fails due to the leading space character. But the real problem is how the packaging tool created that entry, blindly stripping off the installation location without considering this case, which should have been treated as a VFS path.

0 Replies