I guess what I was wondering is why all this work put into porting this over to C# instead of working on further enhancing the platform itself. But I see your point, if the idea is to target more developers (ie: c# community) then that might be a reason.

Shauns blog at http://www.dotnetnuke.com/Resources/B... covers the reasons behind the move - essentially it was done for business reasons not technical reasons, though of course we hope that the choice of c# will attract more developers and hence more downloads/modules etc. (vb.net developers are more accepting of c#, whereas c# developers often look down on vb.net).

Regarding the work, we've leveraging the work that Ben did migrating it initially and then keeping a c# version up to date with core releases. Of course we had some effort (though not as much as you'd think), merging in the c# code and converting some additional items that were contributed to 6.0 that were in vb.net, but it's also a good opportunity for us to do some "spring-cleaning" and tidy up the code and the xml commenting. In addition the c# version offers some additional opportunities e.g. there are code analyzers such as stylecop that we can now utilise, and the refactoring tool (resharper) that DNN Corp employees use is more useful for c# than vb.net.

Thanks,
Cathal

---

Buy the new Professional DNN7: Open Source .NET CMS Platform book Amazon US

I've been meaning to make this comment for some time but was waiting to see what was happening with the DNN development. 

I don't have any issues with DNN moving to C#, I am personally making the switch myself, again, not for technical reasons, but because of market forces.

My big beef is with the decision of not making a 5.6.3 version of the core as the final VB version.  As it has been discussed in the forums, there are outstanding issues that should be resolved.  Related to that is the fact that there are so many changes incorporated into the move to C#, it is not only a language conversion but a lot of architectural changes and features have been added.  You really think that people having issues with 5.6.2 are going to jump to the new 6.0 right away???  With all the changes taking place, it would not be wise for anybody to move to the new core until at least 6.1 or 6.2.  This is typical of any major software upgrade, not just DNN, don't take it personally.

So please, give us a solid, final, 5.6.3 version so that we can use it for the next year or so until DNN TNG is truly stable.

Carlos