
Announcements
SolutionPackager 9.1.0.42 release notes mention:
Support service-side sharding of component files during extract and pack. Consequence of this when packing a solution zip: any subfolder and its files in the solution's root folder will be treated as potential component files and added to the solution.zip. Folders with names as bin/obj will be ignored during extract and pack.
Can anyone shed any light on how this might affect the unpack/pack process as part of the ALM process? i.e. will it make exporting a solution faster, will it make extracting or packing a solution.zip faster? Does it add any capabilities?
Thanks
@Anonymous- Right now, the zip file structure has not changed between the new version and old version. But, what the release notes text it saying is that it could change in the future. One thing that has changed in this version is, that it now packages all the folders with files in them into the solution zip file, apart from bin and obj. If you don't have any user created folders/content in the unzipped solution component folder, you would not notice any change in this version.
Solution Packager is a black box. So as long as you are using this tool to unwrap the solution and repackage the solution in the ALM pipeline, you probably would not notice any performance improvements/changes.
"Support service-side sharding during extract"- This could mean that the whole solution component structure could be mirrored on an per instance/solution level, rather than something that is applied only when you use the tool, which might improve the solution import/export performance. But, I am just theorizing at this point.