Andrew Hoefling

Dependency Injection is a new feature coming to DNN in 9.4 that allows you to inject abstractions or other objects into your MVC Module Controllers. This has been a common practice in both ASP.NET MVC and ASP.NET Core MVC application development. Removing the tight coupling between your controller code and business layer of your module.

Dependency Injection is used in many modern applications, it is ubiquitous across .NET application development. In .NET Core it has been built into the platform as a core feature that gets configured during the App Startup code. DNN was built before Dependency Injection became so popular in .NET, and in-lieu of Dependency Injection the Factory Pattern was heavily used. Adding Dependency Injection in DNN will be the first major step towards migrating to .NET Core.

Manually handling storage and retrieval of images and video can be time consuming and error prone because of all the image and video formats. Serving this content can be even harder especially with videos and getting the right codecs is enough to make you not want to do it. 

Using 3rd party tools such as Dropbox and Youtube will greatly reduce your time and risk when creating a photo/video solution. This is just what our team here at Hoefling Software did to deliver a Photo Contest Module built specifically for DNN

DNN 9.2 introduces many new features including new routing controls for MVC Modules. Now, when building a MVC Module you can easily Redirect routes between Controllers and Actions at the Controller level. This new feature introduces flexibility that adds feature parity with Microsoft’s MVC implementation. With this change a MVC Module can contain many controllers and actions per controller that handle the complex routing scenarios associated with MVC development. Prior to 9.2 developers were limited to having one controller. While there were workarounds to this limitation until now there wasn’t an elegant way to handle routing in a MVC Module.