Hello Guy,

Thanks for replying on this...

>In C# you can have unmanaged code, operator overloading, that cool XML auto->documentation (forget the name) that you don't have in VB.Net.

Would there be a case when one might want to write unmanaged code?

Read up on 'operator overloading' which was defined as "the process of creating two or more functions with the same name but with different function signatures. With overloading you can implement functions that react differently based on input type." I dont really understand the data 'type' thing yet other than character, numeric, etc and why all this is different in .Net than VFP. Is operator overloading a big advantage?


>VB.Net has background compilation, not C#.

Noticed in my reading last night that 'backround compilation' catches syntax errors and such on the fly in the editor as entered. This is good for guys like me.

Also from my .net training tour documentation:

"All .net languages use the same runtime giving them the same performance and feature set. But the languages were designed for different target developers.

VB.Net provides declarative events, dynamic arrays, case insensivity, better com interop, late binding, modules, optional parameters and a backround compiler. These make VB.Net better suited for typical RAD Developers.

C# supports syntax for unsafe pointers,operator overloading, case sensitivity and bitwise shift operations since target users include lower level C developers."

Being a VFP developer, that puts me in the RAD category... Need to learn more about these features to make a good decision.

Thanks again for the input...

Todd