Articles under DotNetNuke Best Practices
Almost a year ago we published to this blog our first whitepaper, "DotNetNuke Performance Best Practices", in that time the document has been downloaded over five thousand times and we have received numerous e-mails with feedback regarding the contents of the document, the basis of our recommendations and suggestions on how to expand the document.
...
A majority of the time when working with a business there is a strong focus on keeping things working, and leaving working items as they are. However, when it comes to ensuring that business can continue as usual it is important to make sure that not only you have processes in place for backups, but backups alone are not going to do everything for you. It is important to test/validate the backups and also to ensure that you are taking backups at all times that are necessary. Below we will discuss our stance on these two topics.
In the past few weeks on my personal blog I have published articles on "Selecting a DotNetNuke Hosting Provider" as well as "Shared, Virtual Private Server, Dedicated or Cloud Hosting". Between these two articles the topic of hosting selection has been pretty well discussed, however, based on questions/comments that have been provided to us s...
Over the past few months IowaComputerGurus has fielded more and more questions surrounding the "how" part of DotNetNuke module/extension development. Along with these questions have been requests for "best practices" and other general information that if followed will help developers create solutions that work well within the DotNetNuke platf...
One of the most common questions that I have been asked over the past 1-2 years is; "How do you make DotNetNuke perform well?". Over the past few months I have given a few presentations on basic configuration elements and how you can tune DotNetNuke for the best performance possible. I will also be giving a presentation on the topic at ...
Well, somehow “a week or two” turned into 10 months since I posted part 1 of this case study. Since then, DotNetNuke 5.1 brought a minor improvement to DNN’s XML sitemap implementation and has grown more web standards compliant, but other than that the points discussed so far in regards to SEO still apply. With that in mind, let’s refer back to my ...
Recently on Twitter we noticed a discussion regarding another DotNetNuke vendor and how their website was not based on the DotNetNuke platform. The discussions that followed came to a very clear conclusion, the act of dogfooding the technology you work with is very important. For example, a company that "specializes" in DotNetNuke solutions and uses Joomla to manage their corporate website portrays a conflicted image, either intentionally or not. We have noticed this since the beginning of our company and have taken a unique approach to the management of our website and I thought it would be nice to share a bit on how we see our website impacting our potential customers.