As a "hard core" VB developer I am "saddened" to think  the core may move to C#.  Realistically, since the I don't change the core, it does not directly impact me.  I can still develop modules in VB.net so I voted "Does matter to me"  

However,  I agree with suggestion that such a move WILL help the adoption of the DNN. So I would recommend that the change happen with the release of version 6.0  -- this is the time to do it.   They also should make this determination soon .. especially considering the work needed to get version 6.0 released. 

With DNN goal of being the largest CMS .. this is a step that is needed.  

Just my 2 cents.
Paul.

I just voted for VB, not because I really care, it's just that I started .Net as a C# developer and only changed to VB when I started using DNN. My thought was that I wanted to use the same language as the core. After I got over my false profesional pride, I actually prefer VB now!...switching between C# and VB isn't difficult, I'm still amazed that C# developers have a reluctance to use VB....It's basically the same language!!

If the core moves to C# my first concern would be bugs in DNN....DNN5, in my opinion has only just become stable enough to use on a Live system (As long as you don't turn on CL), the thought of now breaking it scares me!

I can see the point for DNN to move to C#, but this is only an attempt to make DNN more accepted by the C# hard liners, I can't see any technical need to do so....in fact I can see technical reasons not to move all the code over to C#, it's a big jobs and very likely to end up with quite a few bugs, at least for the first few releases.

I suppose if DNN does move to C#, I'll simply move back to coding C# again...don't much like the idea of converting NB_Store to C#....might keep that VB!

One last thought is that VB and C# is getting to be a single language in many ways...I don't know what the future is bringing, but a C# -VB automatic converter could be just around the corner?.......a plugin to Visual Studio to switch between the two langauges dynamically would be ideal..but that might be asking a bit much.

Dave.

As I see it, there would be two main reasons to convert to C# - improved perception amongst the wider developer community and access to a larger talent pool. But TBH I can't see that either of those are sufficiently important.

As far as developer perception goes, the "cool kids" will sneer anyway because DNN uses WebForms, and that's not going to change any time soon.

Also, any developer worth hiring in the first place shouldn't be put off by which language they'll be using. I'm guessing the current team is pretty much bi-lingual already, so there's no reason why new hires shouldn't at least be willing to embrace both languages.

So I'd err on the side of the status quo, unless the core team particularly want to move to C# because of better tooling or some other similar reason, in which case just stuff it through an automatic converter and be done with it :)

---

Mark Allan (@MarkXA)
DNN Garden, home of the DDRMenu free DotNetNuke menu module