Glad to help.  I'm just sick of seeing the Language Wars; they are all backed by the same powerful framework so all it really comes down to is personal preference.  Personally don't like VB but I've been using Reflector to convert it to C# (even though I can read VB) for years.  The same applies to human languages as well -- I'm fluent in Spanish but that doesn't mean I actually *want* to speak Spanish to everybody I meet that can also speak Spanish... I'd rather speak my native tongue (English).  C# and VB programmers are the same way... they may *know* another language but that doesn't mean they actually want to use it.

So yeah, glad that the suggestion to use Reflector will potentially help people out.  That program is awesome.

Sorry to come into this thread as a complete DNN noob and both resurrect it from the dead while offering an opinion - I know it's in poor taste and hope I can be forgiven...

I can offer one fairly compelling reason why C# is preferreable to VB for asp.net development that is not simply a matter of personal taste; browsers run on Javascript. Vbscript is pretty much dead as a client-side scripting option. While C# has a lot more syntactic sugar than javascript, the two are certainly in the same family, and the more we all do web programming and with the rise of AJAX, the more we as developers need to be fluent in javascript, so you might as well work in the similar langauge for both client-side and server-side.

OTOH, I suppose the reverse argument could be made from the perspective of VB and T-SQL; T-SQL is a very Basic-like language and pretty much every (business) developer worth his salt need to know T-SQL, so...

Anyway, just thought I'd throw that into the mix for everyone's consideration.

...and oh yeah, Reflector is fantastic! The fact that I can go in and see the source code of the System.* dll's use for the .net framework has taught me so much!

Cheers,
C.List