The Webs.RevertCss method reverts style sheet customization of a file to the default style sheet.
These two methods are stored in Webs.asmx.cs and are defined in Webswsdl.asps.
The methods are outdated and are no longer needed
Some Search features deprecated from Foundation 2010
The search capabilities of SharePoint Foundation 2013 have changed, and are now based on the same search implementation as SharePoint Server. This provides many improvements, but also means that the search configuration is very different.
and in Server 2010.
SharePoint 2013 uses the web-based interface to show the current status of the topology. You change the topology by using Windows PowerShell. SharePoint Server 2010 also included a web-based option for changing the topology
The thesaurus replacement mode is deprecated in SharePoint 2013.
Search Query web service
In SharePoint Server 2010, the Search Query web service exposes the SharePoint Enterprise Search capabilities to client applications. This enables you to access search results from client and web applications outside the context of a SharePoint site.
Search RSS and search from Windows
The search RSS feature is deprecated in SharePoint 2013. The functionality for performing enterprise searches from Windows 7 depends on search RSS and this element has also been deprecated in SharePoint 2013. The RSS link no longer appears on the results page. This link is replaced by the Search Alerts link.
Custom word breaker dictionaries
Configuration of stemming in the registry
The configuration of stemming in the registry is no longer supported in SharePoint 2013. Modifying stemming entries in the registry has no effect during search. In SharePoint Server 2010, you can turn stemming on or off, or you can replace it with a third-party stemmer by changing the registry. In SharePoint 2013, you cannot use a third-party stemmer.
SharePoint Search SQL syntax
In SharePoint Server 2010, you could construct complex search queries by using SQL syntax.
SharePoint Server Search in Office 2010 supported shallow search refiners. FAST Search Server 2010 for SharePoint supports shallow refiners and deep refiners. InSharePoint 2013, only deep search refiners are supported.
FAST Search Server 2010 for SharePoint deprecated features
FAST Search database connector
The FAST Search database connector is not supported in SharePoint 2013.
FAST Search Lotus Notes connector
The FAST Search Lotus Notes connector is not supported in SharePoint 2013.
FAST Search web crawler
The FAST Search web crawler is not supported in SharePoint 2013.
The SharePoint 2013 crawler provides similar functionality to the FAST Search web crawler.
FAST Query Language (FQL) deprecated featuresThe FQL features are aligned with the features of the SharePoint Keyword Query Language (KQL) syntax
URL Query syntax
In FAST Search Server 2010 for SharePoint, the URL-related managed properties (such as site, or path) are tokenized as a text string, and you can query any subpart of the URL. This includes
PHRASEand proximity queries on URL properties. Special characters such as “
_” and “
-”are handled as word delimiters.
In SharePoint 2013, the entire URL is tokenized as one word. This includes special characters such as “
_” and “
-”. You can query these managed properties by:
- Searching for the full string for the site or path.
- Searching for the leading part of the site or path.
the protocol part (http, https), and omitting the leading part of the
domain address in the query expression, for the site managed property.
Specific search scope filtersIn SharePoint 2013, search scopes are automatically converted to result sources.
Anti-phrasingThe search anti-phrasing feature in FAST Search Server 2010 for SharePoint is not supported in SharePoint 2013.
Offensive content filtering
The filtering of offensive content in search is deprecated in SharePoint 2013.
Substring searchThe substring search feature was removed in SharePoint 2013.
Person names and location extractionsIn SharePoint 2013, you cannot extract person names and locations from documents by using predefined extractors.
Number of custom entity extractors
In SharePoint 2013, the number of custom entity extractors that you can define is limited to 12.
Supported document formatsSharePoint 2013 no longer supports rarely used and older document formats that are supported in FAST Search Server 2010 for SharePoint by enabling the Advanced Filter Pack. Both the ULS logs and the crawl log indicate the items that were not crawled.
In SharePoint 2013, the set of supported formats that are enabled by default is extended, and the quality of document parsing for these formats has improved.
Content processing extensibilityThe FAST Search Server 2010 for SharePoint content processing extensibility feature has changed in SharePoint 2013. Content processing prepares an item from a content source for indexing and searching. The FAST Search Server 2010 for SharePoint content processing extensibility feature uses a sandbox where your custom code runs.
Custom XML item processingFAST Search Server 2010 for SharePoint includes a custom XML item processing feature as part of the content processing pipeline. Custom XML item processing is not supported in SharePoint 2013.
Adding a test item to the index
DocPush is a test and diagnostic command-line tool that submits test documents to the FAST Search Server 2010 for SharePoint index. A similar command-line tool is not available in SharePoint 2013