Hi Neha,

Is there a reason why Web API has to be separate from the Episerver site? Have you thought about raising the Web API endpoints within the Episerver CMS Project and adding your DDS code from there? That way you get all of the Episerver configuration for free.

Hey thanks for responding!

We are using WebAPI so that the services can be exposed publically and be used by many other applications. Due to this reason, we are maintaining the solution seperate so that deployment and maintainance can be handled independent of the epi site.

Help me know considering this, do we have the solution for implementing DDS here? 

Hi Neha,

Thanks for the explanation. Ultimately, the DynamicDataStoreFactory Instance is initialized through Episerver's InitializationModule. So, if you want to use DDS outside of the CMS framework, you will need to somehow "mimick" the initialization steps automated by Episerver in addition to adding in the necessary configuration in the web/app.config. Here's a blog and forum post that might be of help. However, as you can see, this task can be daunting and could be a maintenance nightmare when upgrading.

One possible workaround is exposing Web API endpoints inside of Episerver that contain all DDS CRUD operations, and then exposing another set of Web API endpoints outside of Epi to contain all necessary business logic (or, of course, contain both CRUD operations/business logic in the endpoints inside of Episerver). Hope this helps!

-RJ