I've been reading all the posts/flames/etc, regarding DNN C#, which, of course, does not exist.  I understand the reasons behind selecting VB originally, and why it is still that way today.  I'd like to add my 2 cents to the conversation.

In my experience, C# is a bit easier to maintain.  This could be due to my background (C++, Java, among other OOP languages), but I've noticed for large scale projects some languages seem to just be easier to deal with.  I have to admit, when I code VB, I usually have language syntax reference on speed dial, but it always seems like more work to do a large project in VB (opposite in small projects, though).

What a pain it would be to translate the entire site to C#!  I have always wanted to contribute to the core DNN project, but wouldn't consider it in its current VB.net implementation.  It gives me headaches just thinking about it (and nightmares if I would actually be doing it...). 

That leads me to my next point.  MAD PROPS to the core team for pulling off such a massive VB application that is still very performant!  Wow.  Mad skillz!

Anyway, here's my idea.  It's a matter of time before we see DNN for .net 3.0.  Wouldn't it be great to have a total rewrite in C# for 3.0?  I'd definitely pitch in where I could!  I'd love to see some of the cool features of 3.0 implemented in DNN (especially voice activated website! wow...).  I know a massive project like this is very difficult to manage, and trust the core team to deliver the best possible solution, in any case.  Besides, the project is great as is, and I can use C# for my modules, etc.  I believe there are tons of developers who would contribute more to the core project, however, if it were entirely in C#.

I was not aware of the .net 2.0-3.0 connection!  Thanks for the info!

BTW, I understand the JIT interpretation model of .net just fine.  In my opinion, it's not a matter of 'can it be done in VB or C#'.  Of course it can be!  It's more a matter of what does it look like and how understandable is it when it's complete.  Obviously VB people will find a VB easier to work with, etc..  Personally it always felt to me that some of the C# constructs were 'forced' into VB.net (though the opposite is probably true in many cases as well..), though C# isn't perfect either :-)

I've always used C# for modules and have had no problem (thanks to .net), but my original intent for this thread was to point out that C# programmers will be less likely to contribute to the framework since it's in VB.  Whether or not that's a problem is for you guys to decide, of course.  BTW, does anyone have any idea how many C# programmers there are vs VB programmers (at a high experience level, of course)?

Thanks for the reply!

Also, no sweat on the rewrite.  Even microsoft doesn't do that with their versions usually (though they should sometimes).  If a rewrite were planned, however, it would seem to be a reasonable time to switch languages if one were so inclined.

Rodney,

Thanks for replying!  Anyway, I totally agree that a rewrite would take forever, and obviously that makes it unlikely that it would ever happen.  You're also correct in pointing out that VB people would be less likely to contribute to DNN# (though it has a nice ring to it!). 

I do disagree with one point though, that there is not a single valid point for using C# vs VB, even though they are interpreted into the same thing when it's done.  I'll agree there are no technical reasons for using C#, as there are no inherent language limitations in VB that would allow one to do more in C#, though the same case could be made for C and C++. 

I have to say that I was a big C# skeptic when it was released (was sort of a java disciple converted from a C++ user), but was forced to use and learn it for some new projects.  I was an instant convert.  The language just seemed beautiful to me.  Sure there are flaws, but overall it was so intuitive (based on my previous experience) that I rarely needed a language reference even except for a few things.  I've NEVER felt that way about VB no matter how many lines of code I've written.  I do a lot of contract work and I avoid VB whenever possible.  It always seems like I'm programming QBASIC in high school again when I use it.  I ABSOLUTELY don't want to diss VB developers.  I've done lots of coding there myself and know it's powerful.  I just personally don't like using it.

Admitedly, I've given no concrete reasons for a rewrite (many would say no reason at all), and one will never be done (I'd wager unless MS drops support for VB at some point).  Does anyone at all agree with me about the difference in programming VB vs C#?  I know it's apples to apples in terms of function.  Anyway, it's an interesting topic.