Hi Neil,

>gain I don't know what the implications of the internal VFP plumbing are and would never claim to but MFC now has support for hosting controls and to quote the article:-
>
>"Internet Explorer simply loads the Windows Forms control itself and treats it as a COM control"

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.

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...

+++ Rick --