Tony,

This is old news. IF VFP were part of .NET you would not have VFP 7 right now and VFP 8 would not yet be in development as VFP would tied to the .NET beta and release dates. It was decided awhile ago to separate VFP from .NET so VFP 7 could be released since it was ready and .NET was not.

VFP IS part of MSDN as is VS .NET.

If you want to move on to something else, go ahead. VFP 8 is in development and was just recently demoed at the Essential Fox conference by Microsoft. If you think VS .NET is an important issue related to the future of VFP then follow your thoughts. Personally, I think VFP meets the rerquirements of a certain segment of the development tools market and as long as it continues to meet those requirements and that aspect of market exists, then VFP will exist.

Your question should not be "VFP is not in .NET should we move on?" but rather "Does VFP have a viable market share or should we move on?"

Remember MS is in business to make money. They don't really care what tools we use as long as they are MS tools. As long as a tool makes money it will exist and be evolved. As soon as it begins to lose money it will be retired. There is no conspiracy.