DNN (software)

DNN (formerly DotNetNuke) is a web content management system and web application framework based on Microsoft .NET. The DNN Platform Edition is open source.

DotNetNuke
Original author(s)Shaun Walker[1]
Developer(s)DNN Corporation [2]
Stable release
9.4.1[3] / 2019-09-27 [±]
Operating systemMicrosoft Windows or Cloud
PlatformASP.NET or Cloud[4]
TypeWeb framework
LicenseMIT[5]
Websitewww.dnnsoftware.com

DNN is written in C#, though it existed for many years as a VB.NET project.[6][7] It is distributed under both a Community Edition MIT license [5] and commercial proprietary licenses as DNN Evoq Content and DNN Evoq Engage editions.

Editions

DNN Platform (formerly "DotNetNuke Community Edition" content management system) is open source software distributed under an MIT License that is intended to allow management of websites without much technical knowledge, and to be extensible through a large number of third-party apps to provide functionality not included in the DNN core modules. Skins can be used to change the visual appearance of a website using DNN.

There are two commercial editions of the software with increased functionality (compared to DNN Platform) and technical support. The DotNetNuke Professional Edition was introduced in February 2009 with version 4.9. In July 2013, DotNetNuke Professional Edition was renamed Evoq Content.[8] In addition, DotNetNuke Enterprise Edition was renamed Evoq Content: Enterprise.[9] Evoq version 9.0 was released in December 2016.[10]

Architecture
DNN uses a three-tier architecture model.

DotNetNuke uses a three-tier architecture model with a core framework providing support to the extensible modular structure.

While traditionally DNN focused on providing server side functionality, recent projects strive to enhance client side experiences - along with the rest of the industry.[11] In recent years DNN migrated from using exclusively Web Forms to also allowing Model View Controller and Single-page application architectures.[12] In the future, DNN faces the challenge of moving from ASP.NET 4.6 to the cross-platform free and open source .NET Core.

DNN can be extended using 3rd-party modules and providers that add functionality at the server or client side. The appearance of individual pages and sites can be customized using skins.[13]

Modules
DotNetNuke modules.

The default functionality of DNN can be expanded by adding third-party modules, either from an existing module store,[14] from 3rd party authors,[15] or through in-house development of custom functionality.[16] The DNN framework provides basic functionality such as security, user administration, and content management, while modules are used to tailor the web site for specific deployment needs.[17]

A set of primary modules are included with the core DNN distribution. These modules provide the functionality required to create an e-commerce system, an intranet, a public web site or a custom web application. They are maintained by a volunteer team community. In 2015 and 2016 most projects were moved from the DotNetNuke Community Forge[18] to GitHub.[19]

Web pages have skins which define regions of a page (plus their appearance) where page editors can place modules (or extensions) made available by site administrators. Pages and modules can inherit or set custom access permissions that define which groups of users can view or edit each item.

Module can be created in various ways: compiled modules use the Web Application Project model and are written in C# or VB.NET,[20] dynamic modules use the Web Site Project model, and Razor modules which use a C# or VB.NET scripting language.[21]

Skins

A skinning architecture provides a separation of presentation and content, enabling a web designer to develop skins without requiring any specialist knowledge of development in ASP.NET: only knowledge of HTML and an understanding of how to prepare and package the skins themselves is required. Skins consist of basic HTML files with placeholders (tokens) for content, menus and other functionality, along with support files such as images, style sheets and JavaScript, packaged in a ZIP file.[22]

Like modules, skins, can be uploaded and automatically installed through the administration pages. If the compiled skin does not contain an ASP.NET user control file, then the DNN skinning engine builds one based on various tokens included in the HTML file which refer to various sections, placeholders and/or modules of a DNN-produced page. Modern skins incorporate CSS3 and HTML5[23] with many authors' skins supporting Responsive web design, various JavaScript libraries. With no credentialing, a skin's quality may vary, but often trial periods are available to evaluate functionality.

Hosting

DNN 7.0 and above has a minimum requirement of Windows 7, SQL Server 2008, and .NET 4.0 and IIS 7+. These product's latest versions are supported.[24] As of version 6.0, DNN can also be installed in an Azure cloud computing environment.[25] Numerous web hosting companies offer DNN as an offering, and a 1 step installation process is available through Microsoft.[26] However DNN's requirement for an IIS medium trust environment has prevented broader adoption[27] among some mainstream hosting companies.

Developer ecosystem community

DNNSoftware.com has over 1 million registered members as of November 2013 and is used on some 750,000 websites globally.[28] Support for the Community Edition of DotNetNuke is provided by community members and developers can participate in the open-source project on GitHub.[29]

API reference documents for modules[30] and skins[31] are available, although as of 2013, some documentation was still available only in task-oriented form.[32] A Wiki has been created to address this weakness, with 400 wiki pages as of May 2014.[33]

Project history

The DotNetNuke application originally evolved out of another project, the IBuySpy Portal which was a reference application created in 2001 by Microsoft to showcase the new ASP.NET software development framework. Shaun Walker[1] added significant enhancements to the IBuySpy Portal and released a new version branded as the IBuySpy Workshop on December 24, 2002.[34] The early releases of the IBuySpy Workshop application were developed solely by Walker and distributed by his consulting company, Perpetual Motion Interactive Systems Inc. In March 2003, Shaun Walker announced a rebranding of the open source application to DotNetNuke. The name "DotNetNuke" was coined by Walker by combining the term .NET with the word "nuke", which had been popular with pre-existing frameworks such as PHP-Nuke and PostNuke.[35] Walker registered trademarks for the terms DotNetNuke and DNN in both the United States[36] and Canada.[37][38] At this point Walker formed a Core Team of software developers to help him develop and promote new versions of the open source project.[39]

In September 2006, Shaun Walker invited 3 members of the Core Team, Joe Brinkman, Nik Kalyani, and Scott Willhite, to form DotNetNuke Corporation to oversee management and development of the project, as well as offer professional services to the community.[40]

On November 25, 2008, DotNetNuke Corporation announced that it had secured Series A financing from Sierra Ventures and August Capital and hired Navin Nagiah as CEO; and in February 2009 it released DotNetNuke Professional Edition, targeted at business and enterprise customers. In February 2010, DotNetNuke closed a round of Series B financing from Sierra Ventures, August Capital, and Pelion Venture Partners.[41]

In August 2009 DotNetNuke Corporation launched a partnership program aimed at providing support to web design and development companies using DotNetNuke. They also announced the acquisition of Snowcovered, an online market for DotNetNuke modules, skins, services, and related products.[42]

In October 2009, the Open Source CMS Market Share Report concluded that DotNetNuke was the leading .NET-based open source web content management system.[43]

In 2013, the company was renamed DNN Corporation[44] and in 2017 the company was acquired by ESW Capital.[45]

Content management

DNN provides basic content-management out of the box, but is usually accompanied with one of many (mostly open-source) content management extensions.

Overview
ProductLicensePriceWebsiteSource CodeAvailable SinceVersion
DNN StandardMITFree DNN GitHub ca. 20039.4.1[3]
2sxcMIT and othersFree 2sxc.org GitHub ca. 201211.04.00[46]
OpenContentMITFree OpenContent GitHub ca. 20144.4
LiquidContentProprietaryyearly fee DNN (closed source) ca. 20169.4.1[3]

Basic content editing features
ProductRich-Text (HTML) EditStructured ContentAsset Management
DNN StandardYesNoYes
2sxcYesYesYes
OpenContentYesYesYes
LiquidContentYesYesYes

File management
FeatureYes EditNoRemarks
Host levelYes
Portal levelYes
Folder permissionsYes
Secure foldersYes
Specify allowed extensionsYes
Search assetsYes
Get asset urlYes
gollark: We are not ACTUALLY circumventing xenon.
gollark: I mean, it's a real codename for some of our projects, at least.
gollark: Yes.
gollark: That is not the case.
gollark: No, you're just wrong.

See also

References
  1. "Interview with Shaun Walker – Co-Founder and Chief Technology Officer of DotNetNuke Corporation". cmscritic.com. 14 March 2013.
  2. "Web CMS - Online Community Software - DNN (DotNetNuke)". dnnsoftware.com.
  3. "Releases - dnnsoftware/Dnn.Platform". github.com. Retrieved 2019-09-27.
  4. Pranav Singh (2013-06-04). "Deploying DotNetNuke on Windows Azure". CodeProject. Retrieved 2017-04-05.
  5. "DNN CMS Platform - License". Dotnetnuke.codeplex.com. Retrieved 2017-04-05.
  6. "DotNetNuke Switches to C# !! >". DNN Software. 2011-02-28. Retrieved 2017-04-05.
  7. a (2007-05-11). "A conversion of the popular DotNetNuke web application to C#". CodeProject. Retrieved 2017-04-05.
  8. "DNN Expands Product Suite, Services and SaaS Offering With DNN Evoq". DNN Corp. Retrieved 14 Aug 2013.
  9. Mosher, Barb (2013-07-09). "DotNetNuke Rebrands to DNN Evoq, Focuses on Business Solutions + Platform". Cmswire.com. Retrieved 2017-04-05.
  10. "New CMS Features in Evoq 9". DNNSoftware. DNN Corp. Retrieved 6 March 2017.
  11. "Client Resource Management API". Dnnsoftware.com. Retrieved 2017-04-05.
  12. "DNN Loves MVC: 1 - Introduction". Charlesnurse.com. 2015-03-28. Archived from the original on 2016-08-13. Retrieved 2017-04-05.
  13. "DotNetNuke - the easy way to an ASP.NET website - .NET tutorial". Developer Fusion. 2010-06-28. Retrieved 2017-04-05.
  14. "The Official DNN Store - Modules, Skins and Extensions". Store.dnnsoftware.com. 2017-02-11. Retrieved 2017-04-05.
  15. "DNN Community". Github.com. Retrieved 2017-04-05.
  16. "DotNetNuke 4 - Module Developers Guide - Chapter 1". Adefwebserver.com. Retrieved 2017-04-05.
  17. "Amazon.com: dnn and dotnetnuke". Smile.amazon.com. Retrieved 2017-04-05.
  18. "NET Forge CMS, Extensible CMS - DNN Software Forge". Dotnetnuke.com. 2017-01-28. Retrieved 2017-04-05.
  19. "Why DNN Community Extensions have Moved to GitHub". Github.com. 2015-02-20. Retrieved 2017-04-05.
  20. "DotNetNuke Development | DNN Developer | DNN Experts, DNN Module Development, DNN Skins India". Swayamsoft.com. Retrieved 2017-04-05.
  21. "Build CMS, Building a Product Roadmap, CMS Development Tools". Dnnsoftware.com. 2017-01-28. Retrieved 2017-04-05.
  22. "Top 5 DotNetNuke Manifest file Module Packaging Tips". iFinity. Archived from the original on 2017-07-04. Retrieved 2017-04-05.
  23. "How to Create a Responsive HTML5 Skin for DotNetNuke". Dnncreative.com. Retrieved 2017-04-05.
  24. "DNN Cloud Demo - Install DNN Software | DNN DotNetNuke". Dnnsoftware.com. 2017-01-28. Retrieved 2017-04-05.
  25. "DotNetNuke in Azure Cloud". Elinext. 2012-04-14. Retrieved 2017-04-05.
  26. "Microsoft Web Platform". Microsoft.com. Retrieved 2017-04-05.
  27. "Installing DotNetNuke 4.9.0 on Medium Trust Webservers". Programmersanonymous.net. Archived from the original on 2016-08-16. Retrieved 2017-04-05.
  28. "DNN CMS Platform - Home". Dotnetnuke.codeplex.com. Retrieved 2017-04-05.
  29. "dnnsoftware/Dnn.Platform: DNN Corp Platform Repository". GitHub. Retrieved 2017-04-05.
  30. "DNN API Endpoint Documentation". Endpoint.dnnapi.dnnsharp.com. Retrieved 2017-04-05.
  31. "DNN Skinning Reference | DNN Skinning Tool | Dot Net Nuke Skinning". 10poundgorilla.com. Archived from the original on 2017-04-30. Retrieved 2017-04-05.
  32. "About DNN - DNN Company Overview | DNN". DotNetNuke. Retrieved 2017-04-05.
  33. "CMS Wiki, Content Management Wiki". DNN Software. 2017-01-28. Retrieved 2017-04-05.
  34. "Open Source CMS Project History - DNN CMS & Online Community Software". dotnetnuke.com.
  35. "About DNN - DNN Company Overview - DNN (DotNetNuke)". dotnetnuke.com.
  36. "Trademark Electronic Search System (TESS)". uspto.gov.
  37. "Basic search: 1192080 - Canadian trade-marks database - Intellectual property and copyright - Canadian Intellectual Property Office - Industry Canada". Ic.gc.ca.
  38. "Basic search: 1256752 - Canadian trade-marks database - Intellectual property and copyright - Canadian Intellectual Property Office - Industry Canada". Ic.gc.ca.
  39. "Building Websites with DotNetNuke 5". www.packtpub.com.
  40. "About DNN - DNN Company Overview - DNN (DotNetNuke)". dotnetnuke.com.
  41. "DotNetNuke Raises $8 Million". PE Hub. 2010-02-09. Retrieved 2017-04-05.
  42. "DotNetNuke Buys Snowcovered". Silicontap.com. 2009-08-27. Retrieved 2017-04-05.
  43. "Archived copy". Archived from the original on 2010-06-18. Retrieved 2010-06-15.CS1 maint: archived copy as title (link)
  44. Shaun Walker. "DNN: The Metamorphosis Continues..." DNN Software.
  45. "DNN Corp. Acquired by ESW Capital". prweb.com.
  46. "Releases - 2sic/2sxc". github.com. Retrieved 2020-07-31.


This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.