Different behaviour between MSIX Packaging Tool 1.2019.110 and 1.2018.xxx

%3CLINGO-SUB%20id%3D%22lingo-sub-327028%22%20slang%3D%22en-US%22%3EDifferent%20behaviour%20between%20MSIX%20Packaging%20Tool%201.2019.110%20and%201.2018.xxx%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-327028%22%20slang%3D%22en-US%22%3E%3CP%3EFor%20V%201.2018.xxx%2C%20adding%20files%20in%20the%20Package%20Editor%20assumed%20that%20they%20were%20stored%20in%20named%20folders.%20The%20symbolic%20structure%20was%20then%20created%20in%20the%20VFS%20and%20the%20file%20was%20assigned.%3C%2FP%3E%3CP%3EWith%201.2019.110%20that%20doesn't%20work%20anymore.%20Each%20file%20is%20stored%20in%20the%20root%20of%20the%20package%2C%20regardless%20of%20the%20source%20directory.%20The%20function%20%22Add%20file%22%20is%20deactivated%20for%20the%20subfolders%20in%20the%20VFS.%20The%20function%20%22Create%20folder%22%20to%20model%20the%20VFS%20is%20also%20missing.%20Adding%20files%20to%20VFS%20is%20now%20very%20complicated.%20The%20first%20step%20is%20add%20the%20file%20to%20the%20root.%20Then%20you%20can%20use%20the%20context%20menu%20to%20call%20the%20function%20%22Move%20file%22%20and%20enter%20the%20destination%20manually.%3C%2FP%3E%3CP%3EWhat's%20wrong%3F%3C%2FP%3E%3CP%3EAndreas%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-327489%22%20slang%3D%22en-US%22%3ERe%3A%20Different%20behaviour%20between%20MSIX%20Packaging%20Tool%201.2019.110%20and%201.2018.xxx%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-327489%22%20slang%3D%22en-US%22%3E%3CP%3EThanks%20John.%20Cool.%3C%2FP%3E%3CP%3EAndreas%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-327482%22%20slang%3D%22en-US%22%3ERe%3A%20Different%20behaviour%20between%20MSIX%20Packaging%20Tool%201.2019.110%20and%201.2018.xxx%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-327482%22%20slang%3D%22en-US%22%3E%3CP%3EWe%20had%20feedback%20to%20make%20it%20more%20like%20a%20%22zip%20editor%22%2C%20which%20is%20what%20the%20current%20experience%20is%20moving%20towards.%26nbsp%3B%20You%20should%20be%20able%20to%20add%20files%20contextually%20within%20the%20VFS%20and%20not%20need%20the%20move.%26nbsp%3B%20Right%20now%20the%20Create%20folder%20is%20not%20available%2C%20but%20we%20are%20looking%20to%20get%20that%20in%20a%20future%20update.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EJohn.%3C%2FP%3E%3C%2FLINGO-BODY%3E
Contributor

For V 1.2018.xxx, adding files in the Package Editor assumed that they were stored in named folders. The symbolic structure was then created in the VFS and the file was assigned.

With 1.2019.110 that doesn't work anymore. Each file is stored in the root of the package, regardless of the source directory. The function "Add file" is deactivated for the subfolders in the VFS. The function "Create folder" to model the VFS is also missing. Adding files to VFS is now very complicated. The first step is add the file to the root. Then you can use the context menu to call the function "Move file" and enter the destination manually.

What's wrong?

Andreas

2 Replies

We had feedback to make it more like a "zip editor", which is what the current experience is moving towards.  You should be able to add files contextually within the VFS and not need the move.  Right now the Create folder is not available, but we are looking to get that in a future update.

 

John.