>>>>>Just think of it as a big install <g>: do an administrative install of IE4 during your install, then an administrative de-install of IE4, also during your install. Viola. <g>
>>>>
>>>>Yes, but we would like to have it as an OCX + required DLLs components instead of a full install of MSIE. In the client corporate decision, MSIE won't be certified until one year. So, it's difficult to justify a full install of MSIE for our application.
>>>
>>>The WebBrowser control has no ocx file, but only DLL.
>>
>>because it is not a real control - it just exposes some of the PEMs of MSIE
>>
>>Arnon
>
>Are you sure? It works even after you uninstall IE. After all an ocx is a dll internally, isn't it?
>
>Vlad

It work only because you have installed it(full) and all needed entry was made in the windows registry.

May be, if you take the dll and make all msie entries in the registry you probably able to use it.

But i don't think MS give you the permission to use this dll without installing MSIE on the client machine, you know that this dll is not public domain even if the MSIE is free.

:0)