locked
WCF File-less activation and net.tcp RRS feed

  • Question

  • I had a simple service setup using an .svc file and it was hosting both http and net.tcp.

    I then added a serviceactivation section in my web.config file, set my relativeaddress to a .svc file of the same  name and the service to my namespace.service name.

    Http still works file, but net.tcp throws this exception.

    Could not connect to net.tcp://<machineanddomainname>/MyService/MyService.svc. The connection attempt lasted for a time span of 00:00:21.0232025. TCP error code 10060: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond 2001:0:cc9:ff0a:8d:2319:ba7b:5ae0:808.

    If I add a service reference to the service (the .svc file) it still gives me a net.tcp address but I believe that when you go back to file-less activation, doesn't that move you back to http only?


    STom

    Sunday, December 23, 2012 5:19 PM

Answers

  • What I meant was, after I had removed the physical .svc file, I had deployed the service to IIS. At that point in time, I already knew what the address was where I would use to add my service reference.

    The actual problem ended up being that in my endpoint addresses, it was referencing my machine name, domain etc and could not resolve via DNS. I changed the endpoint addresses to 'localhost' and that solved the problem.


    STom

    • Marked as answer by stombiztalker Tuesday, December 25, 2012 2:48 PM
    Tuesday, December 25, 2012 2:48 PM

All replies

  • What is the meaning of "If I add a service reference to the service (the .svc file) it still gives me a net.tcp address but I believe that when you go back to file-less activation, doesn't that move you back to http only?"?

    Do you mean after apply serviceactivation net.tcp does not work, before that both net.tcp and http work?

    Tuesday, December 25, 2012 8:07 AM
  • What I meant was, after I had removed the physical .svc file, I had deployed the service to IIS. At that point in time, I already knew what the address was where I would use to add my service reference.

    The actual problem ended up being that in my endpoint addresses, it was referencing my machine name, domain etc and could not resolve via DNS. I changed the endpoint addresses to 'localhost' and that solved the problem.


    STom

    • Marked as answer by stombiztalker Tuesday, December 25, 2012 2:48 PM
    Tuesday, December 25, 2012 2:48 PM