Marking ActiveX safe for initializing and scripting???

[tfierens]

Hi All,

Anyone out who has had problem marking ActiveX controls safe for initializing and scripting.

I have tried :

- Deployment wizard (including the correct registry entries!)

- IObjectSafety Method

- both at the same time!

But it's no good. I am currently awaiting answer from Microsoft Tech support team, but I still have no answer.

To Keep it simple, I have created a simple activex with a single property let called Domain. UserControl11.Domain = ...

I had problem with my fully coded activex and the simplier one! I still get the same problem! When installed on the machine, it will not work unless I set the option in IE to script and initialized activex not marked as safe.

I am running out of options as it seems that to mark an activex as safe, all you need is to add a few registry entries and I have check, double check, and all entries are there.

One problem I have spotted is that the IOSafetyObject check CLSID for peristence and for IDispatch, unfortunately an error 430 is generated due to the fact of an unsupported interface which seems to be IDispatchEx. Problem though is that I have included IDispatchEx as part of the Select Case. Fine it does not generate the error anymore, but I don't think it is the solution since I still get IE to generate an error such as UserControll11.Domain is unknow property or function.

It seems to work on any machines where it has been compile one, which obviously is not a solution.

Anyone out there that has successfully mark activex, can you please let me know! I know I am not doing anything wrong as I have now read many articles from Microsoft in relation to the topic from web site, MSDN CD, and they all say the same thing. Also the project is too simple and I used the deployement wizard ensuring that all reg entries are correct. So anyone that was success full, please contact me!

Thanks!!!

Thierry

 

[kenjoswe]

Tfierens,

I have the same problem.
<...it will not work unless I set the option in IE to script and initialized activex not marked as safe.>

Let me know if you hear something about this.

/Kent J.

 

[tfierens]

Ken,

I have made some progress, but I'm still where I want to be. I have wipe all the information out of my registry out of my activex. Got rid of the lib file, etc.. created when you compile your activex. Deleted the OCX file itself that used to be compile as binary compatible.

I edited the vbp file and marked it as non binary compatible.

Open the project, turn off requires a license file and recompile it. Quit VB, went back in and this time I compiled it as binary compatible.

Build a cab file, with vb6 sp3 and now it works fine.

I have not had much chance to test it more, but I obviously understand why there may be some step that are completely uncessary. I just wanted to narrow it down.

If you get a chance before I Do about the following, please let me know:

- Add license and recompile
- maybe all I needed to is to wipe the registry and no other steps?

Please note out of 3 activex controls: I only got it to work for 2 of them? The 3rd one, I am hoping that by rewritting it and improving the code it, it may work. The one I cannot get to work was very good, but too messy inside in order to modify the code, so I decided to rewrite correctly. Once done, we'll see what happens.

Hope this help (somehow!!!)

Regards,

Thierry