Stuart,

Thanks for your feedback on your personal experiences with Sharepoint.  They are very helpful.  I have read the same complaint about Sharepoint that you can't turn off features that you don't have priveleges for.  The security features of DNN definitely set it apart and it appears like they are getting even better in 5.0.  I have 5.0 RC2 installed on my machine and started working with it last week.  I like some of the improvements that I have seen.

Some of the other issues I have read about with Sharepoint is that you have to manipulate the web.config to install webparts where as you can just upload a new module to DNN.  This is very beneficial since the web servers will be sitting in a DMZ that we won't be able to access directly very easily if at all.  The skinning capabilities are far better than Sharepoints master pages. I had also read that Sharepoints menu system is difficult to work with.

The only benefit I see this organization going with Sharepoint is for standardization since they are using in for an Intranet already.  This is a weak argument in my book.  Thanks for you input.

Derrick

This debate has been raging for a long time... and I must admit I am guilty of feeding it as well ( with some of my past blog posts ). The reality is that DotNetNuke and SharePoint solve different problems. And the sooner that we get people to focus on the differences rather than the similarities, the stronger DotNetNuke' market positioning will be. SharePoint is a great Intranet solution - especially in large corporate environments where there are a lot of MS Office documents and collaboration requirements. DotNetNuke is a great Extranet or Internet solution, and is also well suited to small to medium-sized Intranets where a high degree of MS Office integration is not necessary. Going forward we are planning to position DotNetNuke as the perfect compliment to your SharePoint deployment. We will achieve this by providing some SharePoint integration capabilities ( ie. the ability to expose data from SharePoint in DotNetNuke, and potentially the ability to run WebParts within DotNetNuke ). By doing this, it moves us away from an either/or decision ( ie. a zero-sum game ) and provides users and customers with a comprehensive solution to their Intranet AND Internet requirements.

Jeff,

The $40,000 is Microsofts price for using MOSS for Internet facing sites.  This is the cost quoted directly from the Microsoft site ( http://office.microsoft.com/en-us/sharepointserver/FX102176831033.aspx ).