Transition to SP2010: Impact on developer part1

Solution Architects (and developers) need to be aware of a few changes between SharePoint 2007 and SharePoint 2010.
Keep this in mind when upgrading SharePoint 2007 or WSS 3.0 web parts or custom code to SharePoint 2010.


WSS 3.0 to SharePoint Foundation 2010:
Deprecated features (will eventually be removed):

• Stsadm command-line tool: The Stsadm command-line tool will be superseded by Windows PowerShell 2.0.

Features and functionality no longer available in SharePoint Foundation 2010:

• 32-bit operating systems: SharePoint Foundation 2010 requires a 64-bit operating system.
• Side-by-side installation: The ability to perform side-by-side installation of Windows SharePoint Services 3.0 and SharePoint Foundation 2010 on the same server is being removed.
• Gradual upgrade: Support for the gradual upgrade feature is being removed as part of the removal of Side-by-side installation.
• Web discussions:Web discussions enable users to add comments about documents and pages without modifying their actual content. SharePoint Foundation 2010 does not support Web discussions.
• SQL Server 2000 data sources: SQL Server 2000 does not fully support many of the newer data features available in SharePoint Foundation 2010 and have been removed.
• ODBC data sources: Newer and more versatile database connection options have replaced the functionality of ODBC.
• Version 3 themes: The functionality provided in the version 3 themes is not available in the newly designed version 4 themes.The new version architecture is not compatible with the architecture of version 3 themes.
• Web bot software agents: Search crawlers and indexers are examples of Web bots. Developers can no longer use Web bot entry points and users cannot add Web bots to SharePoint Foundation 2010 sites. (Use Web Parts instead of Web bots.)
• E-mail enabled groups and Microsoft SharePoint Directory Management service (DMS): The Microsoft SharePoint Directory Management service (DMS) connects SharePoint sites to an organization's user directory to provide enhanced e-mail features. If a SharePoint farm is using DMS, users cannot enable SharePoint groups to use e-mail.The type of authentication used in DMS is being replaced with claims authentication.)
• Permissions for sub-webs: In SharePoint Foundation 2010, if you want to give different permissions to a sub-web, you must assign a separate permission level to the sub-web. Site collections that are upgraded from Windows SharePoint Services 3.0 and have these unique permission level structures will continue to work. However, the user interface in SharePoint Foundation 2010 does not have a way to edit an inherited permission level at the sub-web scope, so you cannot change them or create new permission level definitions of this type.
• Internationalized domain names: removed.

MOSS 2007 to SharePoint Server 2010:

Deprecated features (will eventually be removed):

• Stsadm command-line tool
• Site Directory feature:This functionality will be replaced by the social features of the User Profile service.
• Scorecard export to Reporting Services.
• Business Data Catalog: Replaced with Business Data Connectivity service.

Features and functionality no longer available in SharePoint Server 2010:

• All features and functionality removed for SharePoint Foundation 2010 applies to SharePoint Server as well as the items listed below.
• Office Web Components: The PivotChart, PivotTable, and Trend Chart report types are no longer available as options in the SharePoint Dashboard Designer.
• Web discussions: Now use the Note Board feature.
• Storage Management page: The Storage Management (storman.aspx) page is now removed from the Central Administration Web site.
• Shared Services Provider (SSP): Service applications replace this functionality.
• Site directory template: replaced by Enterprise Content Management (ECM) solutions.
• News portal template:replaced by Enterprise Content Management (ECM) solutions.
• Collaboration portal template: replaced by Enterprise Content Management (ECM) solutions.

Object Model:
There are also a number of Obsolete types and methods.
They will continue to work in your custom code and solutions, but they will generate compiler warnings, and you should update your code to use the new types.

The following site (http://code.msdn.microsoft.com/sps2010deprecated) contains 3 text files:

SPS2010NewlyDeprecated.txt lists the types and methods that have been made obsolete in Microsoft SharePoint Server 2010 since the release of Microsoft Office SharePoint Server 2007.
SPS2010Deprecated.txt lists all of the types and methods that are obsolete in Microsoft SharePoint Server 2010.
OfficeSharePointServer2007Deprecated.txt lists all of the types and methods that are obsolete in Microsoft Office SharePoint Server 2007.