>>That's because Internet explorer is not an application interface, but a document container. It's an ActiveDocument host, and support of this is very difficult to do. And even in IE it works worth a s*it. It's nice to demo but I have yet to run into anybody actually using this technology. Heck Microsoft did (GotDotNet shared projects) and stopped - in fact it killed the whole GotDotNet concept over it.
>
>>There's also the whole issue of security that will likely be a nightmare with control access at this level because VFP will not support hte .NET security model - so there's no way for VFP to be a trusted caller over COM.

Is .NET really that poor of a system that it can't concievably interact nicely with other systems? And... if it is why would I want to bother using it at all? You really leave .Net in a rather unfavorable light here. Listening to you I have to wonder why I would consider using .NET with VFP at all.

But... I don't really buy that. On a simple google search I see tons of examples of .NET\winform controls being hosted in IE. If it's that hard why do so many places say it's so easy to host them in IE? I currently host IE in VFP just fine... so it only follows that it should be posible to host winform controls in a more direct fashion.

>>Frankly I fail to see the significance of running an Avalon UI INSIDE of a VFP application? Avalon is different enough that if you want to take advantage of this functionality you will need an environment that supports the richness of this model.
>
>Avalon is VERY different in how it handles the graphics layer and it's not really 'more of the same'. it's kind of like asking to embed a Windows control into a DOS application...

I don't recall anyone here even mentioning the Idea of hosting Avalon in a VFP form. It sounds like the ability to call and interact with an Avalon form will be one of the things we are getting in Sedna. Avalon is further out in the future, and you may be right it may not be doable on a VFP form. We were talking about hosting current .NET winform style controls on a VFP form, a much different animal from what I can see.

.NET programming really isn't an option for the 90% of work I do. Maybe some day in the future it will start to have some of the features that make VFP such an indispensable tool for me, but .NET has a long long way to go to even come close. In the mean time, I would love to be able to use some C# in the work that I do. There are some things that would be easier for me to do in C#. Providing a way to host winform controls on my forms would be a great step in that direction. But... if it's too hard or .NET is too bloated or incapable of a system to be able to do that, I can live with out it. (I just find it hard to believe that it is.)