>
First of all, my intent isn't to marginalize VB. When it comes down to it, I believe you can be as successful with .NET using either C# or VB.NET and ultimately it's a matter of personal preference.
<

Your comments about the extra "syntax" baggage with regard to VB does not fit -does it??? IMO, curly braces, case sensitivity, and having to terminate your lines with semi colons make for "extra baggage". Why don't you address this point? In addition, I would like to see you address the inference you made that VB .NET was "less" specifically designed to work with the .NET framework.


<<
From a practical perspective I was a C developer on the Unix platform before working with Fox...and I've also had to work with Java along the way...I like the fact that C# is syntactically similar to both C++ and Java which actually lessens my learning curve!
<<

I don't see how this is all that relevant. If you like C that much, why didn't you elect to go with C++ or Java?? If you like the Fox syntax, I would agree that your preference is reasonable. However, it boggles the mind as to why you would go back to something that looks more like C/C++/Java as opposed to using a langauage like VB .NET - which is essentially VFP without the native data engine. VB .NET is a lot more similar to VFP than C# is.

FWIW, my exposure to C/C++ is VERY limited. And, I have ZERO experence with Java. My learning curve with C# was nil. With that said, to intimate that C/C++/Java necessarily lessens the learning curve greatly overestimates and over-exagerates what C# is... More to the point, it over-estimates and over-exagerates technically superior features that C# has when for the most part - database application developers are not likely to use those features in the first place...i.e., any additional pointers C# can access (assuming I would ever have the need to access pointers) is not a compelling feature of C#

Quoting from your ad...

The power of C++???? First, if the power of C++ was that important - wouldn't people use that instead of VFP? Even if C# does have all the power of C++ - which I am not convinced it does - would that unused power be worth giving up the syntax in VB .NET which is more similar to VFP? I think not...

<<
Many VFP developers I've worked with are also in this same position.
<<

I have no basis to dispute this. However, I would bet the vast majority of VFP developers would probably be more comfortable with VB. YOU might be more comforatable with C# - but to use that as a basis for what you average VFP developer would be more comforatable with is a specious argument at best.

IMO, when most of the work is done with the framework - the language is a secondary issue. I get a bit of a chuckle when in your pitch to sell $2K training that you bill C# as an "elegant" language. I laugh because 1: C# is not an elegant language given all of its "legacy" attributes. 2: to emphasize a language completely misses the point. I would be willing to bet that everything you have accomplished in your "classes" could have been just as easily accomplished in VB .NET.

I am not criticizing your choice of langauges. However, the inference you make is that somehow, VB .NET is inferior to C# is ridiculous. IMO, it smacks of an elitest approach to things. If in your framework - which is designed for database applications - you can give me 1 solid TECHNICAL reason you chose C# over VB .NET - then I might be able to understand your position.

To couch it from the stand point that C# was developed from the ground up to work with .NET is bull - because VB .NET was developed from the ground up as well to work with .NET.

<<
On the other hand, if I were talking to VB6 developers, I would definitely recommend VB.NET on the grounds of familiarity.
<<

There are a lot of VB developers who would disagree with you - to the extent that VB .NET is somehow "familar" to VB 6 developers. The fact is, there are a bunch of major differences once you get past the syntactic similarities.

I see your choice of languages being driven more by marketing than anything else...

If you want to provide value in your "training" - you should show both C# and VB .NET