Evan,

>Once again from David's Devcon report here is the official word on the CLR (common language runtime): "He ended with the statement that CLR support is one of the options for VFP8, but dialog with the VFP community is needed before that decision can be made."

Ohhh... it seems they're passing the burden to us. Why the need for a dialog first? Are they not sure yet of the impact of CLR and .NET technology? How it gonna cripple those dependent in VFP only if .NET is a smash hit? Good thing if .NET will be a flop. And why it is only an option in VFP8, is it not a necessity? They were the ones knowing the technology in advance, isn't it?

Sure, VFP is included in VS.NET but for Components and WEB Services only. BTW, how about WEB Forms / ASP+?

>Any thoughts on this. If we get CLR we will be one version behind the rest of the VS languages in this option.
>On the flip side, VB is 3 versions behind VFP on getting inheritance.

You know it Evan. You will survive and do good in VB even without inheritance. But on the other side, you can't build .NET enabled application in VFP foundation without CLR.

If in the end, it comes up that CLR is a necessity, better of MS VFP Team saying that they ran out of time why it is not yet included in 7.0.