I upgraded to FB7, batch converted copies of my projects, and now find that Authenticode actions fail with "Error Signing File: The requested operation is not supported in this platform". I have had to drop back to FB6.
Hi Tim
This is something I have been looking into. There is next to zero information about this error from microsoft (the authors of the capicom api we use), the only difference I can see between the FB6 version and the FB7 version is the FB7 version is compiled with a unicode aware compiler. The strange thing is it works fine every time on my dev machine (windows 7 64bit). What OS are you running on? So far I have only seen this on Server 2008 R2 64bit.
FWIW, Microsoft have deprecated the capicom api, which is why In FB7 we added the SignTool actions.
I am using Windows7 64bit. After I posted the report, I realised that the item that failed was an iterator that signed everything, but earlier in the project we sign two individual items that must have succeeded. So I ran those steps again, and one succeeded (a small DLL) and one failed (a smallish EXE). The iterator always fails on the first item. And everything still works in FB6.
Do you suggest that we switch to use SIGNTOOL? I have been uing FB to sign for so long that I don’t remember what all the options are and which I need.
Hi Tim
I would recommend signtool over the Authenticode action, however that does require that you have signtool.exe on your system. Signtool.exe is part of the windows sdk, and it seems the only way to get the file is to get the whole sdk.
I may have a fix for the Authenticode action, at least it is now working for me here on a server 2008 R2 machine (our FB7 build machine) where it wasn’t before. Please test again when the next build is uploaded (hopefully later today).
Build 524 fixes the problem here, thanks. Is there an echo in here? I see each recent message twice.
Excellent thanks for confirming the fix. We’re looking in the forums issue… very weird.
The duplicate posts issue should be fixed now too.