I'm sorry, but you're not going to like my reponse to this one. Given no other information, I would choose VB.NET based on JVPs posts alone. Filtering through the 'tone' and extra stuff of his posts, they are highly informative. I have learned over the years (been using VFP/Foxpro since the early 80s) to listen to what he has to say, not how he says it. I have benefited from his knowledge too many times to disregard any knowledge he shares offhand. He is also one of the best VFP instructors I know.

However, I am leaning towards C# too but mostly for the future portability possibilities rather than any language specific features. I also program in Delphi on a regular basis and I programmed using C many years ago. I can adjust (if I have to) to the syntax of C#. I like the information available on the web for VB.NET from Microsoft (most of that due to YAG's efforts I think or at least his making the information available to us on the UT). I wish the same type of posts that YAG does were here for VFP and C#. I know VB is easier to pickup (syntax-wise), and I like some of its features over C#, but longterm, I think more possibilities will exist using C# (or at least it appears to be so at this stage in the game). C# code is more concise (to me). I'm also seeing more examples using C# on the web (from many different sources) to grab than VB.NET so far which tilts the learning curve in favor of C#, syntax and all.

In the meantime, I am playing around with both VB.NET and C# and haven't focused in either one yet. Our business, however, will have to select one or the other at some pont in time. Who knows, we may stick with Delphi and VFP since the two have met 100% of our needs so far.

We'll see! Anyway, I was very interested in your final decision, because there does not seem to be any real strong benefit to choosing one over the other at this point, except a lot of strong personal opinions...

:o)
Tracy


>And remember, everything else being equal there is always one reason to go with C#. John Petersin.
>
>Bill