Hi,
Firstly I must state that I'm currently evaluating AI so I probably don't have a right to request fetures (couldn't find a pre-sales forum

). We have however looked at quite a few options and currently we are progressing with AI as our (only) preferred choice.
The only "shortcoming" we found so far is, in our opinion, the ability to use command line switches for signtool. If I understand it right you are "forced" to nominate either a .pfx file or a combination of .pvk and .spc files for the signing process. In my view that spreads the exposure on your machine of your private key, which I believe should be kept tucked away somewhere safe. Someone might be able to correct me here as I'm no expert on digital signing.
Our current VS2008 process uses a post build event command line like this: "signtool.exe sign /a /t 'tsURL' $(TargetPath)" which picks the "best" suitable code signing certificate from the cert. store. Works perfectly but that's where it stops. AI has much better features than VS2008 to sign the msi (or exe) and also to sign other dlls you may be using but don't participate in the build, so we would like to make use of those features once we move to AI.
My suggestion is therefore to ease the requirement for cert. files and provide a textbox for command line switches for signtool.
I would appreciate any comments from AI on this one.
Regards
Bert
FOLLOW US
Get the latest news in Application Packaging