First code submission for MVC Pipeline

[donker]

Core Purpose

Introduces a new ASP.NET MVC-based rendering pipeline as an alternative to the traditional WebForms pipeline, allowing DNN to modernize its architecture while maintaining backward compatibility.

Key Features

Dual Pipeline Architecture:

• Traditional WebForms pipeline continues through /default.aspx
• New MVC pipeline routes through /DesktopModules/Default/Page/{tabId}/{locale}

Video showcase the general usage

Module Support:

More info about MVC Module Control Implementation
Razor Module Development Guide

• HTML module converted to MVC
• Sample modules demonstrating Razor+, MVC and SPA patterns

How to compile Samples

Configuration:

• Pipeline selection at portal and page level
• Settings UI integrated into Site and Page Settings
• URL rewriter modifications to route based on pipeline settings

More info about MVC pipeline (routing / settings)

New MVC Pipeline Projects

DotNetNuke.Web.MvcPipeline.csproj - New core MVC pipeline library

• Skins : Html Helpers (replacement for skin objects)
• Containers : Html Helpers (replacement for skin objects for containers)
• ModelFactories : construction of the Page Model (Model of the DefaultController)
• ModuleControl : Module Control infrastructure
• Utils : MvcViewEngine (Replacement for RazorEngine based on MVC 5 and can only be used inside HttpContext)
• UI/Utilities : MvcClientAPI (replacement for ClientAPI for mvc)

Razor Module Sample

• Razor-based module sample project

NewDDRMenu

• Fork of DDRMenu for MVC navigation support (WIP)

Core Platform Projects

DotNetNuke.Library

• Added Site and Page pipeline settings
• Added Module Control settings
• URL rewriter changes to route based on pipeline settings
• Update SPA (Html5) to use new CDF

DotNetNuke.Abstractions

• Added PagePipeline property to IPortalSettings

DotNetNuke.Web.Mvc

• Integration with new MVC pipeline
• Make actual DNN MVC modules run on the MVC Pipeline

HTML

• Add support for MVC Pipeline rendering
• Add MVC views and controllers
• This is implemented as true MVC (with form tags) using AJAX

Dnn.PersonaBar.UI

UI for pipeline settings in Site and Page Settings

DNNConnect.CKE

• HTML helper additions for CKEditor in MVC context

Skins/Aperture

• Added mvc suport to the skin (Razor files)

Website

• MVC Razor Layout
• MVC Default skin
• mvc.js minimal stuff needed for dnn to work
• Terms and privacy pages (razor files)
• DefaultController
• ModuleActions Controller

AdminExperiance

• settings ui for new settings
• mvc controls for persona and edit bar

This PR is a first submission of the work of the MVC Pipeline team to bring the main project up to date with what has been developed in a forked repo.

Documentation

MVC Module Control Implementation
MVC pipeline (routing / settings)
Razor Module Development Guide
How to compile Samples

[thienvc]

This is fantastic, I've been waiting for this for a long time. It feels like DNN is experiencing a strong resurgence. I hope the core version is finalized soon so I can experience it and gradually migrate the webform modules.

[thienvc]

In the classic webform version, we could use a .html skin and then DNN auto convert it to .ascx. Does the newer version still support this, as it automatically converts to .cshtml? I'm interested because I want to allow the portal admin to edit the portal theme without affecting host security.

[sachatrauwaen]

In the classic webform version, we could use a .html skin and then DNN auto convert it to .ascx. Does the newer version still support this, as it automatically converts to .cshtml? I'm interested because I want to allow the portal admin to edit the portal theme without affecting host security.

In the first version the .cshtml skin need to be created manually.
But it is an option to generate the .ascx and .cshtml from the .html

[thienvc]

In the classic webform version, we could use a .html skin and then DNN auto convert it to .ascx. Does the newer version still support this, as it automatically converts to .cshtml? I'm interested because I want to allow the portal admin to edit the portal theme without affecting host security.

In the first version the .cshtml skin need to be created manually. But it is an option to generate the .ascx and .cshtml from the .html

Great, when deploying multiple portals on the same host, I think allowing site administrators to customize the theme (skin) in .html format is standard practice, because if they were given permission to edit the skin in .ascc or .cshtml formats It's like giving them SuperUser privileges because it's too powerful.
In the future, I think we should only allow site administrators to install standard .html skins/themes to ensure overall security.