DotNetNuke
Now that DotNetNuke 6.x has been out for a while and with the recent release of DotNetNuke 6.0.1 while I was on vacation I thought I'd take the time to write a must requested blog post regarding my thoughts on the DotNetNuke 6.x platform and performance. Keep in mind, these points are my own personal opinion and should be considered that only, so without further delay.
Read more...
Posted by Mitchel on Sunday, September 04, 2011
In my earlier blog post I mentioned that one of my favorite features of the new DotNetNuke 6.0 release is the ability to download and automatically install purchased extensions from SnowCovered within the installation. In this posting I'll walk through the functionality as well as give my disclaimer and recommendation in regards to using this process.
Read more...
Posted by Mitchel on Thursday, July 21, 2011
As many of you might not have heard yet DotNetNuke version 06.00.00 was released last night. You can read all about it on the Announcing DotNetNuke 6.0 page from DotNetNuke. In this blog post I'll talk a little bit about what it this release means to you as a user in the community as well as share some insights and recommendations that I have to make the transition easier, and we will finish with information on a special offer from a known DotNetNuke Vendor.
Read more...
Posted by Mitchel on Thursday, July 21, 2011
Like many people I have been building DotNetNuke Modules using Chris Hammond's DotNetNuke Module Template. It is a great template set and works well in 99.9% of cases. However, recently I have been building more and more complex module solutions for customers where within a single project I have a need to package up two or more "distinct" modules. Therefore I have one DotNetNuke Module Manifest and it will install multiple modules. Overall the process works great, but there is one small nuance, the filename, if you have two modules you will get xx.xx.xx.yy.yy.yy as the filename, which is the version of module 1, and the version of module two. In my case I just want the first module to show, and in this post I'll show you how.
Read more...
Posted by Mitchel on Thursday, July 07, 2011
One thing that can kill a DotNetNuke quite quickly is a module that goes "rogue" and starts throwing regular errors in the scheduler. This is especially the case when it comes to a module that might be heavily used. Not only do you just have the fact that you are having errors, but you also have the issues around the fact that you can't find TRUE errors in the log. In a world long ago, back in the DNN 4.4 - 4.8.x days there used to be an issue with certain modules that has apparently started to rear its ugly little head again and I'm not sure why. In this post I'll investigate this specific error type.
Read more...
Posted by Mitchel on Thursday, July 07, 2011
A while back I blogged about Creating DotNetNuke Scheduled Jobs and promised a "part two" article, this is that article. In the previous installment I talked about the process of creating and manually installing a scheduled job. This article is designed to take this to the next step and discuss how you interact with the Scheduler System to handle installation and other validation methods of scheduled jobs. I will explain the finer points in regards to checking to see if a job exists and creating or modifying a job.
Read more...
Posted by Mitchel on Sunday, April 17, 2011
For those of you not able to attend the Orlando Day of DotNetNuke and Orlando Code Camp events this weekend I wanted to take a few moments to post a quick bit of feedback on the event and also make those of you aware of some new presentation materials that I will be making available to the community over the next few weeks. (The first of which is available now!) See the full post for details!
Read more...
Posted by Mitchel on Saturday, March 26, 2011
I know that many of the readers of this blog manage their own webservers and i have a helpful tip to share about improving the initial load time of your webserver. Although this modification I am recommending is a SMALL change and has a small impact, it is still worth doing as it will improve the performance and reduce the amount of work that IIS has to do.
Read more...
Posted by Mitchel on Wednesday, March 09, 2011
Well, as I'm sure that most of you have figured out already, DotNetNuke Corporation announced yesterday that starting with Version 6.x of DotNetNuke the core will be using C# as the programming language. This change is something that has been talked about at community events in the past and various people have shared their comments on the potential decision, and even since yesterday people have voiced their opinions on it now that the change is official. With this post I'm going to share a few of my thoughts on this, and hopefully take a slightly different approach.
Read more...
Posted by Mitchel on Tuesday, March 01, 2011
So for a long time now I have been promising an article on creating DotNetNuke Scheduled jobs and finally I'm actually getting it written. This article is actually the first in a series of two articles. This one will start out with the programming process involved, and the general "manual" setup process to actually get the job going. The second article will focus on using the DotNetNuke API's to be able to validate and configure a scheduled job from within a module, making the user setup process easier.
Read more...
Posted by Mitchel on Tuesday, January 18, 2011
Previous Page
2 of 24
Next Page