Comments on: WCF and SharePoint: context != context

By: MossBuddy

MossBuddy — Wed, 09 Nov 2011 12:56:56 +0000

Thanks John Liu:- have u tried the stuff with cliams enabled web-apps…they dont pass the end user cliam easily you have to follow what Steve Peschka from microsoft has said in his blog….

By: John Liu

John Liu — Wed, 09 Nov 2011 06:19:08 +0000

WCF is very simple in SP2010 now, start with CKS for VS.NET 2010, and use the project item template for WCF Service.

The magic in SP2010 are the three SharePoint service factories that does a lot of the plumbing that we didn't have in 2007.

By: Waldek Mastykarz

Waldek Mastykarz — Wed, 09 Nov 2011 06:16:09 +0000

@MossBuddy: I have to admit that I haven't stumbled upon such scenario yet. Have you tried asking on MSDN SharePoint Forums?

By: MossBuddy

MossBuddy — Tue, 08 Nov 2011 22:59:31 +0000

Hello Waldek, hey have you tried creating the WCF (simple Hello World) in SP 2010 and host it in the ISAPI folder of the same web-application (SP 2010). Make sure that Sharepoint web-app is using claims authentication. Now run the WCF from the SharePoint context and check what is the identity the WCF code is running under, it turns out it is app-pool identity of the web-app and not the end user identity/claim.. I think this is not correct as the WCF code shld run under the end user identity and not app-pool. Have you experience it? Any thoughts around it?… Not sure how the out of the box WCF services in SP 2010 work seamlessly in claims authentication…

By: Publicação de Serviços WCF no SharePoint « SharePointersBR

Publicação de Serviços WCF no SharePoint « SharePointersBR — Thu, 21 Jul 2011 14:41:59 +0000

[...] http://blog.mastykarz.nl/wcf-sharepoint-context/ [...]

By: Publicação de Serviços WCF no SharePoint « Fabian André Gehrke

Sun, 17 Jul 2011 14:20:34 +0000

[...] http://blog.mastykarz.nl/wcf-sharepoint-context/ [...]

By: Sheetal

Sheetal — Wed, 02 Jun 2010 05:46:46 +0000

Hi,

I had to register the HttpHandler in the tag in web.config and it started working.
I am not able to figureout how the SharePoint services been configured.

By: Sheetal

Sheetal — Wed, 02 Jun 2010 05:46:06 +0000

Hi,

I had to register the HttpHandler in the tag in web.config and it started working.
I am not able to figureout how the SharePoint services been configured.

By: Waldek Mastykarz

Waldek Mastykarz — Wed, 26 May 2010 10:38:27 +0000

@Sheetal: have you tried deploying your custom SVC alongside SharePoint services? Additionally have you looked how SharePoint services have been configured?

By: Sheetal

Sheetal — Tue, 25 May 2010 09:46:13 +0000

Hi Waldek, Great Post!!

I am currently migrating a site from MOSS 2007 to SharePoint 2010 which has custom WCF services. When deploying .wsp file in MOSS 2007 environment it gets deployed at Features directory under 12 hive and works well. Where as when I try to deploy the .wsp file in SharePoint 2010 the WCF doesn't work.

The service is working correctly when the .svc is stored directly in the virtual directory of the iis… the problems appear when I deploy the .svc file to the 14. Any idea?

I didn't change anything, only put the .svc outside SharePoint to test it, and it works. When I call the .svc file inside SP I get this error:
Description: HTTP 404. The resource you are looking for (or one of its dependencies) could have been removed, had its name changed, or is temporarily unavailable.

Apart from that when I deploy the .wsp file (its a custom site template ) and create a site, the default webservices also doesn't work (_vti_bin\Lists.asmx , _vti_bin\Listsdata.asmx..etc)… I have verified for the webservices by creating a normal team site and browsed for _vti_bin webservices which works fine.

Is that the way WCF behaves differently in SP2010 environment?