Monday, February 14, 2011

Out of box SharePoint Development

DO NOT write code if you don't have to.

I am a developer and I love coding. However, I find that not to write code, when the requirements can be fulfilled using OOB, is the way to make a SharePoint development project successful.
Yes, go codeless in a SharePoint development project.

Here are pros for going OOB:
  1. No need to write code
  2. No need to debug code
  3. No need to test code
  4. No need to optimize code, such as cache, log, exception handling, etc.
  5. Easier to understand (not always)
  6. Easier to deploy (not always)
  7. Shorter development cycle
  8. Save time and $
And of course there are cons:
  1. Harder to debug and test
  2. Limited options for optimization
  3. May not be feasible
  4. May be harder to deploy

Future of the SharePoint is OOB only, Sandbox solutions in SharePoint 2010 is the first step towards it.


  1. There are certainly a lot more details to take into consideration, but thanks for sharing this post. SharePoint Consulting can provide a business with custom web parts and administrative tools.

  2. Nice post. I learn something more challenging on different blogs everyday. It will always be stimulating to read content from other writers and practice a little something from their store. I’d prefer to use some with the content on my blog whether you don’t mind. Natually I’ll give you a link on your web blog. Thanks for sharing.