.Joe,

I need to clarify that I am in no way affiliated with the Umbraco team.  Yes, I like Umbraco, but the reason is because it is a .Net based system, the same reason I like mojoPortal.  Let me repeat.. I like mojoPortal.  It is a very well put together product.  My primary reason for choosing Umbraco over mojoPortal, was the ease of developing extensions and the overall feel of the system.

I am sorry if John Sanborn had any issues on my blog, he would be the first to report it
My blog uses BlogEngine.Net and my main site is using Umbraco.

I am a huge supporting of .Net and opensource CMS.  I use varying systems depending on my need.

Daniel Bardi
www.danielbardi.com
www.dascoba.com
cmstv.net

You are correct.  The post title is a bit mis directed.  I will do some more research and post a more indepth review.  Fair?

As far as why I use BlogEngine.Net.  It's a great .Net blogging app, just that simple.  It's extensible and easy to use.  Umbraco is a great platform for CMS based web applications (development framework), but blogengine is focused on blogging.  I enjoy both platforms.  I look at web applications as tools and I decided on using a particular tool for a particular purpose.  You should read my post on "why I use blogengine.net" for blogging.  I support several opensource applications; each one has something it does better than the others.

I was glad to see this conversation between two respective experts on the two open source CMS systems I am considering for my business, and I want to take this opportunity to pose a question to BOTH of you regarding how to accomplish my goal in using an open source CMS.  You see, I am actually writing an iPhone application that manages an entity that is essentially a type of content (a "quote").  As with many iPhone applications, it is useful to have a community web site (usually built using a CMS system), to perform some small percentage of tasks and allow those that don't have iPhones to have a way to view your content (in this case, quotes are sent to other people with little notes attached that the user provides).  To implement this, I need the following:

• To extend the content type "namespace" and use custom tables and my OWN schema for saving the data.  This seems to be more easily accomplished with Umbraco.
• To extend the way the content is displayed in a way that can be partially controlled by site installed templates.  While the display can be more easily customized with Umbraco, it seems that mojoPortal might win on this one, since there is an easy way to control the entire look and feel of a site centrally without building your own structure to do so--like it seems you would have to with Umbraco.
• Have the resulting customization tie into the user namespace and community functions that the CMS provides without marrying me to it in a way that prevents me from migrating my data services that my iPhone application will use and keep the same code base.
• Be able to use the same security model for both web and iPhone--but have the iPhone leverage an OAuth-driven model for authentication to a REST API (implemented with WCF).  In other words, the user should use the same User ID and password in both places.

GQAdonis,

You should also read "A Complete Newbie's Guide To Umbraco CMS".

Thanks so much to the both of you for the detailed and quick responses.  There was some admitted ignorance in my asking my question, because I had had very little contact with either CMS before now--I had done more with Drupal, Joomla!, and Telligent Community Server.  I eliminated Drupal and Joomla! on the basis of wanting to have a single code base based on .NET for server side functionality.  I eliminated Community Server because it was expensive and did not improve function or extensibility any better than open source solutions.

Bottom line is this is what I found since I have reviewed the materials both of you sent:

• Both solutions offer ways to accomplish my goal quite nicely.  Setting up a development environment for Umbraco was slightly easier and natural to do, and I like the way "packages" are done so fluidly.  It reminds me of the neat fluidity of Wordpress in this regard (ability to search for and load packages from the Internet in place as an administrative function).
• After following the instructions Joe has posted on setting up the development environment manually and watching his video going over the code, I had a much better understanding of what was going on and was able to get myself started.  I do wish there were options other than adding all those post-build steps to copy assemblies, etc., however, because my "quote engine"--the back end services infrastructure--makes use of Microsoft Enterprise Patterns for DI and has its own layered architecture, which means about 6-10 more assemblies to copy than in Joe's "WebStore", which is the example I followed.
• As far as theming, mojoPortal seems to have a slight edge for what I am doing although, the XSLT-based model in Umbraco is VERY similar and compatible with the work I am doing on the iPhone application, where I am using XSLT, JTemplate (with JQuery), and other template methods to create HTML on the fly for use in "hybrid" views (HTML local to iPhone and used for display in WebKit while data comes from my back end services mentioned above).  There is some good potential to share XSLT templates, I believe in the future, although this will take more time than I want to spend figuring it out right now.  On this point, mojoPortal still wins for me, because I don't have to create my own theming theory or infrastructure like it seems I have to in Umbraco (unless someone can point me to how I can do it easily without giving my graphic design partner--who knows HTML and typical models for theming like Wordpress and ASP.NET--a heart attack and making HIS job tougher).
• Authentication with the model I am looking for can be implemented either place, but I, at this point, think my intended model for providing applications (iPhone, BlackBerry, and other web based integrations to other sites and widget frameworks) might be more quickly done with mojoPortal by a very slight margin.
• Administration facilities are prettier, cooler, and a bit more functional and extensible--in my quick analysis--with Umbraco.  Like I said, I love the packaging, but I also feel this could be accomplished with mojoPortal by extending it a bit to process zipped files of resources with a manifest XML file somewhere in there telling mojoPortal where to find everything (like the features XML and setup and tear down components).