New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

The Community Blog is a personal opinion of community members and by no means the official standpoint of DNN Corp or DNN Platform. This is a place to express personal thoughts about DNNPlatform, the community and its ecosystem. Do you have useful information that you would like to share with the DNN Community in a featured article or blog? If so, please contact .

The use of the Community Blog is covered by our Community Blog Guidelines - please read before commenting or posting.

DotNetNuke is switching to C#, uh oh

If you didn’t see Shaun’s blog post earlier this week you should give it a good read through. The post announced the fact that starting with Version 6.0 (targeted for Q2 2011) DotNetNuke will no longer be developed/released as a VB.NET Application. All development of the core platform will be in C# (this does not mean that the community modules for the platform will change languages).

Most of the feedback I have seen so far has been rather positive, most folks who use DotNetNuke on a regular basis understand that the language that the framework itself is written in really doesn’t make a bit of a difference to 99.9% of all DotNetNuke based websites. The framework is there for you to build on top of, and while it is open source, it is actually recommended by all experts that you don’t modify the “core” code of the framework, if you need to make changes you do it through the use of modules and custom providers.

Extensions (modules, providers, skins, etc) for DotNetNuke have always been language independent, you can develop your extensions in whatever language you want. I personally have developed all modules for the past 4-5 years (besides the Wiki module) in C# rather than VB.NET out of personal preference.

So the framework being VB.NET or C# shouldn’t make a difference to most people.

People have questioned the decision still, why would DotNetNuke Corporation bother spending time with the conversion? Aren’t there plenty of other things in the platform that could use the attention? What about all the “bugs” this will introduce into the platform? That is the biggest question I have seen from people so far, and I’ll be honest with you. I was one of those people, I had the very same concerns.

When the discussion to convert to C# began I was very much against it. Every one of those folks listened to me and heard my arguments. Having worked at DNN Corp for a year now, and having been part of the community for 8+ years, I know there are plenty of things in DotNetNuke that could use attention to make them better, easier to use, etc. I told Shaun, I told Rob (VP of Engineering), and I told Navin, our CEO.

Before the final decision to convert was made I made some phone calls to engineering and got myself a copy of the C# version of the upgrade package, with VERY VERY early DotNetNuke 6.0 code. I wanted to test this code out myself, I wanted to prove that moving to C# at this point in time was a bad idea.

So I downloaded one of my production websites, I got it up and running locally, and then I upgraded from v5.6.1 6.0.

Do you want to know what happened? The damn website worked….. The upgrade worked. I was very surprised. Sure there were a couple of very minor issues, a problem with the ADMIN pages, but digging through the website, my custom modules worked, my pages worked, my content was all there. My event viewer (event log) was fine, it wasn’t throwing errors, things were working.

This was very early code, sure there were a few things that still needed to be worked on (removing old VB files, etc) but the website was working, and it was working far better than I had expected it to be.

I was sold. I called Rob, I called Shaun, I apologized, I told them I was wrong, and I told them I supported the move to C# because I knew the ultimate benefits would be worth it (see Shaun’s post for those).

So, for all of you doubters out there, I totally and 100% know where you are coming from, I’ve been there, but I think that you will ultimately find that this move is going to be great for DotNetNuke.

That’s not to say there won’t be issues, there are always issues, but DotNetNuke Corporation strives to make each and ever release of the platform better, future releases won’t be any different.

If I haven’t eased your mind, or even if I have, I would encourage you to check out the CTP for V6.0 when it is available later this month. Test out the C# version, run some of your production websites through upgrades in a test environment.

We definitely need your help making sure things work, I will sure be doing a lot more testing of my websites before the official release, far more than I typically do as I generally am limited in time. I will make the time over the next month or two to make sure that I can do all that I can to make 6.0 the best release yet.


Comment Form

Only registered users may post comments.


Aderson Oliveira (22)
Alec Whittington (11)
Alessandra Davies (3)
Alex Shirley (10)
Andrew Hoefling (3)
Andrew Nurse (30)
Andy Tryba (1)
Anthony Glenwright (5)
Antonio Chagoury (28)
Ash Prasad (37)
Ben Schmidt (1)
Benjamin Hermann (25)
Benoit Sarton (9)
Beth Firebaugh (12)
Bill Walker (36)
Bob Kruger (5)
Bogdan Litescu (1)
Brian Dukes (2)
Brice Snow (1)
Bruce Chapman (20)
Bryan Andrews (1)
cathal connolly (55)
Charles Nurse (163)
Chris Hammond (213)
Chris Paterra (55)
Clint Patterson (108)
Cuong Dang (21)
Daniel Bartholomew (2)
Daniel Mettler (181)
Daniel Valadas (48)
Dave Buckner (2)
David Poindexter (12)
David Rodriguez (3)
Dennis Shiao (1)
Doug Howell (11)
Erik van Ballegoij (30)
Ernst Peter Tamminga (80)
Francisco Perez Andres (17)
Geoff Barlow (12)
George Alatrash (12)
Gifford Watkins (3)
Gilles Le Pigocher (3)
Ian Robinson (7)
Israel Martinez (17)
Jan Blomquist (2)
Jan Jonas (3)
Jaspreet Bhatia (1)
Jenni Merrifield (6)
Joe Brinkman (274)
John Mitchell (1)
Jon Henning (14)
Jonathan Sheely (4)
Jordan Coopersmith (1)
Joseph Craig (2)
Kan Ma (1)
Keivan Beigi (3)
Kelly Ford (4)
Ken Grierson (10)
Kevin Schreiner (6)
Leigh Pointer (31)
Lorraine Young (60)
Malik Khan (1)
Matt Rutledge (2)
Matthias Schlomann (16)
Mauricio Márquez (5)
Michael Doxsey (7)
Michael Tobisch (3)
Michael Washington (202)
Miguel Gatmaytan (3)
Mike Horton (19)
Mitchel Sellers (40)
Nathan Rover (3)
Navin V Nagiah (14)
Néstor Sánchez (31)
Nik Kalyani (14)
Oliver Hine (1)
Patricio F. Salinas (1)
Patrick Ryan (1)
Peter Donker (54)
Philip Beadle (135)
Philipp Becker (4)
Richard Dumas (22)
Robert J Collins (5)
Roger Selwyn (8)
Ruben Lopez (1)
Ryan Martinez (1)
Sacha Trauwaen (1)
Salar Golestanian (4)
Sanjay Mehrotra (9)
Scott McCulloch (1)
Scott Schlesier (11)
Scott Wilkinson (3)
Scott Willhite (97)
Sebastian Leupold (80)
Shaun Walker (237)
Shawn Mehaffie (17)
Stefan Cullmann (12)
Stefan Kamphuis (12)
Steve Fabian (31)
Steven Fisher (1)
Timo Breumelhof (24)
Tony Henrich (3)
Torsten Weggen (3)
Tycho de Waard (4)
Vicenç Masanas (27)
Vincent Nguyen (3)
Vitaly Kozadayev (6)
Will Morgenweck (40)
Will Strohl (180)
William Severance (5)
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out