Mitch's Blog

Now that we have a good structure in place, how do we deploy to different environments and test our DotNetNuke solutions?

In the final installation of my Enterprise Extension Development blog series we look at the actual project file structure and focus on reusability.

Enterprise extension development is a mindset and a technology set. The prior blog post looked at the mindset, now we look at the technology.

There is a difference when developing enterprise-grade solutions vs those quick-hit type items that are more bespoke. This post explores some of the differences in structure and process for the enterprise developer.

Over the past 6 months, I have been pushing to establish a set of NuGet packages for DotNetNuke extension development, these have finally been released!

Starting with 6.0.0 DNN introduced a new forms design standard, however, they changed that pattern in 7.x. How can we cope with the differences an minimize the level of effort?

With the release of ASP.NET 4.5, Web Forms developers managed to obtain some amazing new features even with all of the emphasis being placed on MVC. Of these new features, the most helpful, in my opinion, is the ability to do Model Binding in a similar manner to MVC within WebForms.

Providing secure access to files within an application can be a bit complicated, this post explores options available to .NET Framework 4.5, and later, developers for securing access to file assets.

DotNetNuke has a number of internal logging processes, these can leave behind files that are uncleaned. This post explores the items that can, and should, be cleaned on a regular basis.