Michael Morten Sonne | Microsoft MVP

We see "Exception calling "Initialize" with "1" argument(s): "Object reference not set to an instance of an object."" too in our automation! We love the bugs like this too: https://github.com/microsoft/Microsoft365DSC/issues/4720...

For now, when adding files all supported for signtool.exe (Microsoft) is added... is this needed?

Hi @ixm7 , Thanks for the report here! Tested it via the tool on my own laptop right now, but tested some senarios based on the steps you provided here,...

I see the error on a other client else not tested on (tested the installer and so on in Windows Sandbox) - intresting find @ixm7 - I will see what...

I have pinged the product team for Trusted Signing about the error here, as it looks like internal the bug happens in the lib. Regarding the features you mention for...

> The error: **Dlib file not found at: .\Tools\Azure.CodeSigning.Dlib.dll** is an exception triggered in your code, not on Azure's side: > > It fine runs here in that combination via...

> The tool already remembers the endpoint options. In the same way, users would expect remembering process options. > > This would also facilitate calling the tool via a **command...

> The error: **Dlib file not found at: .\Tools\Azure.CodeSigning.Dlib.dll** is an exception triggered in your code, not on Azure's side: > > Added some more logging for what I get...

Hmm strange it works differently based on what I see when I test it and the output I getting for the .dll... I will change the code, thanks for the...

> The relative path is relative to the **current working directory**. It may not be the application directory. > > So consider changing the code to build the path using...