I looked at a programming solution for adding my publisher certificate to the Trusted Publishers store, as suggested in the ADN Dev Blog article, but I came up with a simple command line process, like this:
certutil.exe -addstore TrustedPublisher "EganBIMResources.cer"
(For you publishers out there, the actual command is: certutil.exe -addstore TrustedPublisher "%_SB_INSTALLDIR%\Resources\EganBIMResources.cer")
It needs elevated permissions to run properly (my installer does), and you need to know where the certificate (.cer) file will be when you need it. (My installer copies the .cer file to the app "Resources" folder and then adds the certificate from there.)
I have been testing it, and it seems to work fine. Does anybody have information to the contrary?
certutil.exe -addstore TrustedPublisher "EganBIMResources.cer"
(For you publishers out there, the actual command is: certutil.exe -addstore TrustedPublisher "%_SB_INSTALLDIR%\Resources\EganBIMResources.cer")
It needs elevated permissions to run properly (my installer does), and you need to know where the certificate (.cer) file will be when you need it. (My installer copies the .cer file to the app "Resources" folder and then adds the certificate from there.)
I have been testing it, and it seems to work fine. Does anybody have information to the contrary?