So this is Part 7 of my CommunityServer to DotNetNuke blog series, unfortunately it is well over 7 months late, but better late than never I say. This will be a quick blog post talking about “URLs” and how you can handle the old CommunityServer URLs and redirect them to the proper DotNetNuke URLs. Why would you do this? SEO, bookmarks and existing links. You want people that try to access the CS urls to be redirected properly to the appropriate DotNetNuke URL, be it for a forum post, blog post, or other. This post isn’t going to cover all the specifics, as there are too many possible variations based on the configuration of your specific website, but hopefully it will provide you an overview of how I handled things in my conversion, and get you on the way to handling them in your conversion.

If you didn’t hear the news, DotNetNuke 6.0.1 was released yesterday, check out Joe’s blog post for more details.

On that note, I put out two new open source releases as well. I updated DNNSimpleArticle with a fix for DNN6 and made made a few other minor changes. As always, the module is released in C# and you can get the installable package, or the source package over on http://dnnsimplearticle.codeplex.com/. If you want to see the module in action check out http://www.bicycletips.com/

I also released an update for Multifunction, the World’s Best Free DotNetNuke Skin. It has a minor CSS fix for DNN6 (and 6.0.1). I also removed the custom actions menu it was using in favor of the new DotNetNuke 6 specific actions menu. MultiFunction is a C# skin, with both install and source packages available from http://multifunction.codeplex.com/

Be sure to rate both releases when you download!

Big thangs baby, today is a big day in the world of .NET. DotNetNuke 6 has been released. I won’t go into all of the details, Joe Brinkman has done that with a blog post over on DotNetNuke.com, but I will cover some of the highlights. First though, a little Too Short – Big Thangs (lyrics NSFW, and may be offensive, it is rap, get over it) (read the full post)

DotNetNuke 6 is coming, DotNetNuke 6 is coming! That’s right, we’re getting close, close enough that we had our first “beta” for DNN6 today. While we’ve had a couple of CTP (community technology preview) releases, the beta today has quite a bit of things wrapped up and addressed.

I had hoped to finish up my Community Server to DotNetNuke blog series tonight, but I realized there is just too much less to cover! I’m working tonight to get the HTTPModule that I created to handle the URL mapping from CommunityServer to DotNetNuke URLs into codeplex. I haven’t touched the code in a few months, and for simplicity sake I had just created using my standard DotNetNuke Module Template, which contains way more information than is necessary for a simple HTTPModule. I’m ripping out the module code and working on cleaning up the project/manifest so it will install properly as just an HTTPModule.