Fog Creek Software
Discussion Board




Welcome! and rules

Joel on Software

.NET Content Management

I'm looking for a fairly simple to use ASP.NET-based CMS for a project I'm working on. I've looked at DotNetNuke and Rainbow Portal, both of which offer the source code; of these DotNetNuke seems to be the more developed. I can work with either VB.NET or C#, so either language is fine, but I'd prefer C#. I'm not able to spend a lot of money on this, so I'm looking for either Open Source or fairly cheap. Any suggestions? Am I overlooking something? Thanks!

Josh
Friday, March 04, 2005

Whats wrong with the two you just mentioned?

Full Name
Friday, March 04, 2005

I may actually use DotNetNuke, as it looks to be the more developed of the two. However, being as general as they are, they don't have all the features I'm looking for, such as granular article management. I could develop a module for this, and I might, but I'd also like a better URL rewriting system that I've seen in several of the PHP solutions.

Essentially, I just want to know if there are any other ASP.NET CMSs worth looking at.

Josh
Saturday, March 05, 2005

We've just started using <a href="http://www.communityserver.org">CommunityServer</a> over at <a href="http://www.madprops.org">our site</a>. Seems to work pretty well.

Matt Hamilton
Sunday, March 06, 2005

... and Matt discovers that hyperlinks don't really work in the forum ... :)

Matt Hamilton
Sunday, March 06, 2005

I picked up Real World ASP.NET: Building a Content Management System (http://www.contentmgr.com) a few weeks ago out of having similar needs as Josh. It appears to detail a particular CMS system built by the author, he calls it CMS.NET. The source code hasn't seen significant update, but I don't believe that's the point of the source offering--it's a learning tool.

I am also torn between doing it myself or using DotNetNuke. I think if you hare doing a substantial number of sizable CMS-backed websites, and you think the headache of managing them over the long time makes you shy about baby-sitting the code all by yourself--then your investment in DotNetNuke would be well worth it.

If you are just doing it for your personal homepage or your cousin's little ecommerce site and it's fire and forget--you might just want to implement something yourself if dead-line is no problem--it'd be a good learning experience.

Li-fan Chen
Monday, March 28, 2005

*  Recent Topics

*  Fog Creek Home