Extending Microsoft Office Sharepoint Server 2007
Extending Microsoft Office Sharepoint Server
2007
This is an overview of feature.xml attributes.
Feature.xml Attributes
Feature attribute | Description |
Id |
|
Title |
|
Description | (Optional) Describes what the Feature does |
Version | Specifies the version of the feature |
Scope | Specifies where the Feature will be deployed and made available -- that is, server farm, Web application, site collection, or Web (site). |
Hidden | Determines whether the Feature will be visible in the Feature administrative user interface. This option toggles between False and True. False is the default. Set this option to True to hide the Feature from administrative user interface. |
AlwaysForceInstall | (Optional) If True, any updates to the Feature are installed within the given scope without manual intervention during updating. Removes the need to add the - force parameter to the stsadm.exe command line when redeploying a Feature. |
DefaultResourceFile | (Optional) The resource file the Feature uses for additional configuration details |
ImageUrl | (Optional) The URL to an image you want to have associated with the Feature in the Feature administrative user interface. |
ReceiverAssembly | (Optional) The strong name of the assembly that handles events for the Feature. (*) |
ReceiverClass | (Optional) The fully qualified, case-sensitive name of the class that handles events for the Feature. |
ActivationDependencies | (Optional) The Feature IDs of any dependent Features -- that is, Features that depend on the Feature being activated before they can be activated. |
ElementManifests | The relative path to associated element files for the Feature. This can include more than one element file. |
(*) The ReceiverAssembly attribute in the Feature.xml file
should not be confused with the Receiver element in the supporting element
files. The ReceiverAssembly attribute names the assembly from
which to load Feature events-- that is, different events specified throughout
a Feature life cycle, such as when a Feature is activated or deactivated,
using special Feature classes through the Sharepoint object model. The
Receiver element in the element files associated with the Feature receives the
assembly for a specific event handle assembly.
0 Comments:
Post a Comment
<< Home