Deploying WCF services on DASP seems to be a bit tricky. Many thanks for this tutorial. I've actually downloaded the zip file with the code and tested it. Then I tried to find the differences between how I work and how this service is set up. I have found two differences. How I work, I create a svc service in Visual Studio 2008, this adds some configuration to the web.config. Then with svcconfigeditor, I usually set under Advanced/Service Behaviours/my new svc service/serviceMetaData, the properties "HttpGetEnabled" and "HttpsGetEnabled" to false. With this option, it is no longer possible to request the wsdl of the webservice, which I find is a very convenient way to secure my webservice. The two differences between the working svc from the tutorial refenced above, and the way I work are: 1) HttpGetEnabled is set to true (in the working svc) 2) Configuration of element "serviceHostingEnvironment" contains a base address (in the working svc) If I create a svc webservice and I configure it according to the two points above, it seems that I can deploy my service without problems to DASP. But, I don't want HttpGetEnabled to be set to true, I want it to be false. And I don't want a base address really. I use a lot, and that is, a lot of svc webservices and this becomes unmanagable. If I add the base adress to the configuration, then the webservice does not work locally anymore (not even when I add a second base address "localhost"). Besides that, I need to change the DNS pointers of my existing domain to get the site live. This means that all base addresses I've set to test my site, I need to set them again to work with my own domain. So the question really is, are there really no alternatives to the (working) config settings presented in the tutorial? My current (or future previous) hosting party has problems, this is why I try DASP. But the svc webservices all seem to work fine. A major difference is that DASP works with setting webapplication on folders, why my former webhosting company setted such a folder to be a virtual directory (and not a web application). Maybe this difference makes installing svc webservices so hard on DASP?
