Click here to Skip to main content
15,885,906 members

WCF Binding error. Silverlight 4

DominicZA asked:

Open original thread
Hi

I am trying to save save a fairly large string to the database. I send the required information to the server but I get the following error:

There was an error deserializing the object of type AASC.DAL.Types.EventDTO. The maximum string content length quota (8192) has been exceeded while reading XML data. This quota may be increased by changing the MaxStringContentLength property on the XmlDictionaryReaderQuotas object used when creating the XML reader.

I add the following to the relevant section of my service's web.config:

<textMessageEncoding>
<readerQuotas maxStringContentLength=”2147483647″/>
</textMessageEncoding>

Now, my service doesn't compile. it builds fine with no errors, but gives me the following error:

Failed to add a service. Service metadata may not be accessible. Make sure your service is running and exposing metadata.

Here is the serviceModel section of my web.config:
XML
<bindings>
      <customBinding>
        <binding name="AASC.DAL.AASCData.customBinding0">
          <binaryMessageEncoding />
          <httpTransport maxReceivedMessageSize="2147483647" maxBufferSize="2147483647" />
          <textMessageEncoding>
            <readerQuotas maxStringContentLength="2147483647" />
          </textMessageEncoding>
        </binding>
      </customBinding>
    </bindings>

As soon as I remove that attribute from my web.config it works fine, but with the string limit at 8192.

Any suggestions?
Tags: WCF, Silverlight

Plain Text
ASM
ASP
ASP.NET
BASIC
BAT
C#
C++
COBOL
CoffeeScript
CSS
Dart
dbase
F#
FORTRAN
HTML
Java
Javascript
Kotlin
Lua
MIDL
MSIL
ObjectiveC
Pascal
PERL
PHP
PowerShell
Python
Razor
Ruby
Scala
Shell
SLN
SQL
Swift
T4
Terminal
TypeScript
VB
VBScript
XML
YAML

Preview



When answering a question please:
  1. Read the question carefully.
  2. Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
  3. If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
  4. Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.
Let's work to help developers, not make them feel stupid.
Please note that all posts will be submitted under the http://www.codeproject.com/info/cpol10.aspx.



CodeProject, 20 Bay Street, 11th Floor Toronto, Ontario, Canada M5J 2N8 +1 (416) 849-8900