VFP is not part of the Common Language Runtime, nor will it ever be (probably). There was a huge discussion about this a while ago. Maybe someone can post the thread? Also look on foxwikis about this topic.
Yep, I've watched those threads in the past. I think I agree that reworking VFP to fit the CLR would be at too great a loss of other functionality (can't remember all the facts) but someone here raised the question of whether or not it would be possible to add functionality to VFP giving the choice to build either as a VFP runtime or a CLR runtime. This is an interesting idea, but I have no concept as to what it would take to achieve this. It's probably not even worth the cost of going through all that anyway... we need OOP menus and built-in Crystal Reports first, right? *g*
>So .NET will Interop with FoxPro in two ways:
>(1) Interop Services. Creating wrappers around COM
>(2) Web Services (ie SOAP/XML)
>
>To start playing with it, I would recommend installing IIS 5.0 and the .NET SDK which provides many examples. And of course the Strahl article.
>
Yeah, I'll probably install .Net on one of my test machines one of these days ...
VFP6 SP5, VFP8 SP1, VFP 9 SP 1 and Win XP SP 3 (unless otherwise specified)
www.wulfsden.com