Self-hosting WCF service in a Windows Service
Posted on 2012-03-09
I'm new to WCF so don't be to hard on me. I've tried almost all the demos we can find on the net to self-host a WCF Service inside a Windows Service with no success. I've created that simple WCF service that works perfectly when self-hosted in a Windows Console Application. I can connect from the host PC and any remote PC. But when I try to host the same WCF service in a Windows Service host application, I always get these crazy error messages on the client side saying stuff about SSPI or that the service wasn't able to respond in a reasonable time...
What's the problem ? Why is it working perfectly when self-hosted in a Windows Console Application, but not working at all when self-hosted in a Windows Service host application (even when trying from the host PC) ? And what is funny about this, is that when I type in the URL to see if I can reach the wsdl file in my web browser, I do get it and also when I add the service (using the mex url) in a WCFtestClient.exe client (VS2010), I do see all the endpoints with there respective "operationContracts".
This drives me crazy and can't find a way to get out of this maze. I saw some folks out there having almost the same problem as me, but their problem was related to Windows Firewall being up and running on both sides. It's not my case. Windows Firewall is down.