>
Ok, I asked "what specific situation, or 'place', would you not want to use C#?" and you replied "the type of applications (database) that are build with VFP and VB" and I'm currently converting VFP database apps to C#, so I'm a bit confused why you woudln't want to use C# for that.
>

Because I did not give you the answer you wanted, you are confused. Okay, I'll explain further...

I would not use C# for database applications for the same reasons I would not use C++. I like Markus Egger's quote 'Because life is too short to program in C++'. Second, I don't like the syntax idiosyncracies (sp??) of C#. Now that is simply a preference on my part. That does not mean you are wrong for choosing to go with C# - just as I am not wrong for choosing to go with VB. At the same time, just because a developer chooses the C# route, that does not make him/her in a position of being 'more' of a .NET developer than somebody who chooses VB. Stated in in the alternative, just because somebody choose to use VB, that does not make him/her less of a .NET developer for having made that choice.


>
If the syntax differnce is not the issue, please tell me the issue, so I can avoid problems that may come up in my conversations that I've already successfully completed.
<

Two points

First, if you have "successfully completed" a conversation, there would be no need to avoid problems...right? Completion in my mind is a terminal event.

Second, the marathon racer who finished dead last "successfully completed" the race in spite of the fact that the runner did not win.

As I said, syntax differences are a factor, but they are not the only factor. There are differences in features, which are not the same as syntax differences.