none
WCF service works in Visual Studio but EXE cannot find endpoint for the service RRS feed

  • Question

  • I have created a winforms application using a WCF DataService.

    The application runs in the Visual Studio IDE, but it does not run from the debug.exe

    On my app.config I have this endpoint:

        <client>
            <endpoint address="http://localhost:8733/Design_Time_Addresses/DataService/Service1/"
                binding="basicHttpBinding" bindingConfiguration="BasicHttpBinding_IService1"
                contract="ServiceReference1.IService1" name="BasicHttpBinding_IService1" />
        </client>

    When I run the application from the exe, I get the message that

    "There was no endpoint listening at

    http://localhost:8733/Design_Time_Addresses/DataService/Service1 

    that could accept the message."

    How can I deploy the service on the machine so the exe can find it?

    Tuesday, November 5, 2013 7:31 PM

Answers

  • <copied>

    How can I deploy the service on the machine so the exe can find it?

    <end>

    The app.config only applies or is in use in the VS IDE in debug mode.

    When the program is built, then the app.config information is copied and a file is created called programname.exe.config. The file resides at the location of the programname.exe file. Programname.exe.config is the runtime config file that .NET is looking for, and it is the config that .NET is looking for where a config file is being used for any exe project type solution. Programname.exe.config must always be deployed at the same location where the programname.exe is located so .NET can find it. 

    Wednesday, November 6, 2013 1:24 PM
  • Hi,

    From your description, it seems that you have something wrong with debuging the wcf service, if so, please try to check the following.

    #How to debug the wcf service:
    http://blogs.msdn.com/b/greggm/archive/2008/03/17/debugging-wcf-services-in-visual-studio-2008.aspx .

    And your question is about the WCF Data Services, it will be better for you to post your question to the WCF Data Services Forums, then you will get a good reply from the experts:
    #WCF Data Service Forums:
    http://social.msdn.microsoft.com/Forums/en-US/home?forum=adodotnetdataservices .

    Best Regards,
    Amy Peng


    We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
    Click HERE to participate the survey.

    Wednesday, November 6, 2013 7:39 AM
    Moderator

All replies

  • Hi, 

    can you please poste your app.config  of your servicehost application  we need to  make an idea of how both sides are done  

    Hope this  help   


    A man's dreams are an index to his greatness

    Tuesday, November 5, 2013 10:35 PM
  • Hi,

    From your description, it seems that you have something wrong with debuging the wcf service, if so, please try to check the following.

    #How to debug the wcf service:
    http://blogs.msdn.com/b/greggm/archive/2008/03/17/debugging-wcf-services-in-visual-studio-2008.aspx .

    And your question is about the WCF Data Services, it will be better for you to post your question to the WCF Data Services Forums, then you will get a good reply from the experts:
    #WCF Data Service Forums:
    http://social.msdn.microsoft.com/Forums/en-US/home?forum=adodotnetdataservices .

    Best Regards,
    Amy Peng


    We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
    Click HERE to participate the survey.

    Wednesday, November 6, 2013 7:39 AM
    Moderator
  • <copied>

    How can I deploy the service on the machine so the exe can find it?

    <end>

    The app.config only applies or is in use in the VS IDE in debug mode.

    When the program is built, then the app.config information is copied and a file is created called programname.exe.config. The file resides at the location of the programname.exe file. Programname.exe.config is the runtime config file that .NET is looking for, and it is the config that .NET is looking for where a config file is being used for any exe project type solution. Programname.exe.config must always be deployed at the same location where the programname.exe is located so .NET can find it. 

    Wednesday, November 6, 2013 1:24 PM