I am amazed hearing people say its easier to switch from the one to the other. The hard part of learning either VB.NET or C# is NOT the syntax. The hard part is getting acqainted with the .Net framework. This goes for DNN as well: it really doesn't matter what language it is in, because no matter what the language is you write in, you still have to learn VB the framework ([edit]oops made an important typo![/edit])

So, even though i voted "It does not matter", in reality that means: stay with VB (and my guess is that that's what most people meant when they voted C#). This is the problem with quick surveys like these, you cannot really tell what people really mean from just one quick question.

To sum up my point of view:
It doesnt matter what language the core is in. This means that it is NOT a good business decision to change the language, since this is a) a lot of work, b) will introduce new bugs and c) does not help one tiny bit in helping new developers (incl. new corp employees) understand the DotNetnuke framework

---

Erik van Ballegoij, Former DNN Corp. Employee and DNN Expert

DNN Blog | Twitter: @erikvb | LinkedIn:

 

True, After 4 years of using VB, switching from C#, I do prefer VB, probably because I'm use to it now!

I think the point is, it doesn't matter what the core is written in, you can write modules in C# or VB. the compiled code is the same!....As for productivity of the DNN core team...I do find it difficult to believe they are slower because they are using VB instead of C#.  When I made the switch it took a good 2 weeks to make the mind switch, but after that it becomes natural.

Dave.