SharePoint Portal Server 2003 APIs Deprecated in Office SharePoint Server 2007

  • Article

All object model changes in Microsoft Office SharePoint Server 2007 have been made with an emphasis on a high level of backward-compatibility with Microsoft Office SharePoint Portal Server 2003. So even though you may encounter a completely refactored area of the object model, such as Areas, your code should still continue to work. You should be aware, however, that your earlier code, although functional, may not perform in the way you expect in the new object-model hierarchy.

This topic lists the APIs that are deprecated in Office SharePoint Server 2007 either because of the introduction of a new feature or enhancements in an existing feature.

When you upgrade or write new applications that use the deprecated classes or members, use the new classes or members instead.

Note

This list is not complete and is a work in progress.

Deprecated API Comments/Behavior in Office SharePoint Server 2007

All classes in Microsoft.SharePoint.Portal.UserProfiles

Use classes in the Microsoft.Office.Server.UserProfiles namespace instead.

All classes in Microsoft.SharePoint.Portal.Audience

Use classes in the Microsoft.Office.Server.Audience namespace instead.

All classes in Microsoft.SharePoint.Portal.Topology

Use the Windows SharePoint Services 3.0 topology APIs instead.

All classes in Microsoft.SharePoint.Portal.Security

Use the Windows SharePoint Services 3.0 security APIs instead.

Microsoft.SharePoint.Portal.SiteData.Area

  • AutoApprove

  • CoorAutoApprove

  • InheritUrl

  • IsPublicNav

  • System

  • UrlOverride

These members now return the following values:

  • AreaAutoApprove.NoAutoApprove

  • false

  • AreaUrl.UseWebUrl

  • false

  • false

  • empty string

Microsoft.SharePoint.Portal.SiteData.AreaGroup

  • BestBetGroupID

  • BestBetGroupTitle

  • DefaultGroupID

  • DefaultGroupTitle

  • ExpertGroupID

  • ExpertGroupTitle

  • GroupID

These members now return the following values:

  • -1

  • Microsoft Office SharePoint Portal Server 2003 string

  • -1

  • SharePoint Portal Server 2003 string

  • -1

  • SharePoint Portal Server 2003 string

  • 0

Microsoft.SharePoint.Portal.SiteData.AreaListing

  • BestBet

  • Order

These members now return the following values:

  • false

  • -1

All SharePoint Portal Server 2003 backup/restore APIs

Use Windows SharePoint Services 3.0 backup/restore APIs instead.

All 2003 Document Management Server APIs

Use the new Document Management Services APIs. For more information, see Managing Enterprise Document Content.

PortalRight.ManagePeople, PortalRight.ManageAudiences, PortalRight.CreatePersonalSite, PortalRight.ManageSearchIndexing

These are moved to the Microsoft.Office.Server dll where the security mode is not role-based.

All classes in Microsoft.SharePoint.Portal.Search

Use classes in the Microsoft.Office.Server.Search namespaces, found in Microsoft.Office.Server.Search.dll instead.

All classes in Microsoft.SharePoint.Portal.Search.ObjectModel

Use classes in the Microsoft.Office.Server.Search namespaces, found in Microsoft.Office.Server.Search.dll instead.

Portal Site creation APIs

  • PortalSiteCollection.Create()

  • PortalSiteCollection.Delete()

The SharePoint Portal Server 2003 portal creation object model is deprecated in Office SharePoint Server 2007. In Office SharePoint Server 2007, portal sites use the same provisioning process as Windows SharePoint Services sites. Therefore, you must update any scripts that create portals sites to use the Windows SharePoint Services 3.0 site creation APIs. If you require a new vServer (Web application), use the Windows SharePoint Services CreateWebApplication API before creating the site.

Microsoft.SharePoint.Portal.Topology.Server.IsJobServer

This Boolean property is deprecated in Office SharePoint Server 2007 because job server is not a valid role in Office SharePoint Server 2007.