Question

Today I am digging into WCF Data Service and I have a question regarding this. Can I create WCF Data service as Library and just only create WCF data Service in our existing web app and take reference that library using Factory property so service will deploy with existing web application.

As I know We can create WCF Service Library and only need to take reference that library in Web application like :

1. Create a WCF Library and implement service contract

2. Create a Web application and add new item as Wcf service file then take reference WCF library

   <%@ ServiceHost Service=”MyServiceLibrary.MyService” Factory=”System.ServiceModel.Activation.WebServiceHostFactory” />

Instead of a service library, I want to create OData service library.

Thanks

Answer 1

Yes, you can host a WCF Data Service in your own assembly – with a few little tricks. I researched this a while ago and came up with these steps / instructions.

Here’s how:

• put your data model (EF Data Model) into its own assembly, let’s call it DataModel

• create a new class library project (call it MyDataServiceHost)

• add a few references:

  • your DataModel assembly with the data layer
  • System.ServiceModel
  • System.ServiceModel.Web
  • System.Data.Services.Client
  • System.Data.Services – you cannot pick this from the usual Add Reference dialog under the .NET category – you need to browse for the assembly file. Find the directory C:\Program Files\Reference Assemblies\Microsoft\Framework\.NETFramework\v4.0 (or C:\Program Files (x86)\... on a 64-bit machine) and pick the System.Data.Services.dll inside it

• add a new class to that class library and call it e.g. YourDataService.cs – it will look something like this:

  using System.Data.Services;
  using System.Data.Services.Common;
  
  using DataModel;
  
  namespace MyDataServiceHost
  {
      public class YourDataService : DataService<YourModelEntities>
      {
          // 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.AllRead);
              config.DataServiceBehavior.MaxProtocolVersion = DataServiceProtocolVersion.V2;
          }
      }
  }
  

  You can name the class anything you like, and it has to derive from DataService<T> where T is the name of your data model; if you’re using Entity Framework, it’s the name of your object context class – typically something like (database)Entities or whatever you picked when you created the EDM

• add another class to your new project, call it MyDataServiceHost.cs and it will look something like this:

  using System;
  using System.Data.Services;
  
  using DataModel;
  
  namespace MyDataServiceHost
  {
      public class MyDataServiceHost
      {
          public static void LaunchDataService(string baseAddress)
          {
              Uri[] baseAddresses = new Uri[1];
              baseAddresses[0] = new Uri(baseAddress);
  
              using(DataServiceHost host = new DataServiceHost(typeof(YourDataService), baseAddresses))
              {
                  host.Open();
                  Console.WriteLine("DataService up and running.....");
  
                  Console.ReadLine();
                  host.Close();
              }
          }
      }
  }
  

  It instantiates a DataServiceHost, which is derived from WebServiceHost (which in turn is derived from ServiceHost) and it will spin up the WCF Data Service runtime for you.

• now you can start up your WCF Data Service from any app using:

  MyDataServiceHost.LaunchDataService("http://localhost:4444/YourService");
  

• last thing to remember: the app that you use to launch the WCF Data Service must have the connection string (the EDM connection string, if you’re using Entity Framework) in its app.config (or web.config) in order for this to work!