Apr 6, 2011 at 3:31 PM
Edited Apr 6, 2011 at 3:33 PM
A quick google search results in many interesting discussions on the subject, some of which may or may not be helpful here.
WCF's requirement to expose bindings and configuration only thru Web.config is a serious limitation in and of itself and if you want to do things the MVC way you should consider building a RESTful controller instead, and forget service references - as some
of those discussions point towards.
I think if this is the only way you can do things, you need to implement your service
as a self-contained application which can be deployed independently of Orchard on the webserver, and then implement the repository pattern in Orchard to communicate with your webservice and expose that data in your controllers and so forth.
Which is why I didn't go any further with WCF; it makes things extremely complicated for what was for me a minimal perceived gain.