>My question is how does COBOL fit into CLR and VFP doesn't?

How does it fit? Like a square peg in a round hole comes to mind. I think it was ported for the exact same reason VB was ported. The spent ALOT of money on this, and they need to attract languages left and right (or in VB's case force them onto it). There's a whole slew of reasons VFP didn't get moved, that the community has outlined as technical reasons. The other reason is that when it comes to lanugages (aka, user bases) to entice on to the CLR, you've got bigger fish to fry than VFP (like COBOL).