Ok, I know this is an old topic, but for me it's new. And with all
that's been written, I still have outstanding issues. I've been able to
get .NET controls to be hosted in IE and able to deal with the
dependent assembly and strong name issues. But I've not been able to
get Javascript to communicate with the control.

In this blog post
(http://blogs.msdn.com/andrewdownum/archive/2006/01/25/ControlInBrowserProperties
AndMethods.aspx),
this person claims to very simply get javascript to call a method and
property on a .NET control hosted in IE. Using the code as shown, I
cannot get this to work. Here's another article with a simple example
that I cannot get to work
(http://windowsforms.net/articles/iesourcing.aspx).

1) Is it even possible using such simplistic code? There are no
attributes shown. There is no mention of making it COM interoperable.
It makes sense to me. IE has special behavior to load up a .NET
control. Any access to it via Javascript or whatever script, you would
think, had .NET adapters so that nothing special had to be done on the
control side.

2) If it isn't as simple as shown, then how do I get Javascript to
communicate to the .NET control?

Do I *have* to expose a COM interface and register for COM interop?
Do I *have* to implement IObjectSafety?
Do I *have* to ....?

3) Lastly, if I have to expose a COM interface from my .NET control, do
I also *have* to register it (using regasm or whatever) BEFORE it is
usable in IE? Or, can it self register upon its first initialization?
If the former is the case, this is a bit counterintuitive since one of
the reasons to host a .NET control is to deploy it on demand without
any administrative activies upfront.

All help is appreciated.

Thanks

Gary F.