Consider the following scenario. You have a computer that has the Microsoft .NET Framework 2.0 Service Pack 2 (SP2) or the .NET Framework 3.5 SP1 installed. You use an ASMX service method that includes a property, and the property has an internal setter. The serialization may fail. This problem occurs in a scenario that resembles the following:

• The public type T includes a public property that has a public getter and an internal setter. For example, the source code may resemble the following.

  public class T
  {
                  …
                  public <Type> <Propertyname1> { get; internal set; }
                  …
  }
  

• In a Web service, the return type or the out argument of at least one Web service method returns objects of type T or objects that contain T in their object graphs. For example, the source code may resemble one of the following examples.

  • public T MyWebMethod(…)
    {
                    …
    }
    

  • public void MyWebMethod(…, out U)
    {
                    …
    }
    ...
    public Class U
    {
                    public T <Propertyname2>  { get; set; }
    }

• Type T or type U is not used in any Web service methods as a non-out-only argument.
  
  Note If a method has more than one out argument, the out arguments are called non-out-only arguments.
• The type of the property that has an internal setter is not Enumerable or Collection.
• Before you applied the .NET Framework 2.0 SP2 or the .NET Framework 3.5 SP1, you generated proxy code to the previously mentioned Web service by using the Wsdl.exe tool or the Visual Studio Add Web reference feature.
• After you deployed the Web service and clients, you applied the .NET Framework 2.0 SP2 or the .NET Framework 3.5 SP1.

In this scenario, the return type or the out argument from the previously mentioned Web service method will not be serialized. This Web service method is an object of type T or an object that contains T in their object graphs.

Note Currently, there is no separate package for the .NET Framework 2.0 SP2. The .NET Framework 2.0 SP2 is included in the package for the .NET Framework 3.5 SP1.

Hotfix information

A supported hotfix is now available from Microsoft. However, it is intended to correct only the problem that is described in this article. Apply it only to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

To resolve this problem immediately, contact Microsoft Customer Support Services to obtain the hotfix. For a complete list of Microsoft Customer Support Services telephone numbers and information about support costs, visit the following Microsoft Web site:Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.

Prerequisites

You must have the .NET Framework 2.0 SP2 or the .NET Framework 3.5 SP1 installed to apply this hotfix.

Restart requirement

You do not have to restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace a previously released hotfix.

File information

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.

x86 versions of Microsoft Windows 2000, Windows XP, and Windows Server 2003

x64 versions of Windows 2000, Windows XP, and Windows Server 2003

Itanium-based versions of Windows 2000, Windows XP, and Windows Server 2003

x86 versions of Windows Vista SP1, Windows Server Core, and Windows Server 2008

x64 versions of Windows Vista SP1, Windows Server Core, and Windows Server 2008

Itanium-based versions of Windows Server Core and Windows Server 2008

To work around this problem, use one of the following methods.

Method 1

Change the method signature to avoid the conditions that are mentioned in the "Symptoms" section.

Method 2

Move the internal setters away from the properties in the out argument.

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base: