<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0">
  <channel xmlns:blog="http://www.dotnetnuke.com/blog/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:trackback="http://madskills.com/public/xml/rss/module/trackback/">
    <title>Mitchel Sellers</title>
    <description>My personal blog on DotNetNuke.com where I share information related to general DotNetNuke programming and other items not related to my involvement in the DotNetNuke Documents Module project</description>
    <link>http://www.dotnetnuke.com/Resources/Blogs/BlogId/221.aspx</link>
    <language>en-US</language>
    <webMaster>msellers@iowacomputergurus.com</webMaster>
    <pubDate>Thu, 09 Feb 2012 08:45:05 GMT</pubDate>
    <lastBuildDate>Thu, 09 Feb 2012 08:45:05 GMT</lastBuildDate>
    <docs>http://backend.userland.com/rss</docs>
    <generator>Blog RSS Generator Version 4.0.0.0</generator>
    <item>
      <title>DotNetNuke World 2011 - My Thoughts</title>
      <link>http://www.dotnetnuke.com/Resources/Blogs/EntryId/3220/DotNetNuke-World-2011-My-Thoughts.aspx</link>
      <description>&lt;p&gt;As most of you know I was at the DotNetNuke World 2011 event in Orlando Florida this past week, and I thought I would give a quick recap of my experience with the event and share how much different I felt this event was in comparison to the previous DotNetNuke Connections events.  To help try and give proper justice to the topic, I'm going to break my review out in a few different categories to help make it a bit more understandable, and without further delay, here we go!&lt;/p&gt;&lt;div class="category"&gt;Category: &lt;a href=http://www.dotnetnuke.com/Resources/Blogs/CatID/14.aspx&gt;Events&lt;/a&gt;&lt;/div&gt;</description>
      <author>msellers@iowacomputergurus.com</author>
      <category domain="http://www.dotnetnuke.com/Resources/Blogs/CatID/14.aspx">Events</category>
      <comments>http://www.dotnetnuke.com/Resources/Blogs/EntryId/3220/DotNetNuke-World-2011-My-Thoughts.aspx#Comments</comments>
      <slash:comments>1</slash:comments>
      <guid isPermaLink="true">http://www.dotnetnuke.com/Resources/Blogs/EntryId/3220/DotNetNuke-World-2011-My-Thoughts.aspx</guid>
      <pubDate>Sun, 13 Nov 2011 12:20:36 GMT</pubDate>
      <trackback:ping>http://www.dotnetnuke.comDesktopModules/BlogTrackback.aspx?id=3220</trackback:ping>
    </item>
    <item>
      <title>Securing DotNetnuke Installs - Passwords</title>
      <link>http://www.dotnetnuke.com/Resources/Blogs/EntryId/3193/Securing-DotNetnuke-Installs-Passwords.aspx</link>
      <description>A while back I released a tool called Secure My Install that was designed to help people take existing DotNetNuke sites and change the way that they store passwords to use a more secure process.  Many people have used that module successfully to convert their sites, however, I never took the time to share the few small steps that are needed to simply "secure" your site as soon as you set it up so that you can avoid all of the hassle in the beginning.  In this post I'll walk through the simple process of changing your configuration to go from Encrypted Passwords to Hashed passwords and a bit of detail as to "why" you want to make the change.&lt;div class="category"&gt;Category: &lt;a href=http://www.dotnetnuke.com/Resources/Blogs/CatID/10.aspx&gt;Security&lt;/a&gt;&lt;/div&gt;</description>
      <author>msellers@iowacomputergurus.com</author>
      <category domain="http://www.dotnetnuke.com/Resources/Blogs/CatID/10.aspx">Security</category>
      <comments>http://www.dotnetnuke.com/Resources/Blogs/EntryId/3193/Securing-DotNetnuke-Installs-Passwords.aspx#Comments</comments>
      <slash:comments>0</slash:comments>
      <guid isPermaLink="true">http://www.dotnetnuke.com/Resources/Blogs/EntryId/3193/Securing-DotNetnuke-Installs-Passwords.aspx</guid>
      <pubDate>Fri, 07 Oct 2011 19:13:43 GMT</pubDate>
      <trackback:ping>http://www.dotnetnuke.comDesktopModules/BlogTrackback.aspx?id=3193</trackback:ping>
    </item>
    <item>
      <title>DotNetNuke 6.0.1 Performance And You</title>
      <link>http://www.dotnetnuke.com/Resources/Blogs/EntryId/3166/DotNetNuke-6-0-1-Performance-And-You.aspx</link>
      <description>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, I'll answer the most common questions that I get.&lt;div class="category"&gt;Category: &lt;a href=http://www.dotnetnuke.com/Resources/Blogs/CatID/9.aspx&gt;Development&lt;/a&gt;&lt;/div&gt;</description>
      <author>msellers@iowacomputergurus.com</author>
      <category domain="http://www.dotnetnuke.com/Resources/Blogs/CatID/9.aspx">Development</category>
      <comments>http://www.dotnetnuke.com/Resources/Blogs/EntryId/3166/DotNetNuke-6-0-1-Performance-And-You.aspx#Comments</comments>
      <slash:comments>0</slash:comments>
      <guid isPermaLink="true">http://www.dotnetnuke.com/Resources/Blogs/EntryId/3166/DotNetNuke-6-0-1-Performance-And-You.aspx</guid>
      <pubDate>Sun, 04 Sep 2011 15:06:03 GMT</pubDate>
      <trackback:ping>http://www.dotnetnuke.comDesktopModules/BlogTrackback.aspx?id=3166</trackback:ping>
    </item>
    <item>
      <title>DotNetNuke Documents 05.00.00 Released and Road Ahead</title>
      <link>http://www.dotnetnuke.com/Resources/Blogs/EntryId/3106/DotNetNuke-Documents-05-00-00-Released-and-Road-Ahead.aspx</link>
      <description>It has been a long time in the running, honestly too much time, but finally the DNN Documents Module version 05.00.00 has been released.  This release was critical as it resolved a number of issues that existed with the last "stable" version and the more problematic issues with some of the other releases that were completed in the interm.  Now that we have this milestone behind us, where does the module go now?&lt;div class="category"&gt;Category: &lt;a href=http://www.dotnetnuke.com/Resources/Blogs/CatID/5.aspx&gt;Extension Forge&lt;/a&gt;&lt;/div&gt;</description>
      <author>mitchel.sellers@gmail.com</author>
      <category domain="http://www.dotnetnuke.com/Resources/Blogs/CatID/5.aspx">Extension Forge</category>
      <comments>http://www.dotnetnuke.com/Resources/Blogs/EntryId/3106/DotNetNuke-Documents-05-00-00-Released-and-Road-Ahead.aspx#Comments</comments>
      <slash:comments>0</slash:comments>
      <guid isPermaLink="true">http://www.dotnetnuke.com/Resources/Blogs/EntryId/3106/DotNetNuke-Documents-05-00-00-Released-and-Road-Ahead.aspx</guid>
      <pubDate>Thu, 07 Jul 2011 12:43:20 GMT</pubDate>
      <trackback:ping>http://www.dotnetnuke.comDesktopModules/BlogTrackback.aspx?id=3106</trackback:ping>
    </item>
    <item>
      <title>Auto Packaging Multiple Modules in DNN</title>
      <link>http://www.dotnetnuke.com/Resources/Blogs/EntryId/3105/Auto-Packaging-Multiple-Modules-in-DNN.aspx</link>
      <description>&lt;p&gt;Like many people I have been building DotNetNuke Modules using Chris Hammond's &lt;a href="http://christoctemplate.codeplex.com" target="_blank"&gt;DotNetNuke Module Template&lt;/a&gt;.  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.&lt;/p&gt;&lt;div class="category"&gt;Category: &lt;a href=http://www.dotnetnuke.com/Resources/Blogs/CatID/9.aspx&gt;Development&lt;/a&gt;&lt;/div&gt;</description>
      <author>msellers@iowacomputergurus.com</author>
      <category domain="http://www.dotnetnuke.com/Resources/Blogs/CatID/9.aspx">Development</category>
      <comments>http://www.dotnetnuke.com/Resources/Blogs/EntryId/3105/Auto-Packaging-Multiple-Modules-in-DNN.aspx#Comments</comments>
      <slash:comments>0</slash:comments>
      <guid isPermaLink="true">http://www.dotnetnuke.com/Resources/Blogs/EntryId/3105/Auto-Packaging-Multiple-Modules-in-DNN.aspx</guid>
      <pubDate>Thu, 07 Jul 2011 12:40:32 GMT</pubDate>
      <trackback:ping>http://www.dotnetnuke.comDesktopModules/BlogTrackback.aspx?id=3105</trackback:ping>
    </item>
    <item>
      <title>WAP Projects and DNN TextEditor</title>
      <link>http://www.dotnetnuke.com/Resources/Blogs/EntryId/3074/WAP-Projects-and-DNN-TextEditor.aspx</link>
      <description>&lt;p&gt;Almost two years ago I blogged about &lt;a href="http://www.mitchelsellers.com/blogs/articletype/articleview/articleid/314.aspx"&gt;How To Get Design-Time Support for DotNetNuke Controls&lt;/a&gt; on my personal blog, and back then the solution seemed to be the easiest, just change one setting in your project and everything was just fine.  Well, as the years have progressed and people have downloaded and worked with projects I've ran into a few issues with this route and now have a better solution for this.&lt;/p&gt;&lt;div class="category"&gt;Category: &lt;a href=http://www.dotnetnuke.com/Resources/Blogs/CatID/9.aspx&gt;Development&lt;/a&gt;&lt;/div&gt;</description>
      <author>msellers@iowacomputergurus.com</author>
      <category domain="http://www.dotnetnuke.com/Resources/Blogs/CatID/9.aspx">Development</category>
      <comments>http://www.dotnetnuke.com/Resources/Blogs/EntryId/3074/WAP-Projects-and-DNN-TextEditor.aspx#Comments</comments>
      <slash:comments>0</slash:comments>
      <guid isPermaLink="true">http://www.dotnetnuke.com/Resources/Blogs/EntryId/3074/WAP-Projects-and-DNN-TextEditor.aspx</guid>
      <pubDate>Thu, 09 Jun 2011 08:05:27 GMT</pubDate>
      <trackback:ping>http://www.dotnetnuke.comDesktopModules/BlogTrackback.aspx?id=3074</trackback:ping>
    </item>
    <item>
      <title>Preparing for Next Release of Documents Module</title>
      <link>http://www.dotnetnuke.com/Resources/Blogs/EntryId/3061/Preparing-for-Next-Release-of-Documents-Module.aspx</link>
      <description>I'll admit from the start that it has been a long time coming, but I am working on resolving issues and handling feature requests for the Documents Module.  As part of this, I would like to reach out to the community for some suggestions and feedback on the features that you would like to see.&lt;div class="category"&gt;Category: &lt;a href=http://www.dotnetnuke.com/Resources/Blogs/CatID/9.aspx&gt;Development&lt;/a&gt;&lt;/div&gt;</description>
      <author>msellers@iowacomputergurus.com</author>
      <category domain="http://www.dotnetnuke.com/Resources/Blogs/CatID/9.aspx">Development</category>
      <comments>http://www.dotnetnuke.com/Resources/Blogs/EntryId/3061/Preparing-for-Next-Release-of-Documents-Module.aspx#Comments</comments>
      <slash:comments>2</slash:comments>
      <guid isPermaLink="true">http://www.dotnetnuke.com/Resources/Blogs/EntryId/3061/Preparing-for-Next-Release-of-Documents-Module.aspx</guid>
      <pubDate>Thu, 19 May 2011 17:17:33 GMT</pubDate>
      <trackback:ping>http://www.dotnetnuke.comDesktopModules/BlogTrackback.aspx?id=3061</trackback:ping>
    </item>
    <item>
      <title>DotNetNuke Scheduled Jobs Using the API</title>
      <link>http://www.dotnetnuke.com/Resources/Blogs/EntryId/3036/DotNetNuke-Scheduled-Jobs-Using-the-API.aspx</link>
      <description>A while back I blogged about &lt;a _fcksavedurl="http://www.mitchelsellers.com/blogs/articletype/articleview/articleid/354/creating-dotnetnuke-scheduled-jobs.aspx" href="http://www.mitchelsellers.com/blogs/articletype/articleview/articleid/354/creating-dotnetnuke-scheduled-jobs.aspx"&gt;Creating DotNetNuke Scheduled Jobs&lt;/a&gt; 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/modifying jobs.&lt;div class="category"&gt;Category: &lt;a href=http://www.dotnetnuke.com/Resources/Blogs/CatID/9.aspx&gt;Development&lt;/a&gt;&lt;/div&gt;</description>
      <author>msellers@iowacomputergurus.com</author>
      <category domain="http://www.dotnetnuke.com/Resources/Blogs/CatID/9.aspx">Development</category>
      <comments>http://www.dotnetnuke.com/Resources/Blogs/EntryId/3036/DotNetNuke-Scheduled-Jobs-Using-the-API.aspx#Comments</comments>
      <slash:comments>2</slash:comments>
      <guid isPermaLink="true">http://www.dotnetnuke.com/Resources/Blogs/EntryId/3036/DotNetNuke-Scheduled-Jobs-Using-the-API.aspx</guid>
      <pubDate>Sun, 17 Apr 2011 14:02:25 GMT</pubDate>
      <trackback:ping>http://www.dotnetnuke.comDesktopModules/BlogTrackback.aspx?id=3036</trackback:ping>
    </item>
    <item>
      <title>Creating DotNetNuke Scheduled Jobs</title>
      <link>http://www.dotnetnuke.com/Resources/Blogs/EntryId/2941/Creating-DotNetNuke-Scheduled-Jobs.aspx</link>
      <description>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.&lt;div class="category"&gt;Category: &lt;a href=http://www.dotnetnuke.com/Resources/Blogs/CatID/9.aspx&gt;Development&lt;/a&gt;&lt;/div&gt;</description>
      <author>msellers@iowacomputergurus.com</author>
      <category domain="http://www.dotnetnuke.com/Resources/Blogs/CatID/9.aspx">Development</category>
      <comments>http://www.dotnetnuke.com/Resources/Blogs/EntryId/2941/Creating-DotNetNuke-Scheduled-Jobs.aspx#Comments</comments>
      <slash:comments>2</slash:comments>
      <guid isPermaLink="true">http://www.dotnetnuke.com/Resources/Blogs/EntryId/2941/Creating-DotNetNuke-Scheduled-Jobs.aspx</guid>
      <pubDate>Tue, 18 Jan 2011 13:40:34 GMT</pubDate>
      <trackback:ping>http://www.dotnetnuke.comDesktopModules/BlogTrackback.aspx?id=2941</trackback:ping>
    </item>
    <item>
      <title>Why I Use DotNetNuke</title>
      <link>http://www.dotnetnuke.com/Resources/Blogs/EntryId/2931/Why-I-Use-DotNetNuke.aspx</link>
      <description>As I get back into blogging here on DotNetNuke.com I thought I would take a quick moment to answer publicly one of the most common questions that I am asked: Why do you use DotNetNuke?.  So in this posting I'll give my short description on why I started using DotNetNuke back in 2006 and why I'm still so fond of the product today!&lt;div class="category"&gt;Category: &lt;a href=http://www.dotnetnuke.com/Resources/Blogs/CatID/16.aspx&gt;Community&lt;/a&gt;&lt;/div&gt;</description>
      <author>msellers@iowacomputergurus.com</author>
      <category domain="http://www.dotnetnuke.com/Resources/Blogs/CatID/16.aspx">Community</category>
      <comments>http://www.dotnetnuke.com/Resources/Blogs/EntryId/2931/Why-I-Use-DotNetNuke.aspx#Comments</comments>
      <slash:comments>0</slash:comments>
      <guid isPermaLink="true">http://www.dotnetnuke.com/Resources/Blogs/EntryId/2931/Why-I-Use-DotNetNuke.aspx</guid>
      <pubDate>Fri, 31 Dec 2010 16:05:22 GMT</pubDate>
      <trackback:ping>http://www.dotnetnuke.comDesktopModules/BlogTrackback.aspx?id=2931</trackback:ping>
    </item>
  </channel>
</rss>
