Work with features

Document directory

• Feature execution
• Feature Element

Features reduces the complexity and difficulty of creating a simple website customization, and is robust when provincial applications are deployed. Features eliminates the hassle of simply changing functions and copying a large number of code blocks. Therefore, features reduces the incompatibility between versions and releases of Web Front-end servers. Features can be easily activated and reversed during deployment, so that the administrator can easily change the template or definition of the site by simply switching feature to provide different interfaces for users. Features provides the following capabilities:

• Manage Custom Code Execution

• Deploy feature to install and reverse install to insert a behavior

• To insert an action within a range of activation or reverse Activation

• Data feature package to be stored within a feature range

• Provides a basic and unified WSS solution release and deployment framework

Feature execution

To execute a feature, you need to create a sub-folder to store the feature definition, this path must be created under \ Program Files \ common files \ microsoft shared \ Web Server Extensions \ 12 \ template \ features. The feature subfolder must contain the feature. xml file, which defines the basic attributes of the feature and list element restrictions. For example, the XML file contains any other supporting files for the element list. Examples,. xsn,. resx,. dll and other files of any type.

Note:

When you right-click in the browser and create a new feature sub-folder, this folder cannot have the permission to inherit. you can remove it like this, right-click the folder and choose Properties> Security> advanced> permissions. Then, delete the permission inheritance. You can also create folders through the command line to achieve the purpose of not inheriting permissions.

After the featurefolder is created, you can install and activate the feature through the stsadm.exe command line, or install and activate the feature through the object model. You can also activate feature on the user interface. Make sure that the element in the feature file is recognizable to the server farm. When activating feature, make sure that the feature has a detailed range.

Feature Element

The feature element is used to define the feature in the feature. xml file and specify the local assembly, attributes supported by the file, or feature. A feature contains a feature. xml file and any number of separate element description files. The Feature Element comes from the ONet. XML schema file of the site in use.

The feature item has been included in a pre-defined huge site definition, which is ready for use by the element in the feature. An element is an atomic component in feature. A feature. xml file uses the top-level <elements> tag to include a file that supports Element Definition. The WSS lide element is usually the same as the discrete node in the ONet. xml or schema. xml file. There are several types of elements, such as custom menu items and event processing.

A feature can provide functions such as "my favorite items", which requires the following elements:

• Whether a custom list, user, or list search item is used as a hidden item

• Call "add to favorites," to add a list item to the search folder.

• A webpart is used to search for hidden objects by real users.

Note:

WSS supports low-ASCII characters without spaces as the names of feature folders and files