OK - I give up, please can someone help. Used to be that you would write an OCX and then you would create an INF file. You would use the CABARC.EXE utility to create a CAB file. Then you would sign the CAB file with your suppled PVK and SPC files. Then you would load the signed CAB file on the URL site and then you would have a signed ActiveX component that people could use. Problem: When I look up how to do this today, I keep getting references to the "old way" which does not appear to work. (For example, there is no modern CABARC utlity that works, that I can find.) I have to make a very minor change to my "old" OCX and it still fully complies under VS 2008. However, I cannot find the "new" way for doing the above. Even if I have to fully re-write the code, I am willing to do that, but I still don't know what the "new" way is, nor can I find any reference to it? Seems that Authenticode Technolgy is still in business, so there must be a way to do it? Anyone out there know how to deploy a modern ActiveX component (if that is a valid term)? Thanks, GLV_West

Hi, For this question, we would like to recommend you to refer to MSDN forum, which would be more relevant resource: http://forums.microsoft.com/msdn/default.aspx?ForumGroupID=153&SiteID=1 http://forums.microsoft.com/MSDN/default.aspx?ForumGroupID=24&SiteID=1 Thanks.