Custom 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.
The Microsoft Office Project Server 2007 Web Parts are built with the Project Server Interface (PSI) and use the Microsoft.SharePoint namespace in the Micrsoft.SharePoint.dll assembly that is installed with Windows SharePoint Services 3.0. The Project Server Web Parts have additional properties and functionality that are defined in Microsoft .NET Framework assemblies.
For example, if you export the Project Center .dwp file, you can see that the Project Center Web Part is defined in the Microsoft.Office.Project.Server.PWA.dll assembly. By comparison, the six Project Server Web Parts in Microsoft Office Project Server 2003 are all based on the Content Editor Web Part in the Microsoft.SharePoint.dll assembly for Windows SharePoint Services 2.0. Custom Project Server 2003 Web Parts are designed to use page views of Project Web Access with URL options to hide parts of the standard page.
While you can use the generic Content Editor or Page Viewer Web Parts with Project Web Access URLs, there is no need to do so because you can directly use the Project Server 2007 Web Parts. If one of the standard Project Server Web Parts does not meet your needs, you can develop a custom Web Part using Microsoft Visual Studio 2005.
Developing Custom Web Parts summarizes the differences between the Microsoft ASP.NET 2.0 and Windows SharePoint Services 3.0 custom Web Parts.
Walkthrough: Creating a Custom Project Server Web Part shows how to develop and use a .NET Framework assembly for a custom Web Part that dynamically reads data from a Project Server Web Part on the same page.