ActiveX Control is signed but IE is still blocking it - Why?



I created an Active X component that IE calls whenever a file or link or
certain MIME type is encountered.

This ocx lives on the client machine and is registered in the registry
(which is how IE finds it). Everything works fine except that IE blocks the
running of the control at a security of "Medium" and above.

I used signtool and the wizard to sign the ocx and everything went fine.
When I do a "properties" on the ocx it says the signing is fine and the
certificate is fine as well.

The problem I have is that whenever I hit a webpage or link that triggers
the control IE blocks it from running.

I am running Windows XP and IE 7.

.



Relevant Pages

  • Pocket PC 2003 Emulator OCX
    ... What i wanted to do is to build the same ocx for the ... I've created a new project using EVC 4.0 and gave the same names as on my ... I looked up in the emulator's registry: under HKLM\CLSID there is a key ... Why the hell is it telling me the control is not registred, ...
    (microsoft.public.pocketpc.developer)
  • Re: Creating OCX files
    ... Even so, simply adding Control ... actually added these keys to registry when you run regasm on component ... means you can also implement OCX if you manually implement all the ... (unless it would be added to VB6 runtime at some point). ...
    (microsoft.public.dotnet.general)
  • Re: Windows form application problem
    ... I thought I saw just plain .ocx as the extension. ... Now I have to try to find that control and see what I can come up with. ... Gerry O'Brien ... >>> reference, rebuilt, re-referenced and rebuilt.. ...
    (microsoft.public.dotnet.languages.vb)
  • Re: ActiveX Download Conflict Directory
    ... changes for the same named OCX or packaged files, ... > existing control and update the control (rather than install a second, ... downloaded on client machines by ASP. ...
    (microsoft.public.vb.controls.internet)
  • Re: executionEngineException
    ... No, this is not a solution, by doing this you are fooling the system by pretending that the component can be loaded into the MTA and COM will load it into the newly created thread which enters the MTA by default, but beware you are fooling yourself, here is why: ... An OCX is not designed to be hosted in the MTA, ... - OCX's must be hosted in a ActiveX control container, an MTA is not such container, the UI thread running a Windows Form is a valid container. ... set the Threadingmodel back to apartment and initialize your thread to enter an STA by setting the ApartmentState attribute to STA2. ...
    (microsoft.public.dotnet.framework.interop)

Loading