SharePoint Stack Exchange is a question and answer site for SharePoint enthusiasts. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I am starting to read up on SP development but none of the books I have checked have been able to answer this seemingly simple question.

I am pretty new to the dev side of things and feel like I missed something obvious.

share|improve this question
up vote 6 down vote accepted

A feature is a development package that can be removed and deployed at will from the SharePoint side. Let's say we have a feature in Visual Studios that is a web part. If we deploy this web part as a feature (like most do) in Visual Studios, that web part will be immediately available because it will deploy the feature to sharepoint, and turn on that feature. It also gives the ability to site administrators and farm administrators to turn off (or toggle) the feature. That way the web part will no longer be available.

SharePoint Feature (2007 but still applicable)

share|improve this answer

Features make it easier to deploy managed solutions or site customizations to SharePoint. A feature can be just about anything, but more often than not it seems they are ASP.Net wrapped in a solution and deployed to SharePoint. (IMHO)

Check these out, see if they help:

MSDN overvew

Channel 9 video

Step by step guide in blog

share|improve this answer

Feature is a unit of deployment that generally includes content such as .aspx application pages, list schemas, customizations expressed in CAML

I also highly recommend to read Ted Pattisons book:

Check this Tech-net Article, Creating SharePoint Features
also MSDN, SharePoint Feature
and this link

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.