Closed FSharpCSharp closed 3 years ago
The reason for this is a missing msvcr120.dll in c:\windows\system32 Seems like I was a little too aggressive on saving space. The vcredist will be added to the next version of the generic image. I will add a check in Sign-BcContainerApp to check whether the dll is there and if not, then do a just-in-time install of vcredist, then this should work with the existing versions as well.
Shipped in BcContainerHelper 2.0.0
Describe the issue In a newly created container with the new additional option "FilesOnly" the signing fails with the following error:
SignTool Error: This file format cannot be signed because it is not recognized.
Scripts used to create container and cause the issue
Full output of scripts
Screenshots
Additional context Unfortunately this error occurs with all versions.