User Interface Support Team Blog

Issues with Winform Application when running in Windows 7

Nitish Nagpal — Mon, 21 Oct 2013 12:44:00 GMT

Here comes a blog from EMEA Windows WPF & UI Subject Matter Expert and experienced Engineer Shiva Shankar

Recently one of my customers reported a problem where his Winform application started failing with “Not enough storage is available to process this command” error when running in Windows 7. Yet, the same application works great on Windows XP.

That was really something interesting. So, what could be the reason? Hmm, there may be ‘n’ number of reason, but in this blog we are going to look into a particular scenario.

[Scenario Details]

The application is using a lot of “System.Drawing.Bitmaps” objects.

In the failure scenario you notice that lot of these objects are not disposed.

Lot of 64 Kb allocations on the native side.

The application was working fine on earlier version of OS like Windows XP.

The next question would be, how do I get these details?

To get this we may need to get our hands dirty with WinDBG. I am not going deep into the analysing logs using WinDBG in this blog, but I will share some basic steps , and will concentrate more on the work around here.

Capture a crash dump when the application fails with out of memory or related exception.
Open the dump in WinDBG.
Run “!address –summary” to get the memory details.
Check the memory under “” section from the above output.
Run “!eeheap –gc” to get the managed memory details.
If the managed memory size is low compared to the total application memory, and section memory is very large. Then we can proceed further. Else this blog is not related to the problem you are interested in.
Check the total number of Bitmap used in the application. To get this details run “!dumpheap -stat -type System.Drawing.Bitmap”. This will give us the total number of “System.Drawing.Bitmap” objects in the application.
If you see that the application is using a huge number of Bitmap objects, then this work around below may solve the problem.

[Work Around]

Yes, the below option is only a work around. This is not the actual solution to the problem. The right solution to this problem may depend on the exact scenario of your application. If the application is using lot of bitmaps intentionally, then you would need to re-architect your solution to use fewer bitmaps at a time. In case you see lot of bitmap objects which are not intentional, then you would need to work on properly disposing them when not required. I will not be able to cover the solution
details in this blog, but I will try to write a different blog on this later.

GDI+ 1.1 (default on Windows 7) will call into the Windows Imaging Component (WIC) to handle image rendering. WIC improves the performance and reliability of image encoding/decoding in the application, but consumes little more memory compared to GDI+ 1.0. On Windows Vista/7 operating system, we still have an option to force our application to use GDI+ 1.0 for image rendering, but starting Windows 8 this option is not available any more. As said before, this is temporary solution only.

We need to make the below changes to App.Config file in the application to work around the problem. If you do not see this file under your project, you can add this file using Visual Studio.

1. Right click on the project and select Add -> New Item.

2. Select Application Configuration file from the list.

3. Double the file to open it for editing.

4. Add the changes and save it.

processorArchitecture="*" version="1.0.0.0" publicKeyToken="6595b64144ccf1df" language="*"/>

P.S.: The above setting will make our application work similar to earlier Windows OS like XP by using GDI+ 1.0. By forcing our application to use GDI+ 1.0, we avoid the extra memory used by WIC to render bitmap, thus keeping our application memory low as compared to using GDI+ 1.1.

Hope this helps you to earn some time to work on managing the images more efficiently and/or calling dispose properly in the application.

Written by: Shiva N Shankar

Reviewed by: David Wooden

Making your Winforms application Global

Nitish Nagpal — Mon, 06 Aug 2012 04:15:00 GMT

Recently one of our customers reported an issue that their Winforms application was not behaving properly. The size or alignments of different controls on the forms were badly affected after porting to Chinese Operating Systems resulting in overlapped controls. On top of that, due to the difference in the glyph size of the fonts, on Chinese machines there was a need to change the font size.

We discussed the issue at length and taken the feedback here are few points that we can consider making our application usable for Global customers.

We strongly suggest thinking about Globalization from the early stage of Project Lifecycle. This may not be possible always however, the sooner we do it better it is.

a. Because a fonts point size varies greatly for different fonts and it is therefore recommended to leave 15-30% more space.

2. In case there is a sudden need, we can tweak our application to adapt to the new environment :

a. For East Asian fonts it is recommended that you use GDI instead of GDI+ for rendering by setting SetCompatibleTextRenderingDefault(false) because GDI+ tends to have rendering issues with East Asian characters.

b. If AutoScaleMode is set to Inherit Controls scale according to the classes' parent's scaling mode. If there is no parent, automatic scaling is disabled. When you set AutoScaleMode to Font, Controls scale relative to the dimensions of the font the classes are using, which is typically the system font.

c. Suppose you want to set a specific point size for the font. At present, we don’t have any quick way to automatically set the font size for all the forms and its child-controls. One way to change the font is through the Winforms designer. Another approach is to change the form’s font through code. But you cannot put the code in the designer file since you should not be modifying any code in there at all.

d. In Winforms, if you do not assign a font to a form then the .NET framework will use the font returned by SystemFonts.DefaultFont. SystemFonts.DefaultFont on an English version of Windows will return Microsoft Sans Serif 8.25. On East Asian versions of Windows 7, the fonts returned by SystemFonts.DefaultFont are as follows:

i. Simplified Chinese: SimSun 9 宋体

ii. Traditional Chinese: PMingLiU 9 新細明體

iii. Japanese: MS UI Gothic 9

iv. Korean: Gulim 9 굴림

This means that if you develop a Winforms application on any version of Windows and if you do not explicitly set the font on the form then when you run the application on English Windows 7, the font that is used will be Microsoft Sans Serif 8.25. If you run this same application on a Simplified Chinese version of Windows then the font used by the form will be the font returned by SystemFonts.DefaultFont which is SimSun 9 宋体.

If you don’t want the .NET Framework to use the font provided by SystemFonts.DefaultFont then you need to explicitly set the font for the form either through the designer or in code. The child controls will generally inherit the font from the parent form. Changing the font in .Designer.cs or .Designer.vb is not supported.

The East Asian fonts’ Latin glyphs tend to be wider than their Western counter parts. If you are using the default font then there will generally be expansion when going from English systems to East Asian systems. So as mentioned above, leaving space especially between controls that can autosize is a good idea.

If you specify a font like Microsoft Sans Serif 8.25 which does not contain Chinese, Japanese or Korean glyphs then font linking will be used to provide a link to a font which contains the desired East Asian glyphs. See Globalization Step-by-Step for more details.

Please note that just because two fonts have the same point size does not guarantee that they will have glyphs that are the same size when displayed on the output device. This is also mentioned in the Font Linking section of the above mentioned article. Font sizes are not the only consideration, when localizing strings the length of translated strings will vary from language to language so it is recommended that you should leave 30 percent additional room for text expansion. This is a general rule which works most of the time. The exception to the rule is when using strings containing less than 10 characters like “OK” on a button. If you add 30% you only get one character which might not be enough when translated so if the string is less than 10 characters the general rule is to leave an additional 400%. Since these are general rules, you will need to test your application on target platforms and modify the application as needed.

Why we shouldn’t use the pre-build event to change the assembly version of a WPF project

Nitish Nagpal — Wed, 18 Apr 2012 10:10:22 GMT

Recently, I was working on a support incident where customer was changing the AssemblyVersion in the AssemblyInfo.cs file through a pre-build event. Even if we don’t change anything in the project, the build was getting fired and version number was changing.

How does a WPF project build differ?

XAML differs from most other types of applications in that its build workflow produces a two-part result with dependencies in both directions.

(a) Normal assemblies built from the C#/VB code, and

(b) BAML built from the XAML markup.

The code refers to the markup in obvious ways, and the BAML stream refers to the code any place where the markup refers to a type declared in your code. There are checks at build time and at runtime to ensure the two pieces are consistent – the version number is part of those checks.

Here is the link which describes Building a WPF Application (WPF)

If you change the version number through the pre-build event, the build-time check detects the inconsistency and rebuilds the piece that’s perceived to be out of date. In such a case, the task Markup Compilation Pass1 kicks-in.

This is by design. It would happen in any type of application that had a similar two-part interdependent build product.

Here are the guidelines When to Change File/Assembly Versions from the general .Net Framework perspective.

It’s worth to have a look at Best Practices for .NET Assembly Versioning to decide the versioning strategy and then Incrementing the Assembly Version for Each Build if needed.

Content developed by: Prabhat Tandon
Content reviewed by: Trevor Fellman

How to display controls above WebBrowserControl in Silverlight

Nitish Nagpal — Thu, 12 Apr 2012 03:49:00 GMT

Having problems when trying to render other controls over the WebBrowser control in Silverlight? You’re at the right place.

With the release of Silverlight 4.0, the WebBrowser control was introduced. But, it was designed only to be used in an ‘Out Of Browser’ application. However, with the release of Silverlight 5, the control can also be used in an ‘In-browser” trusted application.

While there are a lot of discussions around rendering controls over the “WebBrowser” control in Silverlight, successful solutions to this problem have been difficult to come by. I did my research while trying to resolve this problem for one of my customers and found a solution! But before I share the solution, let me give you a background to the problem.

Since the introduction of the WebBrowser control in Silverlight, many developers have been using it to display HTML content inside the application. But, the major limitation is the “Airspace” issue.

So, what is “Airspace”?

In an application window each pixel within the windows belongs to exactly only one HWND, which constitutes the airspace for that HWND. The HWND can render only on those pixels which belongs to it.

In a typical Silverlight OOB application, there will be only one Silverlight-HWND. So, the entire pixels in the Silverlight application belong to this HWND and that constitutes the airspace for that.

But, in our scenario when we introduce a WebBrowser control in our Silverlight OOB application, the Airspace is shared by the HWND of the WebBrowser control. And that is knows as Airspace issue.

The pixels on which the WebBrowser control resides will belong to the WebBrowser-HWND. So, Silverlight will not be able to render anything on the pixel which belongs to other HWND.

But, why does WebBrowser control create its own HWND unlike other Silverlight controls?

This is because; the WebBrowser control available in Silverlight is a wrapper around the “System.Windows.Controls.WebBrowser” control. The other Silverlight control will not create a new window for itself; rather it will be created under a single HWND. The WebBrowser control is not a real Silverlight control, but a wrapper around Windows HTML control. These native controls will create their own HWND.

Because of this, the WebBrowser control always overlaps other controls within the application. For example, when the page with the fixed header and scroll functionality are being used or when the WebBrowser control is placed under a menu control. There could be other instances.

Solution to the issue:

By using the “WebBrowserBrush”, we can overcome this problem.

The WebBrowserBrush was introduced with the WebBrowser control, and they are designed to work together to display rich HTML content.

WebBrowserBrush is a type of Brush object which paints an area with HTML content. This HTML content is provided by a WebBrowser control. Just like the other brush types, you can use a WebBrowserBrush to fill a rectangle, geometry contents of path and much more.

So, how is this brush going to help us resolve this problem?

To overcome this problem, you can hide the WebBrowser and use a WebBrowserBrush to paint the area with HTML content from the WebBrowser. The WebBrowserBrush will paint the HTML content in the same layer as other control, and will allow other controls to be displayed above it. We can show the WebBrowser control when it is needed. The only thing which we need to consider is to find an appropriate event to handle this logic.

Sample implementation:

In the sample application below, I want my combobox list to render above the WebBrowser when open. I have used the ComboBox_DropDownChanged event to handle the logic. When the list is open, I hide the WebBrowser control and paint the area with the WebBrowserBrush. I then bring the control back when the list is closed.

- XAML code snippet -


    xmlns="schemas.microsoft.com/winfx/2006/xaml/presentation"
    xmlns:x="schemas.microsoft.com/winfx/2006/xaml"
    xmlns:d="schemas.microsoft.com/expression/blend/2008"
    xmlns:mc="schemas.openxmlformats.org/markup-compatibility/2006">
 
    
        
            
                
                    
                    
                    
                
                
                    
                    
                
                
                
                           DropDownOpened="cbTestList_DropDownOpened" DropDownClosed="cbTestList_DropDownClosed" >
                    
                        
                        
                        
                        
                        
                        
                        
                        
                        
                        
                        
                        
                        
                        
                        
                        
                    
                
                          
                
                
                            Canvas.ZIndex="0" HorizontalAlignment="Stretch" 
                            VerticalAlignment="Stretch" />
                
                
                         Canvas.ZIndex="10"/>

How to integrate Silverlight Webpart with Sharepoint 2010

schalke1 — Mon, 16 May 2011 08:01:07 GMT

What brings Silverlight and SharePoint together?

Users are expecting rich, compelling interfaces

Silverlight is a perfect technology to create Web 2.0 applications in SharePoint

Limit page post backs

Silverlight applications do their processing on the client, eliminating page post backs.

Silverlight applications offload processing to the client

Processing on the client reduces the load on the SharePoint server farm.

Silverlight isolates processing on the client
Separation of design and code

You can use the MVVM pattern to separate the presentation from the processing later. This makes it easy to change the look and feel of Silverlight applications.

Common .NET development techniques

Silverlight applications are based on the .NET framework which makes it easy for .NET developers to create them. The client object model may be used to access SharePoint resources from a Silverlight application.

Overcome Sandbox limitations

Silverlight applications may be used to overcome sandboxed limitations such as the ability to call an external service, or use parts of the .NET framework which are not permitted to run in a sandboxed solution.

Ease of deployment

Silverlight applications are very easy to deploy. Anyone with the ability to upload a document to a document library can deploy a Silverlight application to a SharePoint site. Additionally, the Silverlight Web Part makes it very easy to place Silverlight applications on SharePoint web pages.

Let’s see a simple project that helps us to understand how to use Silverlight along-with SharePoint.

A Silverlight application can be hosted inside a SharePoint site and it is called as a Silverlight WebPart.

Prerequisites:-

Microsoft SharePoint Foundation 2010

Here are some steps to upload a Silverlight XAP to the SharePoint site:-

1) In Visual Studio 2010, Go to File menu -> New -> Project -> under Installed Templates -> select Visual C# -> under SharePoint section-> 2010 -> select EMPTY SHAREPOINT PROJECT.

2) For example,in this case , lets name our SharePoint project as “SharePointSilverlightProjectBlog” .

3) Then you will be asked for the URL of your SharePoint site. Enter the URL and Select the “Deploy as sandboxed solution” option in the dialog and click Finish.

4) Hence, you can see the project created as in the Solution explorer of Visual Studio 2010

5) Since our goal is to integrate Silverlight within SharePoint , lets add a Silverlight application without a website hosting it. Let’s name our Silverlight application/project as “SilverlightWebpart”. Then our solution looks as following :-

6) Let’s add the following code to “MainPage.xaml” file in the Silverlight project :-

    xmlns="schemas.microsoft.com/winfx/2006/xaml/presentation"

    xmlns:x="schemas.microsoft.com/winfx/2006/xaml"

    xmlns:d="schemas.microsoft.com/expression/blend/2008"

    xmlns:mc="schemas.openxmlformats.org/markup-compatibility/2006"

    mc:Ignorable="d"

    d:DesignHeight="300" d:DesignWidth="400">







7)      Also add the following code to “MainPage.xaml.cs” file :-

using System;

using System.Collections.Generic;

using System.Linq;

using System.Net;

using System.Windows;

using System.Windows.Controls;

using System.Windows.Documents;

using System.Windows.Input;

using System.Windows.Media;

using System.Windows.Media.Animation;

using System.Windows.Shapes;

namespace SilverlightWebpart

{

    public partial class MainPage : UserControl

    {

        public MainPage()

        {

            InitializeComponent();

        }

        private void btnClk_Click(object sender, RoutedEventArgs e)

        {

            MessageBox.Show("Hello from Silverlight within SharePoint !!");

        }

    }

}

8)      Lets just SAVE ALL for now (and not Build).

9)      Now, Add a Module to the SharePoint site. Right click the “SharePointSilverlightProjectBlog” SharePoint project and go to ADD NEW ITEM and in the dialog Select “Module ” under installed templates for SharePoint -> 2010 .

10)   Name the Module as “DemoModule”.

11)   After we add the Module it would contain two files under it by default:-

a)      Elements.xml

b)      Sample.txt

12)   It’s ok if you delete the Sample.txt file.

13)   Again lets do SAVE ALL .

14)   Let’s jump to our Silverlight project “SilverlightWebpart” and right click it in the solution explorer window and select Properties.

15)   Go to the “Build Events” tab and click the “Edit Post-build…” button and enter the following line in the dialog that appears :-

copy “$(TargetDir)SilverlightWebpart.xap” “$(SolutionDir)SharePointSilverlightProjectBlog\DemoModule"

16)   Click OK and Save it.

17)   Adding the above content in the post-build events ensures that the visual studio adds the latest build of the XAP file generated from the “SilverlightWebpart” application to the “DemoModule” section of the “SharePointSilverlightProjectBlog” project.

18)   So now if we build the Silverlight project, we would find the “SilverlightWebpart.xap” file under the “DemoModule”.

19)   Make sure the XAP file is included in the Module as following :-

20)   Now lets build the entire solution and then try to deploy the “SharePointSilverlightProjectBlog” project to the SharePoint site.

21)   To achieve this, right-click the “SharePointSilverlightProjectBlog” project and click “Deploy”

22)   Now the “SharePointSilverlightProjectBlog” project is deployed in the SharePoint site.

23)   Let’s open the SharePoint site in the browser and select “Page

24)   Select Edit.

25)   Having done that Select “Insert” tab and click “Web Part” .

26)   In “Categories”, select “Media and content” and correspondingly in “Web Parts” column, Select “Silverlight Web Part” Having Selected the “Silverlight Web Part” , click on “Add” button that appears on the right side.

27)   After clicking add, a small pop-up will appear asking for the URL of the Silverligth content(.xap) file. Enter the URL in the following format as :0

MySharePointSite/DemoModule/SilverlightWebpart.xap

28)   Then click OK and then you can see you Silverlight web part appear in the SharePoint site as :

29)   As you cans ee the blue border is the boundary of the Silverlight web part and the Silverlight application has a button in it. When you click the button, it acts like a normal Silverlight application and responds to the user interaction and a Message Box is popped, for which we wrote code in “MainPage.xaml.cs”.

Content By - Sagar Joshi

Launching WPF application using CLR hosting from C++ application

schalke1 — Thu, 19 Aug 2010 10:36:00 GMT

Recently, I was working with one of my developer customers. Customer's objective was to launch a WPF application from a C++ console based application.

To achieve the same the customer was using CLRHosting and launching WPF application by calling ExecuteInDefaultAppDomain method.

The customer developed the application, but when he tried to execute it, C++ application failed with a first chance exception on ExecuteInDefaultAppDomain and WPF application which prevented it from getting launched.

Here is the code used for CLR hosting and launching a method in assembly (WPF) by calling ExecuteInDefaultAppDomain.

int main(int argc, _TCHAR* argv[])

{

    // Bind to the runtime.

    ICLRRuntimeHost *pClrHost = NULL;

    HRESULT hrCorBind = CorBindToRuntimeEx(

        NULL,   // Load the latest CLR version available

        L"wks", // Workstation GC ("wks" or "svr" overrides)

        0,      // No flags needed

        CLSID_CLRRuntimeHost,

        IID_ICLRRuntimeHost,

        (PVOID*)&pClrHost);

    // Construct our host control object.

    DHHostControl *pHostControl = new DHHostControl(pClrHost);



    // Notify the CLR that this host implements hosting managers.

    pClrHost->SetHostControl(pHostControl);

    // Now, start the CLR.

    HRESULT hrStart = pClrHost->Start();

    // Load an assembly and execute a method in it.

    HRESULT hrExecute = pClrHost->ExecuteInDefaultAppDomain(

        pwzAssemblyPath, pwzAssemblyName,

        pwzMethodName, pwzMethodArgs,

        &retVal);

}

pwzMethodName in the code above, is the method defined in WPF application, the purpose of this method in WPF application is to launch the WPF application itself by calling Main method while pwzAssemblyName is the name of WPF application.

The code snippet is part of following MSDN article which talks about CLR hosting:

msdn.microsoft.com/en-us/magazine/cc163567.aspx

Please note that code above can be used to launch a method from any assembly and is not specific to WPF.

Running the code outside the debugger gave the following error-

System.Windows.Markup.XamlParseException: Cannot create instance of 'Window1' defined in assembly WpfApplication1, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null'. Exception has been thrown by the target of an invocation. Error in markup file 'Window1.xaml' Line 1 Position 9. ---> System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.InvalidOperationException: The calling thread must be STA, because many UI components require this.

As the message clearly indicates that calling thread needs to be STA and it's known that WPF is also STA. taking the clue I used following line of code to make the C++ console based application STA.

CoInitializeEx(NULL,COINIT_APARTMENTTHREADED);

Adding the above line of code did the trick and the WPF application launched fine!

Content By – Sumit Gupta

Issues using Response.Redirect in Silverlight

schalke1 — Thu, 12 Aug 2010 10:20:00 GMT

I was working with one of customer's today, on a Silverlight application. The customer wanted to make the browser redirect the client to a different URL. As in the current scenario the re-direction was to be made to an internal Silverlight Page within the application we had to use something like-

Response.Redirect();localhost/SilverlightSampleTestPage.aspx#/About
In the above example we are trying to redirect to About page.

The application worked liked a charm until it was noticed that when redirected to the About page, the About page would get loaded twice. In order to confirm the same, we used Fiddler which helped us confirm the behavior.

On further investigation it was found that Response.Redirect causes the browser to do a fresh navigation rather than fragment navigation. Due to this Internet Explorer demands for a new copy of the file and hence loads it twice. This is by design.

As the behavior cannot be changed, the following workaround can be used-

1)      Create an initialization parameter, for example initparam.

2)      Assign the page name to which the re-direction is required, to the value attribute, example value="link=/About"

3)      Write the following code to redirect to the new page mentioned in the value attribute
Application.Current.Host.NavigationState = App.Current.Resources["link"].ToString();

4)      This will help us, get the same results as Response.Rediect without the issue of the page loading twice.

Content By – Sandeep Chalke

Using Silverlight to upload more than 8KB of data from a WCF Service

schalke1 — Tue, 01 Jun 2010 12:34:00 GMT

Recently, I encountered an issue where one of my customer was trying to upload more than 8KB (8192 characters) of data from a WCF Service which was consumed by a Silverlight client. The Silverlight application would work fine, till the data upload was limited to 8192 characters, but just increasing it to 8193 characters would throw the following error-

"An exception occurred during the operation, making the result invalid. Check the InnerException for exception details."

If we step through the code the InnerException looks like the following-

System.ServiceModel.CommunicationException was unhandled by user code
Message=The remote server returned an error: NotFound.
StackTrace:
       at System.ServiceModel.AsyncResult.End[TAsyncResult](IAsyncResult result)
       at System.ServiceModel.Channels.ServiceChannel.EndCall(String action, Object[] outs, IAsyncResult result)
       at System.ServiceModel.ClientBase`1.ChannelBase`1.EndInvoke(String methodName, Object[] args, IAsyncResult result)
       at WCFTest.ServiceReference.TestServiceClient.TestServiceClientChannel.EndDoWork(IAsyncResult result)
       at WCFTest.ServiceReference.TestServiceClient.WCFTest.ServiceReference.ITestService.EndDoWork(IAsyncResult result)
       at WCFTest.ServiceReference.TestServiceClient.OnEndDoWork(IAsyncResult result)
       at System.ServiceModel.ClientBase`1.OnAsyncCallCompleted(IAsyncResult result)
InnerException: System.Net.WebException
       Message=The remote server returned an error: NotFound.
       StackTrace:
            at System.Net.Browser.AsyncHelper.BeginOnUI(SendOrPostCallback beginMethod, Object state)
            at System.Net.Browser.BrowserHttpWebRequest.EndGetResponse(IAsyncResult asyncResult)
            at System.ServiceModel.Channels.HttpChannelFactory.HttpRequestChannel.HttpChannelAsyncRequest.CompleteGetResponse(IAsyncResult result)
       InnerException: System.Net.WebException
            Message=The remote server returned an error: NotFound.
            StackTrace:
                 at System.Net.Browser.BrowserHttpWebRequest.InternalEndGetResponse(IAsyncResult asyncResult)
                 at System.Net.Browser.BrowserHttpWebRequest.<>c__DisplayClass5.b__4(Object sendState)
                 at System.Net.Browser.AsyncHelper.<>c__DisplayClass2.b__0(Object sendState)
            InnerException:

I found many posts which gave solution to the issue and said following those would help one upload more than 8KB of data, but none seemed to help. One, thing was clear, the solution had to do with changing the WCF Service configuration.

On doing much of research, I got a the correct solution, which is as follows-

A) In the Visual Studio open the solution which exhibits the issue. For now let’s call it WCFTest.

B) Go to Tools -> WCF Service Configuration Editor.

C) Click File -> Open and browser to the Web.Config for the WCFTest.Web project.

D) Select Bindings -> New Binding Configuration.

E) Select basicHttpBinding and give a name for example - LargeBinding.

F) Select LargeBinding under Bindings and change MaxBufferPoolSize, MaxBufferSize, MaxReceivedMessageSize, MaxArrayLenght, MaxBytesPerRead to 2147483647.

G) Select Services -> WCFTest.Web.TestService -> Endpoints -> Select the binding which is used to bind the WCF Service, by default. In this case, let's assume it to be TestBinding. Change the BindingConfiguration to LargeBinding.

H) Save the Web.Config.

I) Open the ServiceReference.ClientConfig file in WCF Service Configuration Editor.

J) Go to Bindings -> TestBinding (basicHTTPBinding) and change the MaxBufferSize and MaxReceivedMessageSize to 2147483647.

K) Save the ServiceReference.ClientConfig file and exit out of WCF Service Configuration Editor.

L) Build the solution and now the WCF Service should be able to upload more than 8K of data.

Hope this helps!!!!

Content By – Sandeep Chalke