<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://weblogs.asp.net/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>A new way to Upgrade DotNetNuke</title><link>http://weblogs.asp.net/christoc/archive/2008/06/11/a-new-way-to-upgrade-dotnetnuke.aspx</link><description>If you've ever had me as an instructor for a DotNetNuke class , or heard me present at a user group or conference you've likely heard me say that I always use the DotNetNuke Install package when performing upgrades on my DNN sites. I rarely use the Upgrade</description><dc:language>en</dc:language><generator>CommunityServer 2007 SP1 (Build: 20510.895)</generator><item><title>re: A new way to Upgrade DotNetNuke</title><link>http://weblogs.asp.net/christoc/archive/2008/06/11/a-new-way-to-upgrade-dotnetnuke.aspx#7165865</link><pubDate>Mon, 10 Aug 2009 15:33:51 GMT</pubDate><guid isPermaLink="false">c06e2b9d-981a-45b4-a55f-ab0d8bbfdc1c:7165865</guid><dc:creator>Chris Hammond</dc:creator><author>Chris Hammond</author><description>&lt;p&gt;Hopefully you backed up your website and database so that you can rollback to the previous version&lt;/p&gt;
&lt;img src="http://weblogs.asp.net/aggbug.aspx?PostID=7165865" width="1" height="1"&gt;</description></item><item><title>re: A new way to Upgrade DotNetNuke</title><link>http://weblogs.asp.net/christoc/archive/2008/06/11/a-new-way-to-upgrade-dotnetnuke.aspx#7165863</link><pubDate>Mon, 10 Aug 2009 15:30:28 GMT</pubDate><guid isPermaLink="false">c06e2b9d-981a-45b4-a55f-ab0d8bbfdc1c:7165863</guid><dc:creator>Stephen Roberts</dc:creator><author>Stephen Roberts</author><description>&lt;p&gt;I upgraded my site from 5.1 to 5.1.1 and the upgrade did not go well. I need help. &lt;/p&gt;
&lt;img src="http://weblogs.asp.net/aggbug.aspx?PostID=7165863" width="1" height="1"&gt;</description></item><item><title>re: A new way to Upgrade DotNetNuke</title><link>http://weblogs.asp.net/christoc/archive/2008/06/11/a-new-way-to-upgrade-dotnetnuke.aspx#6657881</link><pubDate>Sat, 04 Oct 2008 21:42:05 GMT</pubDate><guid isPermaLink="false">c06e2b9d-981a-45b4-a55f-ab0d8bbfdc1c:6657881</guid><dc:creator>Chris Hammond</dc:creator><author>Chris Hammond</author><description>&lt;p&gt;That is not correct Bret. If you're on 4.6.2 or great I would use the upgrade package. Otherwise I would use the install package, be careful with the web.config file&lt;/p&gt;
&lt;img src="http://weblogs.asp.net/aggbug.aspx?PostID=6657881" width="1" height="1"&gt;</description></item><item><title>re: A new way to Upgrade DotNetNuke</title><link>http://weblogs.asp.net/christoc/archive/2008/06/11/a-new-way-to-upgrade-dotnetnuke.aspx#6656723</link><pubDate>Fri, 03 Oct 2008 17:46:21 GMT</pubDate><guid isPermaLink="false">c06e2b9d-981a-45b4-a55f-ab0d8bbfdc1c:6656723</guid><dc:creator>Bret</dc:creator><author>Bret</author><description>&lt;p&gt;So, I&amp;#39;m looking at upgrading a site from 4.3.5 to 4.9.0. If I&amp;#39;m understanding your advice, I should use the upgrade package to upgrade the core to 4.9.0, then upgrade each of the modules separately? (The upgrade package does NOT include modules as I understand it.)&lt;/p&gt;
&lt;img src="http://weblogs.asp.net/aggbug.aspx?PostID=6656723" width="1" height="1"&gt;</description></item><item><title>DotNetNuke 4.8.4 Released</title><link>http://weblogs.asp.net/christoc/archive/2008/06/11/a-new-way-to-upgrade-dotnetnuke.aspx#6269184</link><pubDate>Wed, 11 Jun 2008 22:33:48 GMT</pubDate><guid isPermaLink="false">c06e2b9d-981a-45b4-a55f-ab0d8bbfdc1c:6269184</guid><dc:creator>DotNetNuke Developer</dc:creator><author>DotNetNuke Developer</author><description>&lt;p&gt;To go along with my earlier post about DNN today, 4.8.4 has been released due to some minor security&lt;/p&gt;
&lt;img src="http://weblogs.asp.net/aggbug.aspx?PostID=6269184" width="1" height="1"&gt;</description></item></channel></rss>