Word add-in.. OK, Authenticode do I have to?

[BadgerByte]

Hey all,

I've created an add-in for Microsoft Word and followed the instructions in the following link to create a shim which resolves managed code issues.

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnoxpta/html/odc_comshim.asp

However, though I've been desperately trying to ignore it.. It tells me that the shim must be signed using authenticode and that a test certificate should not be deployed commercially.

Do we really have to pay verisign good money (of which we have very little) to be able to deploy this add-in?

Can anyone provide more insight into Authenticode in general? it's a very grey area for me.

Has anyone else developed an add-in who can provide any advice?

Any help would be greatly appreciated..

Regards,

Andy

 

[mafrosis]

This is a question Ive been wondering about myself! Ive written an addin (SmartTag) for Word which has a very generalised function and could be of use to many organisations - we're still in final testing but im not sure of the approach for deployment..

What I have been doing for testing purposes is signing the code using caspol.exe and inserting Registry entries for the SmartTag manually - this seems to work ok but I need to test deployment more fully.

The example I copied was in the VB.NET sample from the SmartTag SDK:
http://tinyurl.com/qccby

Hope thats some help..
mafro