Before .Net what you said would've probably been supported by the majority. Replies like "You should use the right tool for the job to be done" and replies similar to that.

But nowadays it seems that .Net is the absolute tool. No matter what needs to be done the answer is almost certain to be .Net

It's just plain stupid.

But there seems to be an agreement amongst a majority of developers that the only tool pushed should be .Net.

Some replies will tell that it's good to add another tool to your toolkit when in fact this argument is bogus.

The real answer should always be that the tool used should fit the job to be done.

And in many cases VFP should still be that tool.


>I'm likely to be crucified for what I'm about to say...
>
>If you develop apps for internal use (ie. your own business) and you don't need to get approval from an IT committee, and vfp seems to be adequate for your needs, there isn't really a pressing need for you to jump into any bandwagon.
>
>If you WANT to learn another language, then by all means, try vb, vc, or whatever you feel intrigued about, and decide what you like best.
>
>Alex
>
>
>>I am an old FoxBASE then FoxPro user (we will NOT discuss how old).
>>
>>I use West Wind to build Web applications using FoxPro.
>>
>>I am NOT a great programmer (more of a business manager than programmer). However FoxPro has let me build some wonderful applications over the years.
>>
>>It looks like I am going to be forced to follow the crowd and go to Dot Net.
>>
>>Please give me your thoughts, should I go to VB or C # ?
>>
>>Now the truth is I am going to keep using FoxPro as long as I can, and I will buy every version of FoxPro that comes out, but it looks like I need to learn another language too.