DNN Blogs

A summary of happenings within the DNN Technology group over the last two weeks ending on 1/6/2026.

This post provides a summary update of DNN Technology Group meetings held over the past two weeks, ending 12/9/2025

As per version 10.2.0 of DNN the code that used to be in the sample modules (MVC/SPA) repository (https://github.com/dnnsoftware/Dnn.Platform.Samples.Mvc) has been moved to /Dnn Platform/Modules/Samples. This move serves three purposes:

This post provides a summary update of DNN Technology Group meetings held over the past two weeks, ending 11/25/2025.

Over the past years, DNN has been deprecating a lot of API methods to services using Dependency Injection. Starting DNN 10, the first batch of "old" API's have actually been removed. This means a lot of the old modules that are still out there, will need to be updated to use those new DI-services. The good thing is that de DNN Docs explain how you can do that. But, unfortunately, back iin the day, static method were considered pretty fancy. No need to instanciate a class if you don't nmeed it's state, right? Well, that's biting us now. But, there's no way back, so we need to have a quick and solid way to use the new services, using DI.

As DNN continues to evolve, we’re increasingly relying on modern .NET libraries distributed through NuGet. This has opened the door to powerful new features and integrations — but it’s also brought with it an old and familiar problem: DLL hell. In this post, we’ll walk through why our traditional upgrade process no longer fits today’s reality, and how we’re moving toward a more robust, installer-driven approach to keep your sites stable and easier to upgrade.

When you’re running an open-source platform like DNN, security is never “done.” It’s an ongoing process. The same openness that makes open source powerful—shared code, community collaboration, peer review—also means that vulnerabilities can be easier to find and exploit. That’s why the DNN Community takes security so seriously.

In our previous blog post, we introduced the idea of creating a true MVC pipeline for DNN. From the very beginning, we want to be open and transparent about how this project evolves. That’s why we are sharing updates as we go, instead of only publishing results at the end

My last post talked about a new community effort to bring an MVC pipeline to DNN Platform.  As you may know, that could really open a door to a transition to .NET, as sites may no longer need to have any dependency on .NET Framework.  For this to happen, we have a LOT of things that we need to discuss, and this post is just one of my first posts, sharing some of the ideas, questions, and thoughts that I have of how we might be able to make this transition a reality.

It has been just about 5 years since my last overall update blog post was shared regarding DNN Platform, high-level technology needs, and future roadmap items. A lot has happened over these years, both for DNN itself, our community, and technology as a whole.  We have accomplished many of the goals that were outlined at that time, and we have some great new efforts by various DNN Community members that we need to revisit, embrace, and see where they will take the DNN Platform in the coming years.