Last post Nov 18, 2011 10:58 AM by christoc
Mar 01, 2011 04:31 PM|sbwalker|LINK
Ever since DotNetNuke was first released on Christmas Eve 2002, the core framework has always been developed and maintained in VB.NET. The historic reason for this language preference was because I had originally chosen to use the Visual Basic / Visual Studio
version of the IBuySpy Portal reference application from Microsoft as the basis for the DotNetNuke platform. In the opening chapter of the
Professional DotNetNuke 5 book from WROX Press, I stated my opinion that I felt the decision to use VB.NET was one of the key reasons for the early success of the open source project, as it provided Classic ASP developers with a simpler migration path to
ASP.NET. I stand by this opinion today; however, I must also acknowledge that in the years since, the .NET development landscape has changed significantly.
One defining characteristic of the DotNetNuke open source project is that it has always tried to be more pragmatic than dogmatic. Our primary goal is to create value for our users, so if a clear and compelling business case can be made which benefits the
majority of the community and mitigates the risk, we have no hesitation in making bold moves with our technology platform.
Over the past 8 years, the DotNetNuke project has had more than its fair share of critics who vocalized the fact that they felt C# was a superior development language to VB.NET for developing large-scale applications. Most of the arguments, although passionate
and convincing, generally tended to be quite subjective. As a result, the language debate simmered in the background as we focused on adding deeper value to the platform.
About 1 year ago, a Chinese developer, Ben Zhong, personally went through the effort of converting the core framework to C# and posted the results of his work on Codeplex. Initially we had obvious concerns that a fork of DotNetNuke could result in confusion
and fragmentation in the ecosystem, but we also recognized that a C# version was something that had been requested often in the past. We decided to reach out to the developer to determine if he would be interested in collaborating with us to provide an “official”
C# source code distribution. It turned out that he was willing, and over the past year the C# source code package, which he independently maintained, resulted in thousands of additional downloads. This provided proof that there was indeed a demand for a C#
version of our software, so when the question about moving to C# was raised publicly at the DotNetNuke Connections conference in Las Vegas last November, it provided the catalyst to take a deeper look at the state of VB.NET versus C# to analyze the specific
business benefits and opportunities offered by each language as we look towards the future.
So without any further ado… I am pleased to announce that we decided to switch development languages for the core platform from VB.NET to C# !!
The rest of the announcement can be viewed here:
Mar 18, 2011 05:24 PM|christoc|LINK
For those of you who might think that such a move may be bad for DotNetNuke, due to the increase in bugs, I had the same fear.
I blogged about those fears, and my experience in testing a very early version of the C# code.
Mar 18, 2011 06:40 PM|Small Peter|LINK
Good news. I think this is a wise move. Because nowadays ASP.NET beginners most start with C# but not VB.NET
Nov 18, 2011 08:16 AM|vigorniensis|LINK
What a very poor decision this is. The reasons DNN utilised VB in the beginning still hold good today. To those of us who have developed countless modules and who made the decision to go with DNN these past few years
because it wasn't written in an idiotic unreadable language of semi-colans this is a slap in the face and an appalling decision. If C# programmers can't understand VB then they shouldn't be in
programming quite frankly.
Additionally I blame Microsoft for pandering to these C programmers and can't help but feel the vast amounts of money wasted on duplicating VB into some ridiculous unreadable language like C# could have been far better spent on
enhancing VB6 because going to VB.Net from VB6 is not an automatic choice. They are worlds apart in scope, but Microsoft have chosen to abandon VB6 in favour of spending the money on C#. What a stupid and crass
decision. And now Mr Walker has compounded this absurdity.
Bye bye Mr Walker I'll leave you to your damned silly semicolons! I am simply appalled by this.
Nov 18, 2011 10:58 AM|christoc|LINK
Just as it shouldn't have mattered to users/developers if DNN was in VB.net, it shouldn't matter now that it is in C#.
Developing extensions for DotNetNuke, the life blood of the EcoSystem for DNN is still the same, VB or C#, your choice.
The core is in C#, changes are happening at a greater pace now, new features, UI overhauls, all happening much more quickly now that the team maintaining it is doing everything in C#.