>>My advice is to get VS .NET and install it.

Fine. I just received today from Microsoft a DVD of VS.NET Version 2000 - release candidate. Let me install it. :)

>>Further, keep tabs on MSDN. There are a lot of whitepapers available that are quite good.

I always forget that one... :(
I take a big look at there!


>> I plan on adding material to my site that will help VFP developes absorb VS .NET. My plan is to create materials that analyze VS .NET from a VFP perspective. This way, VS.NET will seem more familar.

I´m waiting for this kind of material for a long time... We VFPers really need it. We´re very thankful because of this effort of yours.
Please, let us know when it´s available.


>>I agree with Rick. VFP developers should give VS .NET serious consideration. It will be a year or two before VS .NET will take hold. But mark my words, VS .NET will take hold...

I see. I was talking with Ellen (EPS), and she just tell me that too. I´ll totally beginning to study C# next month...


>>>VB .NET classes look more like VFP classes since you don't have {} and ; to worry about. On the other hand, C# uses the "this" keyword - which is like VFP.
Asking which language is better in VS .NET is almost a trick question. Right now, the langauges implement the .NET framework. Regardless of which language you use, most of your code is 99% the same because you are working with framework classes. The difference is whether you use {},; or not...

humm... fine... I think I´ll give a try at C#, because I think it´s good to have some knowledge of "C" stuff...

>thanks for your thoughts.
>>Happy to share them!

thanks once again.