>
They have taken forward some for .NET. Are they not taking it forward anymore in the future?
>

I am sure they will continue to innovate .Net. Not sure what this has to do with VFP...

<<
MS not showing respect for VFP is nothing new, though.
<<

You address your own question here.


>
I would imagine one of the main reasons that VFP cannot fully participate in the CLR and other major features of .NET is the same reason it doesn't fully participate in SourceSafe : it uses primarily binary files instead of text files.
<

I have to say that you are incorrect here, at least as far as your analysis goes. In order to view deltas in a visual sense, you need to use text files. Yes, VFP VCX's are binary. However, you can convert them to text files, which sourcesafe can work with. Source safe works just fine with binary files as well. You cannot view the deltas in a visual sense.


<<
I can certainly understand not going forward with integrating VFP into .NET in this (or the next couple) release(s) for this reason. The entire structure of VFP would have to change.
<<

Again, you reached the right conclusion, but for the reasons. The app and data models in .Net are counter to VFP's. To force VFP into that space would make it almost identical to VB. Well, VB already exists. There is no room for VFP in the .Net space...