Linux executables with no file extension are missing from generated [Content_Types].xml manifest

[dpaquette]

We've encountered this a few times with task extensions that contain an Linux executable that does not have a file extension. Those files are missing from the generated content type mappings file. Files without extensions need to be explicitly entered as an Override element in the [Content_Types].xml file. If that Override is missing, some digital signing tools will remove the files or fail to sign the package in a way that it can be verified later.

Ping me internally for a repro.

[jessehouwing]

We had the same issue with the Azure DevOps Extension Tasks. @dpaquette and I worked on a temporary workaround.

https://github.com/microsoft/azure-devops-extension-tasks/blob/main/fix-manifest-file.ps1