SharePoint Stack Exchange is a question and answer site for SharePoint enthusiasts. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

We are developing an extranet web application (ASP.NET MVC2, I know :( ) using SharePoint 2010 lists. Internal staff users will access the same (and more) data using SharePoint interface. There is a common functionality which is based on set of algorithms. We would prefer to develop it once & share between the both interfaces.

Since extranet app is hosted on separate machine, it will use "Client Object Model" (.net) and SharePoint web parts will use "Server Object model". So now how implement this common function?

Is it possible to extend existing web services in SharePoint & Client Object Model offers wrapper for it? Or can we replicate what COM <-> REST has done? Is "Service Application" one of the options?

We preferably do not want to publish it as a web service from SharePoint (aspx) and consume it in extranet app unless there is no option. I guess this would be separate DLL which will use SP-classes & web part will use it for SharePoint & aspx will use it for publishing for extranet.

There are other issues of impersonation from extranet which on FBA.

Has anyone implemented this sort of thing successfully? Any suggestions/pointers to case-studies are welcome.

share|improve this question

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Browse other questions tagged or ask your own question.