This is very interesting Craig. I started learning C# a couple of years ago actually and wrote a couple of little modules in it. Nothing hardcore. I was still leaning towards C# because of the huge amount of code samples available out there on the web. Now, it's looking like vb.net may be a better choice for developing full-fledged apps in the long haul and using c# behind the scenes. Time to pull out the vb.net book I guess :o)
>I've sat with both the C# and VB teams. They'll both expose functionality from the .Net framework, but how that is exposed and what other features and tools are available in the IDE will make a big difference. There are things that the VB team will be supporting that I find very useful that the C# team has said they have no interest in supporting.
>
>>I'm always surprised when someone compares 2 complex products like you do here. Such comparison implies indepth knowledge of both, and which is in case of a development environment something one needs several weeks of studying and testing, not to say several months. I presume you did for both ...
.·*´¨)
.·`TCH
(..·*
010000110101001101101000011000010111001001110000010011110111001001000010011101010111001101110100
"When the debate is lost, slander becomes the tool of the loser." - Socrates
Vita contingit, Vive cum eo. (Life Happens, Live With it.)
"Life is not measured by the number of breaths we take, but by the moments that take our breath away." -- author unknown
"De omnibus dubitandum"