As more and more people start working with DotNetNuke, IIS7, and .NET 4.0 it is important to note a few important potential problem areas when it comes to running DotNetNuke on the 4.0 framework. Recently I took a DNN 5.4.4 installation and tried running it under .NET 4.0 and without modifications, it was a complete failure, in this blog posting I will show you what needs to change to allow DotNetNuke to work as expected.
Read more...
Posted by Mitchel on Tuesday, July 27, 2010
In past blog postings I have provided what has become a bit of a "Guide to Selecting a DotNetNuke Hosting Provider." As with previous years it is about that time where there have been enough changes in the market and to DotNetNuke in general that I thought it was necessary for a 2010-2011 version of this information. In this article I will talk though the thought process that I use when working with current and potential customers to select their hosting plan, environment and provider. This document has been updated based on current information, in addition, prior to going through the recommendations below I strongly recommend reading my article “Shared, Virtual Private Server, Dedicated of Cloud Hosting” to become familiar with the different levels of hosting and also to review my "DotNetNuke Performance Configuration Best Practices" document to ensure that your DNN hosting plan is up to date.
Read more...
Posted by Mitchel on Monday, July 26, 2010
One of the most common questions that I get from users when it comes to deploying to deploying a DotNetNuke site is "DO I REALLY need all of those files?". My typical answer is something along the lines of yes and no. In this blog posting I want to talk in a bit more detail about some of the processes that I go through when installing a clean DotNetNuke installation and how I keep the footprint down on the disk space.
Read more...
Posted by Mitchel on Wednesday, July 07, 2010
I have had this blog posting all ready to go now for a good three to four weeks, but have been in deep internal conversation in regards to the posting of the article. I have decided that more than anything posting this publicly might stop some of the e-mails that I get bombarded with each and every day that start out with "what do I do" or "do you still believe in DNN".
Before I start the post I am NOT in any way, shape, or form pointing fingers or expressing any displeasure at the platform or any of the members involved. I am still a DotNetNuke core team member, I believe fully in the platform, and I will continue to adopt and recommend usage of the platform for the foreseeable future. The point of this post is very simple, to talk about what has been going on in the DotNetNuke community and my opinions on how to manage expectations and cope with the situation. Please remember the disclaimer that is posted at the bottom of this blog, these thoughts are mine and mine alone.
Read more...
Posted by Mitchel on Tuesday, June 22, 2010
Users that are familiar with DotNetNuke administration are most likely familiar with the old way of creating a custom registration page within a DotNetNuke portal. It was as simple as adding a new page, putting the modules you desired on the page including the "User Account" module to get the actual registration functionality. From there a simple change in "Site Settings" for the "User Page" and you are set to go! Well, for those of you working with DNN 5.2.3 and later (Possibly previous 5.x versions as well, I'm not 100% sure when the change was) will find out that the module definition I mention is no longer listed? What do you do now?
Read more...
Posted by Mitchel on Monday, April 26, 2010
I just posted a new article on my business blog, Business Continuity - Backup Strategies, DotNetNuke, and you. It covers the when/why of working with DotNetNuke from an administrators point of view.
Read more...
Posted by Mitchel on Friday, April 16, 2010
For those of you that have seen my comments on the DotNetNuke forums, my book, or the forum here on this site, you more than likely have noted my consistent notes that I recommend avoiding the "ObjectQualifier" setting within DotNetNuke at all costs. Most of the time I have simply put, I don't use it and recommend that you don't either, but have not given a very detailed explanation as to why I'm not a fan. Below I will share with you what the ObjectQualifer is, why it was created, and why I don't recommend using it.
Read more...
Posted by Mitchel on Tuesday, March 23, 2010
After talking with a number of clients since last week, I thought it would be worthwhile to make a post here with a formal warning regarding upgrades to DotNetNuke 5.2. As announced at OpenForce US, DotNetNuke 5.2 contains the Telerik Controls for ASP.NET, which is a very good thing for DotNetNuke as a whole, however, it can cause massive problems for individuals that are already using the Telerik Controls as a site upgrade can end up rendering portions, or the entire site unusable, until DLL versions are restored. In this post I will give a bit of information regarding the scenarios that I have encountered and some guidance on how to protect yourself from upgrade issues.
Read more...
Posted by Mitchel on Wednesday, December 02, 2009
Back in May of 2008 I wrote an article “Selecting a DotNetNuke Hosting Provider Revisited”. Well, being almost a year-and-a-half later I thought it would be good to provide a 2009-2010 follow-up to the article to update based on new information, updates to hosting plans/offerings, as well as DotNetNuke performance in general. In this article I will talk though the thought process that I use when working with current and potential customers to select their hosting plan, environment and provider. This document has been updated based on current information, in addition, prior to going through the recommendations below I strongly recommend reading my article “Shared, Virtual Private Server, Dedicated of Cloud Hosting” to become familiar with the different levels of hosting.
Read more...
Posted by Mitchel on Friday, October 30, 2009
About two months ago, I responded to a DotNetNuke question on StackOverflow.com with regard to automating the installation of modules within the installation. This is a question that I have seen many times, but with different business requirements and end desires, but the trend is the same, installing extensions one-by-one is an inefficient process, and with a heavily used site can cause performance issues that would impact regular traffic for an extended period of time. This is simply because there is a delay between each install, and with each install and update to the /bin directory the application recycles. Thankfully there is a method built into DotNetNuke that easily allows you to bulk install extensions, the rest of this article will show you how.
Read more...
Posted by Mitchel on Wednesday, October 14, 2009
 | An error has occurred.
Error: Mitchel Sellers' DotNetNuke, .NET, and Other Topics Blog is currently unavailable. |
| An error has occurred.
Error: Mitchel Sellers' DotNetNuke, .NET, and Other Topics Blog is currently unavailable. |