Mitch's Blog

Performance issues with DotNetNuke extensions can be almost impossible to diagnose due to the dynamic nature of the DNN architecture. Thankfully, with tools such as ANTS Profiler, we can isolate activity to report on individual module performance.

Debugging and looking at complex objects can result in a lot of time being spent "hunting" for the proper information because the IntelliSense details do not contain helpful information. By using attributes available for debugging we can improve this display to be manageable.

It can be baffling how to create a link within DNN to a specific page with extra parameters but omitting a specific control.

After speaking engagements, I am often asked what my development tools are and my environments are, this is a list as of today.

Source control is important for all users, however, with many options, it is often hard to pick the right solution for yourself.

There are many configuration settings that can be adjusted to improve the performance of DotNetNuke, however, the terms used can be very complex, this post explores these concepts.

DNN supports multiple authentication providers, however, many users do not leverage this function. Disabling the unused providers can result in impressive performance improvements.

Often times you might need to extract data from SQL into a comma-separated listing of values. This seemingly simple task is not quite as simple as you expect.

DotNetNuke requires that any SQL Script include special additional items to ensure compatibility with the underlying development.