What's up with www.Rochester-Consulting.com?

If you have visited www.Rochester-Consulting.com you probably have noticed that it's currently requiring authorization.  We're in the process of rolling out a brand new website based on SharePoint 2003 and so we have access to it locked down while we are working on it. 

Along with information about the company I'm also going to be putting up sample code, articles, resources and other content that .NET developers might find useful.  I'm also hoping to have a discussion forum for people to talk about any of the content they see. 

The site will be live in a couple of weeks, so please pardon our dust and check back soon!

3 Comments

  • So what made you decide to use a tool primarily designed for collaboration as a content management system? Sharepoint has some really nice qualities that are also present in a good CMS but it's not a CMS. I ask because I'm seeing more and more of this type of implementation. I've done extensive work with major CMS products and Sharepoint and I'd never use Sharepoint for a corporate site. I'd use Sharepoint for an intranet or extranet but not a corporate site.

  • I decided (with much head scratching) to use SharePoint for two reasons. The first is that while I would love to be able to take the time to develop an extensible website using ASP.NET 2.0 and the cool new features like Personalization and Membership, I simply don't have that much time to devote. Funny thing, my paying clients seem to want me to spend my days working on their applications. :-)



    The second reason is that I really like SharePoint as a tool and want to learn more about how it works. So, while it may have a bit of a higher startup time for me to learn how to customize it properly, once it's done it will have proven to be a great learning experience (which I'm sure I'll blog about as it seems appropriate).

  • Actually, I know all about DotNetNuke. I used an older version to create www.central-penn.net back in the days when I was running that User Group. While DotNetNuke is pretty cool, it's unlikely that I would be able to leverage any new-found insights with my current or potential clients as I hope to be able to do with SharePoint.

Comments have been disabled for this content.