Skip to main content

Large Volume of Dataset Transfer from WCF to Silverlight

Most of the times the developers, architects have the problem to retrieve large volume of data from WCF Service to Silverlight client applications. It’s a big head ache for developers. But it’s not up to that much problematic one. We can solve this problem by changing some property’s values in Web.config of WCF Service host, Silverlight application’s ServiceReference.clientconfig and Silverlight XAP hosted ASP.Net Applications.

Here I’m going to explain the Web.config changes we need to retrieve large volume of data from WCF Service and also uploading large size of files to the Server.

Last week, I was trying to figure out why my WCF service call always threw the generic NotFound exception when trying to retrieve large datasets. Even though, I set buffer limits to 2147483647 (int.MaxValue) in the Silverlight ServiceReferences.ClientConfig file and WCF Service configuration Section under web.config the problem was persisting. I tried so many things from Data Access Layer and UI. Finally I did these changes in configuration files and now the application working fine. If you are also in a similar situation, here are some useful steps to ensure that you can retrieve large amounts of data from a WCF service.

WCF Service to Silverlight
Enable the WCF service to send large amounts of data. To do this, You need to set the binding buffer limits as well as the DataContractSerializer's  maxItemsInObjectGraph value. Here's an extract from WCF service Web.config with all the limits set to maximum.
<system.serviceModel>
                        <serviceHostingEnvironment multipleSiteBindingsEnabled="true" />
  <bindings>
                                    <basicHttpBinding>
                                                <binding name="LargeBuffer" maxBufferSize="2147483647" maxReceivedMessageSize="2147483647">
                                                            <readerQuotas maxDepth="2147483647" maxArrayLength="2147483647" maxBytesPerRead="2147483647" maxNameTableCharCount="2147483647" maxStringContentLength="2147483647"/>
                                                binding>
                                   basicHttpBinding>
                        bindings>
                        <services>
                                    <service behaviorConfiguration="Webservices.MyServiceBehavior" name="Webservices.MyService">
                                                <endpoint address="" binding="basicHttpBinding" bindingConfiguration="LargeBuffer" contract="Webservices.IMyService">
                                                            <identity>
                                                                        <dns value="localhost"/>
                                                            identity>
                                                endpoint>
                                                <endpoint address="mex" binding="mexHttpBinding" contract="IMetadataExchange"/>
                                    service>
                        services>
                        <behaviors>
   <serviceBehaviors>
    <behavior name="Webservices.MyServiceBehavior">
     <serviceMetadata httpGetEnabled="true" />
     <serviceDebug includeExceptionDetailInFaults="false" />
      <dataContractSerializer maxItemsInObjectGraph="2147483647"/>
    behavior>
   serviceBehaviors>
  behaviors>
            system.serviceModel>

That’s it from the WCF Service side., We need to do some changes in the Silverlight Application’s ServiceReferences.ClientConfig file. Enable the Silverlight client to retrieve huge amount of data by enabling large buffers. You need to increase buffer and message size limits for the binding inside ServiceReferences.ClientConfig something like this:
<system.serviceModel>
    <bindings>
      <basicHttpBinding>
        <binding name="BasicHttpBinding_MyService" maxBufferSize="2147483647"
          maxReceivedMessageSize="2147483647" transferMode="Buffered">
          <security mode="None" />
        binding>
      basicHttpBinding>
    bindings>
    <client>
      <endpoint address="http://prodsp.com/MyServiceHost/MyService.svc"
        binding="basicHttpBinding" bindingConfiguration="BasicHttpBinding_MyService"
        contract="Webservices.IMyService" name="BasicHttpBinding_MyService" />
    client>
  system.serviceModel>

The above changes are enough to transfer huge amount of data from WCF to Silverlight Client.
Silverlight to WCF Service

Next…I’ll explain one simple step to send large volume of data from Silverlight to WCF Service. However if you like to send large volume of data from Siverlight to a WCF Service, you need to do one change in Silverlight hosted Web Application’s Web.Config. The default maximum permitted HTTP request length is just 4MB. We can increase this value to transfer large volume of data from Silverlight to WCF Service. The maximum value for maxRequestLength attribute is 2097151.
<httpRuntime maxRequestLength="209751"/>

Just add this this in Silverlight hosted Web Application’s Web.Config.
If these post really helpful to resolve your problem then leave your valuable comments as well.

Comments

Post a Comment

Popular posts from this blog

Javascript - Unanswered questions - Part 1

What is Event delegation? Event delegation is Javascript as it relates to the DOM. It basically means that if you attach an event listener to a DOM element that listener is not only firing on that DOM element. It's actually firing on every children in that. So, for instance if you have a navigation and so you've got an unordered list you've got list items and then you've got anchor tags inside that navigation what you have. If you add an event listener to the ul element in essence you're actually adding event listener to all of the children as well. In short, JS event listeners fir not only on a single DOM element but on all its descendants. What is Event Bubbling? It's actually inverse of Event delegation. Also known as propagation, events on an DOM element will bubble up and also fire on all parents.  What's the difference between "target" and "currentTarget"? target is the actual element that triggered the event for example clicked, wh

One or more ActiveX controls could not be displayed because..... in Outlook

Some times We've facing this problem in Microsoft Outlook. While trying to add the images to our mails or Opening some emails. 1) Your current security settings prohibit running ActiveX controls on this page, or 2) You have blocked a publisher of one of the controls As a result, the page may not display correctly. To resolve this problem follow these steps. In Microsoft Outlook : Go to Tools > Options > Mail Format > Message Format Check the options " Use MS Office Word to ....". Happy Mailing..........................

Microservices vs. APIs

It still surprises me just how many times I come across misconceptions around Micro Services and APIs. Often hearing phrases like micro services are fine grained web services or API is themselves are equivalent to micro services. These all sort of show fundamental misconceptions under the covers. So, I've written this just to really break that out and explain about what the key differences are in those two concepts. What is an API? An API, fundamentally Application Programming Interface, that is an interface. It's a way of making requests into a component. So it's the route that you go in to make those requests. In modern use that typically means a REST API, that's a call made using HTTP protocol using JSON data as the payload. What are Micro Services? So let's ensure we also have a clear crisp definition on what a micro service architecture really is. Micro-Services architecture is about breaking down large silo applications into smaller components. That are more m