Not trying to be a troll here, but why?  What would be the benefit of supporting two code bases?  One of the main points of .NET is that it is language agnostic.  Personally, I prefer C#.  I write my modules in C#.  But I can't think of any good reason to go through the effort to port DNN from VB to C#...

Normally, I would respond with "Why ask why? Ask, why not?".

But I was thinking about the real "need" of DNN (base classes) being available in C# and it is hard to justify for a few reasons. One, anyone who might contribute should provide their code in VB anyway to make it easier for the core group to vet - add a C# version and you'll (no doubt) receive code contributions in C# which would probably be a pain in the butt.

Two, the way DNN is architected, and as tg has pointed out, you are, really, free to write your own modules in C# as you see fit.

My only desire to see DNN in C# (beyond being a litte easier to read and understand for myself), is the possibility of a port to MONO. I noticed one of the development efforts is to use the Firebird database - MONO has a good Firebird driver.

I think that MONO could add a huge chunk of developer interest to the project (which is already notably significant in size) but there would be complications for Module developers seeking $ gain for their efforts - that model would be at risk if a MONO port of DNN was made available.

While there is still heavy development of the DNN core, this conversation is premature and I should apologize for bringing it up again (at the chagrin of the core folks I'm sure). I think there will come a time when core DNN has largely matured and we can discuss the merits at that time.

Rein