DNN Blogs

Open source isn’t truly “free”, it’s only free to use. The real cost lies in maintenance, which depends almost entirely on volunteers donating their time, expertise, and energy. DNN is a perfect example: despite being old enough to share a timeline with MapQuest printouts and MySpace profiles, it’s still alive because dedicated contributors keep it alive. Yet many modules were created by developers who have long since moved on, leaving behind essential but aging pieces that block upgrades and require significant, often tedious modernization work.

That’s why sponsorships matter. And it works!

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.

Take a first look at the DNN MVC Pipeline (MVCPL) in this admin settings Video walkthrough! 

We are happy to announce that version 10.01.02 of DNN has been released.

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.

For a next minor release (e.g. 10.2) we are planning to move DNN Platform off a project called Client Dependency Framework (CDF in short). We need you to help us test the proposed alternative.

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

In this meeting of the Southern Fried DNN User Group, we all hangout and have an exciting time catching up with each other and sharing projects we've been working on with DNN recently.

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.