Trying to make the case against Drupal and find a ASP .NET CMS solution. I'm working on making a case against Drupal to a colleague who is redesigning a static website into something more substantial with a 3rd party design firm. They have really no idea what they are going to do to the site at this point beyond that it must change to something that allows collaboration and workflow (changes & approval) and the design firm is really pushing Drupal since they have a developer on staff.

We had a short meeting in which they more or less threw around buzz words (open source, community) which mean nothing to us since we run our servers on Windows Server 2003, IIS, .NET, and Microsoft SQL. So adding a Linux based server for this individual website is going to clutter things up PLUS we already have our own proprietary contact logging system relational database / newsletter mailer written in ASP .NET written by our inhouse contract developer.

What I know that they will need is hooks into a MS SQL database, ability to have very different sections of the site, forums, social media integration, blogs, built in searching (we already have a Google Mini too), event registration w/ hooks into MS SQL, along with a way to organize many PDFs.

I should also add that we are going to implement Microsoft Sharepoint 2010 later in the year but this site redesign/revamp can't wait for that.

What solutions exist for ASP .NET CMS's? Cost isn't a huge issue but ones that I have been rounding up are Sitefinity , Dotnetnuke, and DotCMS