Ok, this console app that I wrote has an endpoint that listens on a TCP port. A web application sends requests to it. Both of these have been running successfully in production for the last 6 months. Anyway, I made a minor change to the code in the console app for an exception that I get from time to time, and now when I test it the web app can no longer connect (Communication Object is in a Faulted State). The code change is insignificant. This has to be something simple that I forgot to generate for the web application to be able to connect to the Console app. Any ideas?
-
-
The problem seems directly linked to the change that you made.
Try removing the change and running the app again...does it work?
If so, please post the code that you've changed and explain what's going on. -
Thanks for your response, Frinny. I'm absolutely certain the the code change is not the problem because it is in a method that is not being executed. When I start the WCF program it shuts down, and the web application that contacts the WCF app gets a Communication object error. If the web application connected successfully, the code that changed would be executed. I am just going to have to dig in to WCF more than I did when I wrote the thing. One difference I noticed between the new WCF app and the old, is that the old app defines a "mex" endpoint. Of course, upon noticing this I swapped the old config file with the new code and it still didn't work, so I will have to go fish.Comment
Comment