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.

Microsoft Further Embraces Open Source


When the DotNetNuke project was started way back in late 2002, the combination of the terms “Open Source” and “Microsoft” were widely regarded as an oxymoron. In those early pioneering years we really had an uphill battle to fight in terms of gaining credibility and convincing people that open source was a viable development model for the Windows platform. In 2005 I wrote a blog titled “No Respect for Windows Open Source” which called out the hypocrisy in the non-Microsoft community when it comes to open source ideals. The blog got Slashdotted and generated more than 500 comments which polarized the extreme opinions on this topic at the time. Later, in 2008, Redmond Developer News ( now Visual Studio Magazine ) ran an article titled “Open Source .NET Projects Getting Cold Shoulder?” in which editor Michael Desmond questioned Microsoft’s lack of support for their own developer ecosystem and suggested that open source projects are treated as second-class citizens.

Well I have to say that the tide has really turned in recent years. The signs are everywhere that Microsoft is now truly embracing open source as a fundamental part of its business strategy. From for managing open source projects, to the Web App Gallery to help provide a high volume distribution channel, to the Outercurve Foundation to assist with open source governance and IP management, to Microsoft officially shipping and supporting organic third party open source projects such as jQuery, to Microsoft utilizing open development practices with its ASP.NET MVC framework, I think it is very clear that open source is now a first class citizen in the Microsoft ecosystem.

So it should really be no surprise that Microsoft went one step further today by announcing that ASP.NET Web API and ASP.NET Web Pages ( including the Razor parsing engine ) are now available under an open source Apache 2.0 license. And taking a page out of the playbook of the ASP.NET MVC project, Microsoft has spun up a new “ASP.NET Web Stack” project on Codeplex where they plan to increase the development transparency for these projects going forward by enabling a more open development model which encourages community participation.

Personally, I think this is a really smart move for Microsoft. Since they have always made their development frameworks available free of charge and the goal is to achieve the broadest adoption possible, there is really no business reason I can think of to manage this IP in a closed source manner. In fact, there are far more benefits and goodwill that can be gained by embracing an open source model and I expect that we will see many positive effects of this move in the years to come. I have to believe that this decision would not have happened without the determination and perseverance of many folks within the ASP.NET team; some of whom are still actively employed by Microsoft, and some of whom have since moved on to new opportunities. But the most credit needs to go to the guy at the top, the guy who has been the leader and the heart and soul of the ASP.NET team since the very beginning – Scott Guthrie has always understood the value of open source and I greatly admire how he has effectively led a quiet revolution within the Company.

So what does all this mean for DotNetNuke?

Since it is likely that all of these Microsoft open source projects will play a strategic technical role in the future of DotNetNuke, it is good that Microsoft chose a standard permissive Apache 2.0 open source license, as it means that we do not have any license compatibility issues to contend with. The fact that these projects will continue to be fully supported Microsoft products that ship both stand-alone as well as part of Visual Studio is also a huge benefit to us and our users, and in fact helps validate the argument we have been making for years that open source software can be fully supported and trusted. With the announcement that Microsoft intends to manage the new open source projects though Codeplex, it sends a clear signal that Codeplex will continue to be the official source for open source projects based on Microsoft technology. This is good for us, as we have been successfully utilizing Codeplex since 2008 and appreciate the investments that Microsoft continues to make in this service ( ie. the recent Codeplex integration with Git will likely provide value to our community in the future ). We will also closely monitor Microsoft’s progress in terms of working with the ASP.NET developer community to establish an open process for collecting feedback, accepting contributions, etc… It is comforting to know that the open source model which Microsoft plans to employ is the same model which DotNetNuke has already been using successfully for many years :)


There are currently no comments, be the first to post one.

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