I suggest you ...

Allow user to specify larger MaxBufferSize etc to prevent silent failures.

Turned out (for me and I suspect others) that when it just stopped working, the serialized object was larger than the default WCF maxbuffer size of 64k. This would throw a silent error, and the server is removed, after which no messages work. I added a maxBufferSize on the services constructors, pass it to GetBinding in which I set the MaxBufferSize, MaxBufferPoolSize and MaxReceivedMessageSize and all works.

1 vote
Vote
Sign in
Check!
(thinking…)
Reset
or sign in with
  • facebook
  • google
    Password icon
    I agree to the terms of service
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    JakeLJakeL shared this idea  ·   ·  Admin →

    0 comments

    Sign in
    Check!
    (thinking…)
    Reset
    or sign in with
    • facebook
    • google
      Password icon
      I agree to the terms of service
      Signed in as (Sign out)
      Submitting...

      Feedback and Knowledge Base