Here is a list of SharePoint Designer 2007 features that have been discontinued in SharePoint Designer 2010.
In this article
Working with remote sites and content migration
SharePoint Designer 2010 is designed for users to work on — not to design and publish — SharePoint Foundation 2010 and SharePoint Server 2010 web sites. This is a shift in focus from the predecessor of SharePoint Designer, Microsoft FrontPage, which was designed as a server-agnostic Web site creation and management tool.
The most significant changes in SharePoint Designer 2010 are related to this shift in focus. For example, legacy features for publishing and connecting to remote Web sites and managing the transfer of Web sites and Web content are removed from SharePoint Designer 2010.
- You cannot import a Web site from another server or file location in SharePoint Designer 2010.
- You cannot create, edit, or publish a disk-based Web site, or work with remote Web sites in SharePoint Designer 2010. Elements in the SharePoint Designer user interface that supported working with disk-based Web sites, such as the Use Microsoft ASP.NET Development Server preview option, have been removed.
- You cannot perform server administration tasks such as backup and restore, content migration, or other management tasks that affect and entire Web site in SharePoint Designer 2010. These operations should be performed in Central Administration.
Working with earlier versions of SharePoint
SharePoint Designer 2010 is designed for working with SharePoint Foundation 2010 and SharePoint Server 2010. It cannot be used with earlier versions of SharePoint.
If you need to open a Windows SharePoint Services 2007 or Microsoft Office SharePoint Server 2007 site, you can do so by installing SharePoint Designer 2007. Note that this requires that you are running 32-bit Microsoft Office 2010.
Microsoft Script Editor (MSE)
In Office SharePoint Designer 2007 and previous versions of Microsoft FrontPage, you could use the Microsoft Script Editor (MSE) to add text, edit HTML tags, and edit any Microsoft Visual Basic Scripting Edition (VBScript) code in a data access page. MSE also provided IntelliSense features for script creation and editing. You could also use the Script Editor to view your page as it would appear in a Web browser. Microsoft SharePoint Designer 2010 does not include Microsoft Script Editor.
The Contributor Settings feature has been removed from Microsoft SharePoint Designer 2010.
In Office SharePoint Designer 2007, Contributor Settings was used to set up and turn on Contributor mode, a limited access mode. Users who opened a site for editing in Office SharePoint Designer 2007 had access to different commands or features, depending on which Contributor group they were assigned to and which editing restrictions had been assigned to that Contributor group.
In SharePoint Designer 2010, you can use the new SharePoint Designer Settings page to restrict access to certain features in SharePoint Designer.
The Single Sign-On (SSO) method of authentication has been removed from SharePoint 2010 and replaced by the Secure Store Service. The Secure Store Service is a claims-aware authorization service that includes a secure database for storing credentials that are associated with application IDs. These application IDs can be used to authorize access to external data sources.
In Office FrontPage 2003 and Office SharePoint Designer 2007, you could create Web page layouts by using layout tables and cells.
Powerful cascading style sheets (CSS) layout features have replaced layout tables feature in Microsoft SharePoint Designer 2010. The tools related to creating and modifying layout tables have been removed from the SharePoint 2010 Designer user interface.
If you open a Web page that contains an existing layout table in SharePoint Designer 2010, the layout table functions correctly. However, you cannot use SharePoint Designer 2010 to insert a new layout table.
Themes in SharePoint 2010 have been redesigned to simplify the process of generating themes. Themes created in Windows SharePoint Services 3.0 are not compatible with SharePoint Foundation 2010. If you are upgrading from Windows SharePoint Services 3.0 to SharePoint Foundation 2010, you can use Visual Upgrade to continue to use sites in the old user interface. However, we recommend that you use the new user interface in SharePoint Foundation 2010 to create themes and apply them to your sites.
Views: Reports, Navigation, and Hyperlinks
SharePoint Designer 2010 includes changes to the Reports, Navigation, and Hyperlinks views.
The Navigation view and Navigation task pane have been replaced by the Navigation pane on the left side of the window, which shows the components that make up your site–its lists, libraries, content types, data sources, workflows, and more. To edit one of the components, an Announcements list for example, you open Lists and Libraries, and this takes you to a Gallery page showing all lists and libraries. You can also use the Navigation Bar to see where you are in the site hierarchy, go forward or back, or see recent pages.
The Hyperlinks view is removed from SharePoint Designer 2010. You can use the error-checking features in SharePoint Designer 2010 to check for broken links, unused pages, cascading style sheets usage, and master page usage. The Recalculate Hyperlinks command has also been removed.
SharePoint Designer 2010 changes the way that you access reports and has removed selection reports.
SharePoint Designer 2010 provides a new set of tools to connect to external data, to create external content types, to publish those external content types to the Business Data Catalog on the server, and to auto-generate both an external list and all of the forms required by that external list.
Because of the changes to data management, the following database features from Microsoft FrontPage and Office SharePoint Designer 2007 are not supported in SharePoint Designer 2010:
- Database Interface Wizard
- Database tab of the Site Settings dialog box.
- Database Results Wizard
Note: When you view a Web page or if you use Design view in SharePoint Designer 2010 to open an existing database results page, the Database Results WebBot is rendered as an HTML comment.
The Find A Data Source task pane has been removed.
FrontPage provided a built-in FTP client for connecting to servers without Microsoft FrontPage server extensions. The built-in FTP client enabled users to open sites over FTP and then publish an entire Web site or manage individual files on the remote Web server. Because SharePoint Designer 2010 is designed for working with SharePoint sites, and these servers already have the necessary underlying code installed, an FTP client is not required and is removed.
Customizing pages (also known as “unghosting”) now requires higher permissions than in the previous release: By default, only Site Collection Administrators can customize pages, master pages, and page layouts, or use the All Files view. This means that, in the Navigation pane, most people will not see the nodes for Master Pages, Page Layouts, and All Files. Instead, people will build solutions by creating and storing Web Part pages in the Site Pages library. So it’s easy for you to preserve a consistent branding and layout across your Web application or site collection.
Dynamic Web templates
The functionality in Dynamic Web templates has been replaced in SharePoint Designer 2010 with master pages.
Web package files
SharePoint Designer 2010 does not import Web package files.
A Web package can contain Web pages, templates, Web components, themes, graphics, style sheets, and other elements. Web packages are CAB files (with .fwp file name extensions) that you use to import or export from a Web site.
Here are two alternative ways you can deploy packaged functionality when you are working with a SharePoint Web site:
- You can use a custom site template. Custom site templates are stored as an .stp file in the SharePoint database.
- You can use the SharePoint Foundation 2010 solution framework.
A solution is a deployable, reusable package that contains a set of features, site definitions, and assemblies that apply to sites, and that you can individually enable or disable. You can use solutions to package and deploy custom features, site definitions, templates, Web parts, and assemblies.
The SharePoint Foundation 2010 solution framework lets you bundle all the components for extending SharePoint Foundation 2010 in a solution file. A solution file is a cabinet format file but it has a .wsp extension. You can use the solution file to deploy the contents of a Web Part package. This includes assemblies, class resources, .dwp files, and other package components.