>>OK, I get that Visual FoxPro was removed from Visual Studio, but I don't recall Microsoft's mentioning that VFP would also be fading from MSDN.
>
>I've got the ear of the technical editor for MSDN magazine, and he already told me that he would be willing to get a VFP article (or more) published. Please forward your article submission to me, and I'll see about getting it in.

Thanks for the offer, Mike. I'm honored that you think I could write an article worthy of MSDN Magazine. There are many more qualified candidates than myself to author such articles, and I'm confident that my esteemed colleagues can satisfy MSDN's stringent editorial requirements.

However, I can't in good conscience encourage someone to undertake this kind of writing at their own expense, while Microsoft persists in conspicuously omitting appropriate mention of VFP at every turn. Those omissions undercut the whole effort, suggesting that one's time would be better spent looking into VFP alternatives.

Still, I don't want to discourage anyone who feels so inspired from submitting an article to MSDN Magazine. Here are some suggested catchy titles:

"Paving the Way for SQL Server with Visual FoxPro"
"Making the .NET Connection with Visual FoxPro"
"Rapid Application Development and Integration with Visual FoxPro"
"Mix, Match, and Pull It All Together with Visual FoxPro"
etc.

OK, maybe not so catchy, but I'm just trying to propose some non-threatening ways of promoting VFP that portray it as a part of the whole Microsoft gestalt, not as the outcast maverick. I appreciate your suggestion and offer to help get some articles published, but I'd rather you exerted all of your influence on the editors of MSDN to elevate VFP from the MUCH, MUCH MORE category to an explicit mention by name. Anything you can do to persuade Microsoft to correct these kinds of small but extremely damaging omissions would be a tremendous help.

Mike