Wow, nobody is getting hot-headed on this thread.  Neither side of the fence is right or wrong in this argument.

Saying that a programmer (C#) won't be interested because it is VB is pretty short-sighted.  I'm a C# programmer but know VB.NET as well.  Do I like VB?  Not at all.  Am I interested in DNN?  Of course, I've built TONS of modules for it and continue to do so.

Saying that "a programmer who says that they are not interested in a project because of the language..." is also short-sighted.  I know plenty of developers who don't know a lick of VB.NET or C# and because of their knowledge have chosen that as a reason not to look into project 'x'.  Does that mean they aren't a programmer?  Not at all.  A "coder with limited experience"?  Possibly... but this should be an opportunity to educate them instead of knock them down.  Ultimately it means that they just don't have the time or desire to try and learn another language even if it is based on the same backend framework (read Microsoft .NET).  One of the arguments presented here was that it is easier for somebody to understand something (even if it doesn't compile) in a language they are more familiar with.

I'm not saying we do need a C# version but what I am saying is lighten up guys.  Somebody made a valid point as to why a C# version would make sense to them and they got attacked and flamed. 

So just to recap here: no there isn't a C# version, no there are no plans on releasing one (even a version that doesn't compile) until there is a wicked good automatic translation program.  What some people tend to do is get Reflector (now by Red Gate -- .NET Reflector) and just decompile it into their language of choice.  That isn't a perfect translation but makes it more readable to those that don't understand VB syntax nor have the time or desire to learn it.

...and from now on I'm only posting in French :).

Thanks for the reflector tip. Now we have a good answer for people wasting their time on Language Wars: use reflector!

(and alex: use google translate :) )

DNN Blog | Twitter: @erikvb | LinkedIn: