It seems to me the CLR is one of the big selling points of .Net.

You're forgetting that the market for this is the Corporate Enterprise. So there won't be one person resposible for all the code. It will be a team of developers, each with their own resposibilities.

I think that's one of the main reasons for excluding VFP from the CLR. VFP is dead in the Enterprise.

PF

>Sounds cool, but how practical is it reall? Its nothing more than writing 3 version of a FoxPro app and using different include files so you can use 3 different syntaxes. Eventually, the different syntaxes will become annoying and hard to maintain. If MS really wanted langauges to interact, they woudl have only made one langauge. Selling VB.NET and C# together is really an excuse for them to charge more for one product.