Authenticode with compiler variables

[rasmusw]

I am signing my installer with authenticode. This works fine.

I would like to change which signature is used based on the OEM build I am performing.

So I added compiler variables for the signature public key, certificate, URL and password configuration in the Authenticode signature properties.
This doesn't seem to work.
I tried hardcoding the Password (it's understandable if this wouldn't accept the compiler variable), but still no luck.

Is this a limitation of IA or am I doing something wrong?

For example I have set the certificate file to "#SIGNATUREPRIVATEKEYFILE#", and am defining that with the miabuild command line as such:

Code: Select all

miabuild "c:\development\buildtemp\Installer\installer.mpr" /o="c:\development\buildtemp\installer\output" /b=1 "SIGNATUREPRIVATEKEYFILE=\\server\share\certificate files\private keyfile.pvk"

[MichaelNesmith]

To be honest, I am not sure compiler variables are resolved in authenticode fields. I can add this as a feature request to R&D.

[rasmusw]

That would be great, thank you.

In general I think all fields should support either regular variables or compiler variables, or both.

[MichaelNesmith]

As it turns out, these fields do support compiler variables.

It may be that the native Microsoft tool we call for code signing cannot understand UNC paths.