16.01.2013 Views

Microsoft Sharepoint Products and Technologies Resource Kit eBook

Microsoft Sharepoint Products and Technologies Resource Kit eBook

Microsoft Sharepoint Products and Technologies Resource Kit eBook

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Other Namespaces<br />

Chapter 34: The SharePoint Portal Server Object Model 949<br />

Table 34-1 Description of Classes in the <strong>Microsoft</strong>.SharePoint.Portal.WebControls<br />

Namespace (continued)<br />

Class Name Description<br />

SearchResults This class implements the SharePoint Portal Server Search<br />

Results Web Part. If you want to develop a more advanced<br />

search results part, this class would be the starting point.<br />

TextEditor This class implements the rich text editor control used<br />

throughout SharePoint sites.<br />

The SharePoint Portal Server object model provides several other namespaces.<br />

These namespaces are much less frequently used than the previously discussed<br />

namespaces. A short discussion of these namespaces will be provided in this section.<br />

For more information on these Namespaces, please refer to the “Reference” section<br />

of the SharePoint <strong>Products</strong> <strong>and</strong> <strong>Technologies</strong> SDK.<br />

■ <strong>Microsoft</strong>.SharePoint.Portal.Admin.Search. This namespace provides functions<br />

for interacting with the search catalogs. You can manage the catalogs by<br />

adding or removing content sources, forcing propagation of the catalogs, <strong>and</strong><br />

forcing a type of crawl (Full, Incremental, <strong>and</strong> so on) on a specific search catalog.<br />

This namespace, however, does not let you work with individual content sources,<br />

only full search catalogs, so you cannot crawl a particular content source directly<br />

using the functions, only a particular catalog, such as Portal_Content.<br />

■ <strong>Microsoft</strong>.SharePoint.Portal.Search. The <strong>Microsoft</strong>.SharePoint.Portal.Search<br />

namespace provides only one single class—QueryProvider. With this class, you<br />

can call the search service. Although this class does provide the search ability, it<br />

is better to use the Search Web service. The Search Web service is more robust<br />

<strong>and</strong> easier to use, plus the code that calls the QueryProvider class can only be<br />

run on the local server running SharePoint Portal Server.<br />

■ <strong>Microsoft</strong>.SharePoint.Portal.Search.ObjectModel. This namespace provides<br />

classes <strong>and</strong> functions for manipulating search scopes. With the namespace,<br />

you can add, remove, move, update, <strong>and</strong> list the search scopes on a particular<br />

portal site.<br />

■ <strong>Microsoft</strong>.SharePoint.Portal.Search.WebQueryService. This namespace<br />

implements the Search Web service, the SPSQueryService class. Using the Search<br />

Web service explicitly instead of going through this class is generally easier <strong>and</strong><br />

allows your code to be run from remote machines.<br />

■ <strong>Microsoft</strong>.SharePoint.Portal.SingleSignOn. This namespace contains<br />

classes <strong>and</strong> functions required for accessing the Single Sign-On service provided<br />

with SharePoint Portal Server. You can add different applications, set up<br />

the credentials systems, <strong>and</strong> request credentials from this namespace.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!