StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
text
Body
copied!<p>We are using IIS 7 hosting about 20 services with the net.tcp and net.pipe bindings and it's working fine. </p> <p>Your problem with the pipe looks like a misconfiguration to me. If it helps, this is how we have them configured:</p> <p>Server:</p> <pre><code> <endpoint address ="" binding="fooBinding" contract="Bla.IBlaAPI" bindingConfiguration="BlaAPI.BindingConfig"> </code></pre> <p></p> <p>Binding config:</p> <pre><code><binding name="BlaAPI.BindingConfig" receiveTimeout = "10:50:00" sendTimeout = "10:50:00" maxReceivedMessageSize="2147483647" maxBufferSize="2147483647" maxBufferPoolSize="2147483647" transactionFlow="false"> <readerQuotas maxDepth="32" maxStringContentLength="2147483647" maxArrayLength="2147483647" maxBytesPerRead="8192" maxNameTableCharCount="2147483647" /> <security mode="None"/> </binding> </code></pre> <p>Note that we are using long timeouts and have really high quotas for message size and etc. because we are passing some big chunks of data through this service. You can adjust for your own needs. We have the security set to "none" because the service is only being contacted from the local machine which is secured. Again, your mileage may vary.</p> <p>Client:</p> <pre><code><endpoint name="Bla.Bindings.BlaAPI" address="net.pipe://localhost/bla/IBlaAPI.svc" behaviorConfiguration="BlaAPI.ServiceBehavior" binding="netNamedPipeBinding" bindingConfiguration="BlaAPI.BindingConfig" contract="Bla.IBlaAPI" /> </code></pre> <p>About the Faulted state problem, please note that if an unhandled exception occurs during execution of the service code, the service instance will remain in Faulted state until it is closed properly. To avoid this, either handle exceptions at service top-level or use, for example, Enterprise Library Excexption Handling blocks.</p>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

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