Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>There are server side "endpoints".........</p> <p>But on the client........you have to add some entries that point to the server side endpoints.</p> <p>To answer your question, (no), you MUST define information on the client side. It is basically saying "here is where to find the service you want to use"</p> <p>They will look very similar.</p> <p>SERVER SIDE:</p> <p></p> <pre><code>&lt;endpoint address = "http://localhost:8001/MammalControllerFascade" binding = "wsHttpBinding" bindingConfiguration="WSHttpBindingName1" contract = "GranadaCoder.Applications.TrinugWCFDemoVersion1.Interfaces.Controllers.IMammalController" &gt; &lt;/endpoint&gt; &lt;endpoint address = "net.pipe://localhost/LocalMammalControllerFascade" binding = "netNamedPipeBinding" bindingConfiguration="NamedPipeBindingName1" contract = "GranadaCoder.Applications.TrinugWCFDemoVersion1.Interfaces.Controllers.IMammalController" &gt; &lt;/endpoint&gt; </code></pre> <p></p> <p>CLIENTSIDE</p> <pre><code>&lt;client&gt; &lt;endpoint name="WSHttpEndPoint" address = "http://localhost:8001/MammalControllerFascade" binding = "wsHttpBinding" bindingConfiguration="WSHttpBindingName1" contract = "GranadaCoder.Applications.TrinugWCFDemoVersion1.Interfaces.Controllers.IMammalController" &gt; &lt;/endpoint &gt; &lt;endpoint name="NamedPipeEndPoint" address = "net.pipe://localhost/LocalMammalControllerFascade" binding = "netNamedPipeBinding" bindingConfiguration="NamedPipedBindingName1" contract = "GranadaCoder.Applications.TrinugWCFDemoVersion1.Interfaces.Controllers.IMammalController" &gt; &lt;/endpoint &gt; &lt;/client&gt; </code></pre> <p>Note, they are similar. Note, on the client side, the ENDPOINT has a name. That is so the client can refer to the ENDPOINT by name.</p> <p>EDIT:</p> <p>Are you running both the Host and the Client?</p> <p>You cannot just run the client in debug mode. The service must be started.</p> <p>Right click the solution, properties..............and set up 2 start up projects. (if you are self-hosting)</p> <p>If you are not self-hosting.....then how are you "serving up server" ? (what is running the server side code) during debug?</p> <p>EDIT:</p> <p>I store my "sectional information" in different files. So I can maintain them without getting everything garbled up in the same app.config (or web.config).</p> <p>Here is a sample:</p> <p>APP.CONFIG (or web.config)</p> <p> </p> <pre><code>&lt;system.serviceModel&gt; &lt;behaviors configSource="WCFBehaviors.config"&gt; &lt;/behaviors&gt; &lt;bindings configSource="WCFBindings.config"&gt; &lt;/bindings&gt; &lt;client configSource="WCFClient.config"&gt; &lt;/client&gt; &lt;services configSource="WCFServices.config"&gt; &lt;/services&gt; &lt;/system.serviceModel&gt; </code></pre> <p></p> <p>and I'll show one of the files above.</p> <p>contents of "WCFClient.config" seen below. The other files follow the same pattern.</p> <pre><code>&lt;client&gt; &lt;endpoint name="WSHttpEndPoint" address = "http://localhost:8001/MammalControllerFascade" binding = "wsHttpBinding" bindingConfiguration="WSHttpBindingName1" contract = "GranadaCoder.Applications.TrinugWCFDemoVersion1.Interfaces.Controllers.IMammalController" &gt; &lt;/endpoint &gt; &lt;endpoint name="NamedPipeEndPoint" address = "net.pipe://localhost/LocalMammalControllerFascade" binding = "netNamedPipeBinding" bindingConfiguration="NamedPipedBindingName1" contract = "GranadaCoder.Applications.TrinugWCFDemoVersion1.Interfaces.Controllers.IMammalController" &gt; &lt;/endpoint &gt; &lt;/client&gt; </code></pre>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload