OCX, Certificates and Warnings

Hello

I am developing an add-in for Word using VBA. It uses 2 ActiveX components (as ocx files) that I created using VB6.0.

I have limited the access to the properties and methods to make the ActiveX components safe, implemented IObjectSafety for each ActiveX component, signed the ocx files as well as the VBA code with a certificate that I have installed on my machine in the Trusted Root Certificate Authority. The certificate was created with makecert.exe.

I have tried every option that I can think of with regards to certificates and code signing and I am still getting the message “This application is about to initialize ActiveX controls that might be unsafe....” etc.etc. How does Microsoft get around this for their add-ins that use ActiveX components?

Would this message go away if I was to purchase a proper certificate from a registered Certificate Authority or will I still get this message? I have read many posts regarding ActiveX components and web pages but I havent seen anything that deals woth Word.

Any help would be greatly appreciated.

Is this just on your system or is the problem on any system?

I haven't checked out the signed code on other systems yet. Does it sound like it's an unusual problem?

Sounds like its not getting signed. The office Cert tool makecert.exe is for signing VBA project code not complied dlls and ocxs. Perhaps this is why

That's an interresting point. It seems to have worked because when I checked the properties of the file, the certificate was attached, however, could it be the wrong type of certificate? Is that possible?

[color=navy]Usually, eveerytime you make a code change and recompile you have to resign the exe too.

How are you signing it?[/coor]

I haven't recompiled the code. I'm happy with the component (for now). I'm using signcode.exe to sign the ocx file.

Signcode.exe is the one to use but its a free signing utility.
See here for its arguments and options:
http://msdn2.microsoft.com/en-US/lib...cy(VS.80).aspx

And the one for Makecert.exe:
http://msdn2.microsoft.com/en-US/lib...y3(VS.80).aspx

And cert2spc.exe:
http://msdn2.microsoft.com/en-US/lib...8f(VS.80).aspx

Thanks for those links. I have seen, read and followed the instructions on the pages but I was still getting that message. I think I will start again from scratch - delete all the cert, spc, ctl (etc) files I creatred and see what happens. I'll post the results when they're in.

In the meantime if their are any more suggestions, I would love to hear them.

I think you need to do it one step at a time. Get the first ocx to be accepted safly and then the other. Then sign the vba project etc. How did you make the Word addin?

It's really a VBA project that is installed in the Word startup folder. I will try it one step at a time.