Open helgihg opened 1 year ago
Personally, I always the option to expand to a new folder where the name of the new folder matches the zip file - 7zip, but I can see how this might be annoying for tools that don't offer that.
I am open to a PR for this one.
Currently the zip file is made using the zipAfterPublish
(default) of this task when publish
ing:
https://learn.microsoft.com/en-us/azure/devops/pipelines/tasks/reference/dotnet-core-cli-v2?view=azure-pipelines
This would need to be modified so that this task doesn't create the zip and then the zip is created separately with the intermediate folder that is needed here.
When the released package is opened after being downloaded, it places the package's contents in the download folder itself, next to anything else that happens to be in the download folder. This requires the user to manually identify files that belong to the package and move them somewhere else.
The solution is to release packages containing a single directory that contains all of the contents that come in the package.