I don't see that as a problem. I don't think many people working in FoxPro want to compile to the clr.
I think the entire concept of .NET supporting many languages is a bit of a joke, to be honest. I don't believe there is a business need to write Cobol on PCs.
.NET is about VB.NET and C#. The rest is all sales pitch.
And VB.NET is a major leap forward for VB.
There most definately is a business need to write Cobol on PCs. I work for an Insurance company, and our policy admin system was ported to the PC platform using Microfocus cobol. The new version is switching to Fujitsu Cobol, and the next release after that, to the .NET version of Fujitsu's cobol, which will allow us to develop interfaces and extensions using virtually any language .NET supports.
This is a package that cost us over $1 Million to purchase and our in house developers will be using .NET to maintain/extend the system, with a great deal of the work being done in Cobol. Even at that cost, the ability to run it on a $25,000 server vs the $1 Million a year cost of our mainframe (which we eliminated completely with this move) has more than paid for itself.