Development Articles

Anytime someone says "our API is easy" or "it will be quick" I instantly add 25% to the project cost because I know that isn't the case. This post explores methods to help mitigate risks with new integrations.

ASP.NET Ajax allows developers to add Ajax functionality to quickly introduce Ajax features without extra development, however, usage of this within DNN is met with some challenges.

Over time DNN applications can see bloat in the web configuration file from modules that were installed and removed, or from upgrade issues. Ensuring that your configuration file is clean can help with upgrades, performance, and other support activities.

I love sharing stories of great experiences with third-party vendors, as it doesn't happen as often as I would like. When a recent performance issue was identified in DNN using 51 Degrees software, they jumped in and helped greatly.

Module developers have many choices as they create their extensions. One of which is around the level of emphasis placed on performance, a few simple things can set your module apart from others with these performance tweaks.

You can have the fastest application server in the world, but if your application does not handle client-side interactions well your performance will still suffer. This post explores client-side optimizations for performance.

With the prior post getting metrics in place, now we shift focus to understanding the users and environment and how they can impact our performance.

Improving web application performance can be a monumental task, this is the first post in a series geared towards removing some of the complexity. Metrics are key for validation of performance changes, and a good starting point.

DNN provides two different caching mechanisms that can be configured to improve performance; ModuleCache and PageOutputCache. Proper configuration and use of these can make drastic improvements to performance.