• Browse
  • Pages
  • Blog
  • Labels
  • Attachments
  • Bookmarks
  • Mail
  • Advanced

  • People Directory
• Log In
• Sign Up

1. Dashboard
2. SharePoint 2007 Development Wiki
3. Welcome
4. Features

• Log In
• Sign Up

Features

• Page restrictions apply
• Added by Rich Finn, last edited by Jeremy Thake on Apr 05, 2009  (view change)

Comment:

Table of Contents Recently Updated masini bogdan Solution package development tool comparisons updated yesterday at 1:20 PM (view change) Jeremy Thake OWSAPI updated Mar 09 (view change) ana OWSAPI updated Mar 08 (view change) Jeremy Thake SharePoint Development Tools commented Mar 04 Adrian Jackson OWSAPI updated Mar 04 (view change) Forms Builder Developing a InfoPath Solution using a Solution Package commented Mar 03 Jeremy Thake Developing a InfoPath Solution using a Solution Package commented Mar 01 Kostadin Markov Developing a InfoPath Solution using a Solution Package commented Mar 01 Jeremy Thake Developing a InfoPath Solution using a Solution Package commented Mar 01 Kostadin Markov Developing a InfoPath Solution using a Solution Package commented Mar 01 Jeremy Thake SharePoint Implementation Approach Comparison Chart updated Feb 19 (view change) Brenda Quart SharePoint Implementation Approach Comparison Chart updated Feb 18 (view change) Jeremy Thake SharePoint Lists updated Feb 17 (view change) Thaddeus Miller SharePoint Lists updated Feb 17 (view change) Jeremy Thake TimeZones updated Feb 09 (view change) More

Features are encapsulated peices of SharePoint functionality which extends the core product.  The Microsoft development team itself used this platform to develop most of the functionality within SharePoint.  For instance, all of the list templates (document library, wiki page library, task list, etc.), site content types, site columns, web parts, etc. etc. were created just the same as how developers create and deploy features today.  The reason for deploying functionality in this manner allows administrators the ability to activate and deactivate specific groups of functionaity at different scopes through the SharePoint environment.  Structure Every feature includes at least one XML file which is required to be named 'feature.xml'.  Inside of this file contains a Feature Element defining the GUID, title, description, etc. and configuration for the feature.  Optionally, a feature.xml file may contain one or more element manifest files defining Element Types (or, what the feature will actually do). Features are contained in the SharePoint file structure at %ProgramFiles%\Common Files\microsoft shared\Web Server Extensions\12\TEMPLATE\FEATURES How to create a simple feature How to build the assembly reference used in Feature files and SafeControls entries with class, assembly name and public key token   Features can be created by developers Features installed with the SharePoint product As a best practice, features should be deployed using a Windows SharePoint Services Solution Package (WSP) Labels parameters Labels features features Delete Enter labels to add to this page:   Looking for a label? Just start typing. Children (3)   Hide Children  |  View in Hierarchy Creating Features Features installed with SharePoint How to build the assembly reference used in Feature files and SafeControls entries with class, assembly name and public key token

This work is licensed under a Creative Commons Attribution-Share Alike 3.0 Unported License.