Dave Burke : Freelance .NET Web Developer specializing in Online Communities

Rockin' with BlogEngine.NET 1.45

It was important for me to upgrade DBVT.COM/BLOG from BlogEngine.NET 1.4 to 1.45 as soon as possible so I could focus on other Open Source Online Community application pursuits in the queue.  This weekend presented a window of opportunity to upgrade and I took it.

I upgraded my blog once a month since moving to BlogEngine.NET in June.  In contrast, DBVT.COM Community Server upgrades occurred once a year.  Things are obviously more fluid for me now, which is an aspect of successful Open Source applications like BlogEngine.NET that I honestly was not anticipating.  Based on my experience over the last two months I say, "bring it on!"  While I don't thrill to the idea of updating my blog, being part of an active community like BlogEngine.NET is worth it.

I spent between 6-to-8 hours upgrading from 1.4 to 1.45.  That included WinMerge pre-upgrade analysis, the upgrade on my office development server, then updating and testing DBVT.COM.  You have to remember that DBVT.COM is heavily customized, so I'm essentially recreating a themed site with each upgrade.  Maybe Mads, Al and crew will have a BE.NET 1.5 release ready in another month.  If so, a 9/10/08 BE.NET 1.5 release would keep the upgrade frequency sufficient for me to refine the process and reduce the upgrade time even further.

A lot of work in the BlogEngine.NET 1.45 Release was done with user account management, yet I was able to reconfigure my web.config to support shared ASPNET Membership setup without skipping a beat.  There may be work to do in the future as functional enhancements are added in BE.NET based on the brand new be_Users and be_Roles tables, but we'll deal with those if they arise.

One "glitch" I encountered during the upgrade was a sporadic "Root Element was Missing" error, which I discovered was related to the fact that none of my BlogEngine.NET Extensions were loading.  Thanks to the active BE.NET discussions on CodePlex.com I was able to quickly find a solution, which was to update ExtensionType = "1" in the be_DataStoreSettings table for all existing extensions.  Funny how such a simple SQL query can bring so much joy to an upgrade.

So that's it.  I'm now running BlogEngine.NET 1.45.  The mark of a successful upgrade is that it is uneventful.  Unless I hear from you otherwise, I'll assume, as Tom Cruise said in Top Gun on his chances of getting lucky with Kelly McGillis in the women's bathroom, "It's looking good so far."

Comments (7) | Post RSS RSS comment feed

Posted on 8/10/2008 8:52:29 PM by Dave Burke
Categories: BlogEngine.NET
Tags: No tags for this post

Related posts

Comments

8/11/2008 3:15:54 AM Permalink

Love the Top Gun analogy.

You've certainly been singing her praises ;)

And espoused the "need for speed!" with BlogEngine.

And given how quickly you've gotten a custom site down, it's almost doing a "buzz the tower" with the upgrades Smile

Is it saving you enough time for your oiled up volleyball sessions?

Sorry Dave, I just couldn't help myself!

Andrew Tobin Australia |

8/11/2008 7:31:39 AM Permalink

Brown Coat, You've demonstrated that my upgrade post was a much more target rich environment for jokes than I would have ever guessed. Thanks for the big Monday morning laugh!  

Dave Burke United States |

8/11/2008 7:30:35 PM Permalink

Hey Dave, did your upgrade mess up the RSS feeds?  I'm getting double posts for everything, even the ones in history.

Bill Bosacker United States |

8/11/2008 7:42:28 PM Permalink

Thanks for this, Bill!  I'm really flattered you're subscribed to two different dbvt.com feed urls!  Smile  

I did make a feed change, that was redirecting my old Community Server RSS.ASPX directly to my feedburner feed url.  Before it was redirecting to BE.NET's default syndication.axd.  The thing is, for testing and monitoring purposes I have readers pointing to /blog/rss.aspx, /blog/syndication.axd, and to http://feeds.feedburner.com/daveburke.  I'm not seeing duplication in any of them.  What do you think I'm missing?

Dave Burke United States |

8/11/2008 8:12:28 PM Permalink

I see what the problem is.  When you changed the links to feedburner it created a whole new set of items in the RSS feed as the link changed, thus the reason everything doubled.  New posts should only have single links, unless you change it again.  Smile

I did think of a downside of going with the feedburner passthrough though.  If you stop using feedburner, all of these mirrored links will no longer work even though the post still exists as the feedburner pass through will be broken.  I'm using the following for my mirror:

dbvt.com/.../rss.aspx

Bill Bosacker United States |

8/11/2008 8:16:58 PM Permalink

Bill, again, thanks.  Let me know on future post reception.  And yeah, I've been thinking about the post-feedburner issues recently.  Feedburner supplies a termination function that redirects to a url of your choosing, so hopefully it won't be too painful would it become necessary.  

Dave Burke United States |

8/11/2008 8:17:23 PM Permalink

P.S.  I only allow mirrors to use exceprts as a mirror is not the owner of the feed and the original post could be changed at any time.  RSS does not support update notifications, so if the entire post was mirrored, changes would be lost.

Bill Bosacker United States |

Comments are closed

This site was built with the Sueetie .NET Open Source Community Framework. Learn more about Sueetie at Sueetie.com.