Export (0) Print
Expand All

User Profiles and Social Data: Setting Up Your Development Environment

SharePoint 2010

Last modified: August 22, 2011

Applies to: SharePoint Server 2010

This document summarizes the basic setup tasks required to begin any custom solution that uses the programmability functions provided by the Microsoft.Office.Server.UserProfiles, Microsoft.Office.Server.Audience, Microsoft.Office.Server.ActivityFeed, and Microsoft.Office.Server.SocialData namespaces in Microsoft SharePoint Server 2010.

In SharePoint Server 2010, the Microsoft.Office.Server.UserProfiles, Microsoft.Office.Server.Audience, Microsoft.Office.Server.ActivityFeed, and Microsoft.Office.Server.SocialData namespaces are in a new DLL. Therefore, you must add a reference to Microsoft.Office.Server.UserProfiles in addition to Microsoft.Office.Server and Microsoft.SharePoint. Additionally, if your custom application creates social tags and works with social terms, you will be working with the taxonomy store and will need to add a reference to Microsoft.SharePoint.Taxonomy. A typical set of using declarations will look like this:

using System;
using System.Web.UI;
using System.Web.UI.WebControls;
using System.Web.UI.WebControls.WebParts;
using Microsoft.SharePoint;
using Microsoft.Office.Server;
using Microsoft.Office.Server.UserProfiles;
using Microsoft.Office.Server.SocialData;
using Microsoft.SharePoint.Taxonomy;

Web services are available for equivalent functionality in Microsoft.Office.Server.UserProfiles and Microsoft.Office.Server.SocialData. See [OrganizationProfileService Web service], [SocialDataService Web service], [UserProfileService Web service], and [UserProfileChangeService Web service] for available types and methods in these areas. Web references to these services should use the SocialDataService.asmx, UserProfileService.asmx, UserProfileChangeService.asmx, and OrganizationProfileService.asmx files available in the _vti_bin directory of your site. No equivalent Web service is available for functionality in Microsoft.Office.Server.ActivityFeed, so if you need to make this functionality available as a Web service, you will have to write a custom connector that receives requests and sends responses to remote applications.

Show:
© 2014 Microsoft