WCF Data Service from Entity Framework 5 in SharePoint 2013

Question

not sure which forum is best, so im going to throw it in here.
I am working on a proof of concept. I want to create a WCF Data Service within sharepoint 2013. not only do i want to do that, i want to use the Entity Framework 5 to expose the data via OData. Now, I have crawled the internet and seen various examples of
how to create wcf data services and wcf services in sharepoint 2010/2013. and have tried to apply those as needed to create this POC. So.. what I have done so far. 
MonitoringData.cs
[BasicHttpBindingServiceMetadataExchangeEndpoint]
[AspNetCompatibilityRequirements(RequirementsMode = AspNetCompatibilityRequirementsMode.Required)]
[System.Runtime.InteropServices.Guid("0185abf6-e8b8-42e2-9965-6bb644338077")]
public class MonitoringData : DataService<MonitoringServiceEntities>
// This method is called only once to initialize service-wide policies.
public static void InitializeService(DataServiceConfiguration config)
// TODO: set rules to indicate which entity sets and service operations are visible, updatable, etc.
// Examples:
config.SetEntitySetAccessRule("*", EntitySetRights.AllWrite);
config.SetServiceOperationAccessRule("*", ServiceOperationRights.All);
config.DataServiceBehavior.MaxProtocolVersion = DataServiceProtocolVersion.V3;
MonitoringData.svc:
<%@ServiceHost Language="C#" Debug="true"
Service="$SharePoint.Type.0185abf6-e8b8-42e2-9965-6bb644338077.AssemblyQualifiedName$"
Factory="Microsoft.SharePoint.Client.Services.MultipleBaseAddressDataServiceHostFactory, Microsoft.SharePoint.Client.ServerRuntime, Version=15.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c" %>
upon deployment, this error when hitting the https://server/_vti_bin/poc/monitoringdata.svc/$metadata
"The type 'xxxxxxxx', provided as the Service attribute value in the ServiceHost directive, or provided in the configuration element system.serviceModel/serviceHostingEnvironment/serviceActivations could
not be found."
Breaking out the google-fu, i found that adding the dll to the <compilation> section was needed for the web.config. so i did that. and now i just get a blank screen with no errors.
so i crack open fiddler. i see the following 
200 http
tunnel to
server:443 0
401 https
server /_vti_bin/poc/monitoringdata.svc/$metadata
16
401
https server
/_vti_bin/poc/monitoringdata.svc/$metadata
0
404
https server
/_vti_bin/poc/monitoringdata.svc/$metadata
0
best i can see is that im either not authorized, and its returning null (which shouldnt be the case) or something is just busted.
The goal is to use ntml auth and https to connect to this service. any ideas?

Answer 1

One thing I found was that it's never worth the trouble to place the WCF service in a web site running SharePoint, it's better to place it in a dedicated web site, as described in this article:
http://sharepointdragons.com/2011/10/07/parallel-programming-in-sharepoint-2010-the-back-to-the-future-pattern/
It's usually too much work to get the web.config settings right because of the settings it inherits from its parents.
Kind regards,
Margriet Bruggeman
Lois & Clark IT Services
web site: http://www.loisandclark.eu
blog: http://www.sharepointdragons.com
I'll say that it is one solution to move the WCF Service outside of sharepoint. but my "1000 mile" requirements makes this a necessity. 
To broaden the scope of what I am doing, I have a custom SharePoint Service Application. this custom application has a proxy that used a restful interface. Now, with all the methods i will have to write (over 100, x3 for all of the "proxy to a proxy" scenarios)
I wanted to explore the idea of using odata. so i can use the various clients to write their own queries instead of me writing them all and exposing them. especially since its all linq queries to a database underneath. I feel that I am missing some specific
component to make this work, and its surely due to my incomplete knowledge of WCF or EF.