Hi Rick,

SNIP
>I don't think anyone outside MS knows at this point whether VFP will participate in the CRL or not. There was some interesting speculation about this in the thread David Stevenson started last week.

Yes there was interesting speculation in that thread, but I must admit I was bothered by. . .
The bottom quote David included said (something to the effect of) "shared by all of the languages in Visual Studio".

Despite this quote there was/is still worry that VFP is possibly *not* included for compliance/usage of CLR.

*IF* this worry is legitimate then (to me) it can only mean that there is a concern that VFP may not be included in Visual Studio. IF the statement in question is of concern because MS has said similarly before, only to have VFP excluded when (whatever it was) delivered, then the real issue is that WE NEED MS to be far more careful and far more accurate and to deliver what they say when they say such things is 'official' settings.

If we are to get upset every time VFP is left OUT of any marketing/announcement material yet mistrust/question when clear statements are made, then we are clearly in a no-win situation.
Given the choice I would rather push MS to DELIVER WHAT THEY STATE (in this case, that *all* programming languages delivered with VS will comply with CLR) than to simply "accept" that they may have mistaken.

Cheers,

Jim N