views:

58

answers:

0

Maybe I am not understanding this so hopefully someone can explain this to me.

I am writing a WCF REST service (lets call it RestProj). RestProj has a dependency to the RestProj.DataAccess dll which houses all of the data access layer and to the WCFRestContrib dll.

I have another project that contains all of the Rest parameters (datacontracts like REST.Response.NetUser class which contains all of the parameters in the xml payload for a new user). I was planning on just giving that to the user until I discovered the WebChannelFactory feature.

From what I am understanding, for a client to use the WebChannelFactory (which is what I want to do), I need to supply the RestProj.dll so the user can obtain access to the REST interface IRestProj. Is that correct? So the client needs my RestProj.dll AND any dependency that it might have as well (ie RestProj.DataAccess)???

Should I make a separate project that contains the REST interface (not the .svc) and the DataContract classes? But that would cause a problem because the REST interface has special attributes from the WcfRestContrib. And what happens with the web.config?

How should a normal Rest svc solution be structured? I am totally lost here. Please help. Thanks!