Summary of the problem: The very same windows service program hosting WCF services:
1) Works flawlessly on our Windows Server 2008 server
2) Used to work, but now doesn't work on my laptop
3) Never worked on my new desktop.
I have a windows service that runs WCF WebGet services. This service does NOT use IIS. The service works on our Windows Server 2008 (32 bit) perfectly well. It also used to work just as well on my development laptop, Win7 (32bit).
Then about nine months ago I bought a Win8 64bit workstation as a fall-back development computer. The very same service on our server mentioned above installs correctly using installutil and and starts up fine. However, when I submit a GET REQUEST to the service I get the following response:
"The remote server returned an unexpected response: (405) Method Not Allowed."
To compound things, not having used the services on my laptop (Win7 32bit) for several months, I recently needed to do some development work and where the services used to work on this computer, I now get the same response message as above. I haven't wittingly changed anything on the laptop and the services program was the same as before. Development work is now very cumbersome as I have to copy the new build to the server and test it there.
I originally thought this was an issue with 64bit or Win8, but now the problem has spread to my Win7 32 bit development computer that idea seems less likely. I am beginning to think that this is some kb that our dear friends at Microsoft have pushed out which I religiously install.
I have read every article I can find but they all hark on about iis. Now I know this looks like an iis response and probably is, but what I want to know is (1) why has my laptop started handling the service requests differently and (2) what can I do to get back to where I was? The answer will no doubt help me work out why the service never worked on my fall-back computer also. It is like something is forcing all my get requests into iis, which I definitely don't want to happen.
The app.config file contains a service trace block, which has reliably worked (when not getting this 405 response). Where I have the 405 response, no entries are made in the service trace log.
I would be immensely grateful for the right help. I should stress that my solution is a windows Service, not a web application and my solution has an app.config file NOT a web.config (as would a web application).
Many thanks,
Malcolm