Website project and WCF project in the same or different solution: pros and cons
I have a Visual Studio solution that contains a website project plus many supporting projects (domain model, data access, etc.).
I want to expose APIs for the same underlying data via URLs in the same domain, so I developed a WCF / REST project for this (which has dependencies on the same set of domain / data access projects).
Now I'm wondering what are the pros and cons of a WCF service in a separate solution deployed on an IIS virtual path versus simply including a WCF project in the original website solution.
Are there any good reasons why I would like to go one way or another? I am not too experienced with IIS deployments.
a source to share
IF you ever want to host a service yourself instead of hosting it in IIS, or if you ever want to share the service interface as an assembly for some reason, it will probably be easier to have it in a separate assembly.
I would recommend one assembly for the service interfaces (including data contracts, etc.), one for implementing the service, and another (if needed) for the standalone host (such as a Windows NT application or command line application). This is the cleanest separation and there is no real reason not to go this route, IMHO.
Mark
a source to share