BlogEngine.NET is a wonderful blog platform (I consider that a CMS) that's easy to extend and the codebase isn't so massive that you can learn it quickly. Some of these, like DNN, are nightmares.
Popular .NET Web Content Management Systems (CMS) - Open Source
11–18 of 18 posts
Re: Popular .NET Web Content Management Systems (CMS) - Open Source
#12Is there a reason to use a .NET CMS other than the obvious (i.e. it's a .NET shop)?
You realize that it is possible that someone might like a CMS because of its features, not the language it was implemented in, right?
Re: Popular .NET Web Content Management Systems (CMS) - Open Source
#13We're a Python/Django shop with a few ASP.NET/C# projects every now and again. We use Django CMS for many of our clients, but we've used Umbraco for a few. It was aweful, the interface is fine for editing content, but building and templating a whole site through a web based client is painful. Trying to build extensions was daunting, especially with the free version, it seems like they have a Commercial version with a…
As of v4, Umbraco uses nested .master pages for page rendering which saves you from the "template stored in database" pain.
Re: Popular .NET Web Content Management Systems (CMS) - Open Source
#14I haven't found a single .NET CMS that doesn't drive me completely batty. I think most CMS tools, including non-.NET ones, break down when they start trying to be able to do all things for all people. It's debatable if any are able to pull this off (though admittedly I'm not up on current CMS tools to know if that world has improved.)
Because of that, I've been rolling my own basic backend for my own personal use on projects for myself, friends & family for about a half-year now; the ultimate goal being dead-simple templating using standard HTML pages, fast & secure data & code, and ease of extensibility. It does what it needs to. But, because it's domain-specific, I'm not trying to make it a general-purpose "CMS," so I currently don't have to worry about stuff like registration/authentication, comments, etc. I would never release it in its current state, though, and likewise I'd probably never plug a bunch of other junky code into it, expose a ton of dubiously-designed interfaces & reflection as "extensibility," require master pages (ew) or some custom markup language (ew x 2) to make templates, and call it a full CMS.
Re: Popular .NET Web Content Management Systems (CMS) - Open Source
#15DotNetNuke, also known as DNN, is the ideal platform for building professional websites with dynamic content and interactive features.
This made me laugh. My coworkers that have worked with DNN have many horror stories. I've never heard from a developer that used DNN and liked it. Given the superficiality of the descriptions, I assume all the info was copy/pasted from the marketing material for each project.
Re: Popular .NET Web Content Management Systems (CMS) - Open Source
#16DotNetNuke, also known as DNN, is the ideal platform for building professional websites with dynamic content and interactive features. This made me laugh. My coworkers that have worked with DNN have many horror stories. I've never heard from a developer that used DNN and liked it. Given the superficiality of the descriptions, I assume all the info was copy/pasted from the marketing material for each project.
DNN is a heap. My God, is it a codebase trainwreck. Apologies to any DNN devs that may be HNers, but holy cow is that an example of how serpentine code gets when you try to be all things to all people without a strong planning phase.
Re: Popular .NET Web Content Management Systems (CMS) - Open Source
#17Is there a reason to use a .NET CMS other than the obvious (i.e. it's a .NET shop)?
You realize that it is possible that someone might like a CMS because of its features, not the language it was implemented in, right?
Yes, that's my point. The OP is a list of .NET content management systems, not a list of CMSs that have broad or interesting features. Hence my question about why anyone would specifically want a .NET CMS.
Re: Popular .NET Web Content Management Systems (CMS) - Open Source
#18Earlier quoted context omitted.
You realize that it is possible that someone might like a CMS because of its features, not the language it was implemented in, right?
Yes, that's my point. The OP is a list of .NET content management systems, not a list of CMSs that have broad or interesting features. Hence my question about why anyone would specifically want a .NET CMS.
Blah my bad - I misunderstood you then. I thought you were just making a general "eewwwww .net" comment :p