Home/ Questions/Q 6909695
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-27T08:43:18+00:00

I am working on a web service which is going to have both a

  • 0

I am working on a web service which is going to have both a native WPF client as well as a Javascript based web interface.

While I was working on the service and WPF client, the WCF service has been an IIS hosted WCF service project of its own, and has been working fine. Now that I’m starting to work in earnest on the web interface, I am wondering if keeping the WCF service separate is a good choice.

Reading around on the subject, there seem to be lots of options regarding this; for example, I could:

  • Keep the two projects separate
  • Create the asp.net MVC website and add an Ajax-enabled WCF service to the project
  • Create the asp.net MVC website and add a WCF service to the project
  • Create a WCF service library project and have that hosted in the MVC application (not entirely sure about this, but it seems possible)

And I have a feeling there’s probably more.

What do you suggest I should do? My goals are:

  • Accessing the service from the WCF client using a service reference like I have done so far
  • Accessing the service from Javascript on the web interface
  • Accessing the service using port 80 from Javascript and the WCF client (to avoid firewall issues)
  • Having website and service under the same domain
  • Being able to run the thing using shared hosting (Gearhost), without multiple IIS virtual directories/application starting points.
Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    In the end I decided to create three projects: the service interface, a dll holding service and data contracts, the service library itself, which references the interface, and the website, an MVC application which hosts the created service library. The MVC code interfaces with the service as if it was hosted on a different system, using a client proxy (which in this case connects to itself, funnily enough). This should allow me to host the whole thing in a single virtual directory while still providing for not-too-painful decoupling down the line if need be. To keep things tidier, I am creating the service proxy manually in code by referencing the interface dll and NOT using the “add service reference” function.

    • 0