OData 101: Bin deploying WCF Data Services

re: OData 101: Bin deploying WCF Data Services

Ross — Tue, 12 Mar 2013 13:20:57 GMT

It might be worth clarifying something that tripped me, which in hindsight is obvious :-) I was upgrading V4.0.0.0

In my svc markup I had to remove the assembly version, change the publickeytoken to the latest, and update the assembly name to Microsoft.Data.Services.

The last thing tripped me because the namespace remains system.data.services in code.

re: OData 101: Bin deploying WCF Data Services

DevDelimited — Mon, 24 Sep 2012 20:58:48 GMT

Disregard... As it turns out, because I have my EF model in a separate project from my WCF svc, I had to install the OData packages in both places. Which is strange, considering that it ran fine in debug with the packages installed only in the WCF project.

On to better things!

re: OData 101: Bin deploying WCF Data Services

DevDelimited — Mon, 24 Sep 2012 20:34:30 GMT

Using nuget, I have just installed the 5.1.0-rc2 packages. I am performing a standard install from an msi and getting the exact error you mention above - 'Could not load file or assembly 'Microsoft.Data.Services.Client, Version=5.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35'

Although I do have a line in my .svc file that reads 'Factory="System.Data.Services.DataServiceHostFactory, System.Data.Services, Version=5.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089"', unfortunately, your resolutions seem to have no affect. Any ideas? Thanks!

re: OData 101: Bin deploying WCF Data Services

alduar — Thu, 30 Aug 2012 07:14:34 GMT

WCF Supoort Oracle

re: OData 101: Bin deploying WCF Data Services

Harry Pfleger — Thu, 30 Aug 2012 04:58:28 GMT

for me, the "pop up" with a good explanation would be sufficient...

why not start from the beginning with the missing version info, like [... Microsoft.Data.Services, Culture=neutral, ...]