>
Add to that the ability to wrap VFP stuff in Web Services callable from .NET and the possibilities for bridging the gap and being valuable to even more companies increase.
>

This is very important and key to the issue of putting all one's eggs in the same basket.


>I agree that anyone chosing to ignore .NET is really rolling the dice on a big gamble. Some, however, would say that the big gamble is to put all your eggs into the .NET basket. Considering that Microsoft is betting the company on it, it seems like a pretty good gamble, really -- but we don't have to put all the eggs there yet.
>

I look at the potential harm. The harm is much greater if VS .net is ignored. I also think there will be great harm if VFP is dumped. The smart VFP developer is going to continue to use VFP and leverage that skill to learn VS .net.

>At CoDe Magazine, we have wrestled the past year with how to provide coverage of "the new stuff" while continuing to support the VFP community with in-depth technical articles. We are still adjusting as we go, but have concluded that one of the best ways to support the VFP community is to explain .NET in-depth and show how VFP can work alongside it when possible, in addition to general architectural topics and a small number of VFP-only articles.
>

Agreed...