Web Parts in SharePoint Foundation
Web Parts are server-side controls that run inside the context of site pages in Microsoft SharePoint Foundation. There are many Web Parts available by default, and you can also build your own custom Web Parts in SharePoint Foundation. They are editable and configurable by users. Web Parts let users add functionality to a site page by simply putting them on the page. SharePoint Foundation includes many default Web Parts. In addition, you can build your own Web Parts.
Types of Web Parts
There are two types of Web Parts in SharePoint Foundation.
<!--[if !supportLists]-->· <!--[endif]-->ASP.NET Web Parts — These Web Parts are built on top of the ASP.NET Web Part infrastructure.These Web Parts makes them highly reusable.
<!--[if !supportLists]-->· <!--[endif]-->SharePoint-based Web Parts — These Web Parts can only be used in SharePoint websites.
Custom Web Parts provide you with a method to create user interface elements that support both customization and personalisation.
The term customization implies that changes are seen by all site members. Individual users can further personalize Web Parts page by adding, reconfiguring, and removing Web Parts. A site owner or a site member who has the appropriate permissions can customize Web Parts page by using a browser or by using Microsoft SharePoint Designer to add, reconfigure, or remove a Web Part.
.
<!--[if !supportLists]-->· <!--[endif]-->Create custom properties that you can display and modify in the user interface.
<!--[if !supportLists]-->· <!--[endif]-->Improve performance and scalability. A compiled custom Web Part runs faster than a script.
<!--[if !supportLists]-->· <!--[endif]-->Implement proprietary code without disclosing the source code.
<!--[if !supportLists]-->· <!--[endif]-->Secure and control access to content within the Web Part. Built-in Web Parts enable any users who have the appropriate permissions to change content and alter Web Part functionality. With a custom Web Part, you can determine the content or properties to display to users, regardless of their permissions.
<!--[if !supportLists]-->· <!--[endif]-->Make your Web Part connectable, allowing Web Parts to provide or access data from other connectable Web Parts.
<!--[if !supportLists]-->· <!--[endif]-->Interact with object models that are exposed in SharePoint Foundation. For example, you can create a custom Web Part to save documents to a SharePoint Foundation document library.
<!--[if !supportLists]-->· <!--[endif]-->Control the Web Part cache by using built-in cache tools. For example, you can use these tools to specify when to read, write, or invalidate the Web Part cache.
<!--[if !supportLists]-->· <!--[endif]-->Benefit from a rich development environment with debugging features that are provided by tools such as Microsoft Visual Studio 2010.
<!--[if !supportLists]-->· <!--[endif]-->Create a base class for other Web Parts to extend. For example, to create a collection of Web Parts that have similar features and functionality, create a custom base class from which multiple Web Parts can inherit. This reduces the overall cost of developing and testing subsequent Web Parts.
<!--[if !supportLists]-->· <!--[endif]-->Control Web Part implementation. For example, you can write a custom server-side Web Part that connects to a back-end database, or you can create a Web Part that is compatible with a broader range of Web browsers.
In SharePoint Foundation 2010, Web Parts are organized in the following categories:
<!--[if !supportLists]-->· <!--[endif]-->Lists and Libraries
<!--[if !supportLists]-->· <!--[endif]-->Content Rollup
<!--[if !supportLists]-->· <!--[endif]-->Documents
<!--[if !supportLists]-->· <!--[endif]-->Forms
<!--[if !supportLists]-->· <!--[endif]-->Media and Content
<!--[if !supportLists]-->· <!--[endif]-->People
Certain Web Parts can only be used with particular types of lists, libraries, or content or pages. For example, the Task Details, Task Decision Makers can only be used in a Task list.
0 comments:
Post a Comment