>>From what I understand, it's not a resources issue, but rather that the datacentric orientation of the language would have to go. It's not that VFP7 is not .net compatible, but that it's not in the CLR, and if I read the stuff right, that is a requirement for it to be considered a .net language.
>
>Cy,
>
>That is until MS releases Word.NET :-)

Pardon my ignorance, but shouldn't Solitaire.Net and Minesweeper.Net come first?

(answer to the voice from the audience: No, Edlin.Net will not be included in this version, maybe in SP1)