Your opinion sparking debate?
Nah, never happens. < g >


>>I happen to agree with you about the future being .NET.
>
>The issue is pretty plain and straightforward...isn't it.
>
><
>Do you really think a "conspiracy" is being perpetuated to stick with VFP or is it just people more comfortable sticking with what they know very well vs. what they don't know?
><
>
>I think you need to look at the entities who preach that sticking with VFP is the way to go and the entities who couch learning .NET from the perspective of incorporating VFP. Look at the entities who preach the message and look at their vested interests.
>
>IMO, VFP developers should look to .NET as the future and further, should eschew as their primary basis of learning .NET any methodology that preaches incorporating VFP. i.e., if folks want to learn how to construct a web service, learn to do it in .NET. It takes about 30 minutes to learn how to do it in VFP, and quite frankly, is not at all like the way you do it in .NET. I guess the point is this: spend time learning what you don't know and less time in technologies that are pretty much viewed as legacy technologies in the world at large. The quicker a VFP developer can shed his/her dependency on VFP and become a .NET developer or a simply a developer with a marketable skill set, the better off in the long run the VFP developer will be - especially the VFP developer who is scrambling around to find work or who is flush with work but must work at a lower rate compared to other technologies...
>
>Just my opinion, but one I am sure will spark a measure of debate..< bg >