>You might want to think it twice before jumping to C# instead of VB.NET.
>
>VB.NET is more suited than C# for the type of applications that you currently build with VFP. In other words, VB.NET is more suited for typical business applications while C# is suited for more system-type of utilities.

Hmmm you mean that Kevin McNeish made a bad decision when he chose to make his framework (Mere Mortals) with C#?


>Yes, it is true that the .NET framework was built using C#, and so will lots of system utilities for .NET (components, tools, and so forth.) If you think about it, the same was true before .NET. For example, Windows and VFP were build using C/C++, yet, that didn't make C/C++ better suited for typical business applications. VB and VFP were/are far better for these type of applications.

I don't know .Net yet but I had the impression that the language used is not really the issue but that the framework does the hard work. To me it looks like it would only be a matter of using whatever .Net language and call the appropriate methods in the framework.


>To me, choosing C# over VB.NET due to the advanced features is like choosing C/C++ over VFP just because C/C++ is closer to the Windows API than VFP.

Don't compare oranges with apples. We're talking about something completely different here. .Net is about different languages having the ability to all use the same framework. So at some point it becomes a matter of choosing one language over the other. I gave my some of the reasons why I'll prefer C# over VB.Net


>I've heard people saying "I would much rather use Delphi or C# than VB.NET" and a lot of times this is just based on the "let's hate VB" mentality. That's OK if that is what you want. Just make sure that is *really* what you want.

That too won't hurt. I feel really comfortable doing some VB bashing :-D
You see I never used VB so I don't mind nor care what happens to it. But considering that VFP has been bashed from VB users for a while now. I hope that my contribution to VB bashing will make them feel some pressure.

One thing is sure and it's that those already using VB will push really hard to keep it going. So that's why you'll see lots of stuff to convince developers that VB.NET is the way to go. I think that it would be crazy to not do so. If a developer is confronted to the fact that he have to change from a programming language to another then perhaps he won't only change the language but also the environment. So even if C# is superior to VB.Net you'll never see advertisement telling VB users to switch to C#. Why I say never because There would have never been a VB .Net if it would have been the case.


>Ken Levy gave a nice list of VFP-like features that VB.NET provides and C# does not. Take a look at message #652549

Normal to try to keep the VB crowd. It's much bigger than the C# crowd.

You can't please everyone so that's probably why MS markets VB.Net to VB 6 and VFP crowd, C# to Java, C++ and VFP crowd (looks like MS really wants to get VFP crowd on something else as a programming language) and VFP to ... evidently VFP crowd.

So in the end everyone's happy... Not really the VFP crowd is a tough bunch to please <g>