Project Server Web Parts
This content is outdated and is no longer being maintained. It is provided as a courtesy for individuals who are still using these technologies. This page may contain URLs that were valid when originally published, but now link to sites or pages that no longer exist.
Microsoft Office Project Server 2007 uses Web Parts in Project Web Access to take advantage of the performance, stability, security, and ease of development of the Microsoft .NET Framework 2.0.
A Project Web Access site is built upon Windows SharePoint Services 3.0 and Project Web Access pages use Windows SharePoint Services 3.0 Web Parts. You can develop custom Web Parts for Project Web Access using the Windows SharePoint Services 3.0 object model or using Microsoft ASP.NET 2.0.
Office Project Server 2007 includes many Web Parts such as Project Center and Resource Center that are installed on the Windows SharePoint Services server for a Project Web Access site. You can install Web Parts from Microsoft or other software vendors or create your own Web Parts.
The Project Server Web Parts and other general Web Parts are available in Web Part galleries. Each instance of a specific Web Part is based on the same Web Part assembly, but can be similar or different in appearance and behavior. A Web Part assembly can include code for more than one Web Part. You can add Project Server Web Parts and custom Web Parts that use the Project Server Interface (PSI) to any Web Part Page that is in the same server farm as Project Server.
For more information about Web Parts, Creating Web Parts in Windows SharePoint Services in the Windows SharePoint Services 3.0 SDK explains when to use the ASP.NET WebPart base class and how to add an ASP.NET 2.0 Web Part to a Windows SharePoint Services site. Working with ASP.NET 2.0 Web Parts and Windows SharePoint Services 3.0 shows how to build Web Parts that work in both standard ASP.NET 2.0 Web sites and Windows SharePoint Services 3.0.
Web Part Concepts shows how to create and use a simple Web Part in Project Web Access, describes some typical scenarios for using custom Web Parts, and shows how to configure the default Project Server Web Parts.
Custom Web Parts summarizes the differences between Windows SharePoint Services Web Parts and ASP.NET 2.0 Web Parts, and explains when to use each type of Web Part. This topic also includes a walkthrough of creating and using a custom Project Server Web Part .NET assembly.
We recommend that you use the Windows SharePoint Services 3.0 SDK to build custom Web Parts, if the Web Part is designed to work within the same server farm as Project Server. The Windows SharePoint Services Developer Center (http://msdn.microsoft.com/sharepoint/) has links to the SharePoint SDK, downloads, and other developer resources. The Web Parts in the Microsoft.Office.Project.Server.PWA.dll assembly are not documented or supported for third-party development. While it is possible to derive other Web Parts from base classes such as Microsoft.Office.Project.Server.PWA.WebParts.PWAPart, we do not recommend or support that. It is not possible to derive other Web Parts from the sealed Project Web Access Web Parts, such as TaskPart.