A hotfix for the.NET Framework 3.5 Service Pack 1 is available for Windows 7 and for Windows Server 2008 R2 as a prerequisite for Microsoft Office SharePoint Server 2010

View products that this article applies to.

INTRODUCTION

This hotfix provides the following features for Windows Communication Foundation (WCF) in the Microsoft .NET Framework 3.5 Service Pack 1 (SP1) on a computer that is running Windows 7 or Windows Server 2008 R2. This hotfix is also a prerequisite for Microsoft Office SharePoint Server 2010.

Feature 1

The hotfix adds the AllowInsecureTransport property in the SecurityBindingElement class for the .NET Framework 3.5 Service Pack 1. The default value of this property is set to False. When the property is set to True, the mixed-mode secured message can be sent over an unsecured transport such as HTTP in Windows Communication Foundation (WCF) services. The property should be set to True only when the client and the service are in a trusted environment.

Feature 2

WCF services in the .NET Framework 3.5 Service Pack 1 use only a single thread to receive secure messages, even if SharePoint has multiple Web services concurrently receiving requests from different service clients.

This hotfix adds DispatcherSynchronization endpoint functionality to improve the performance of the SharePoint services that use WCF. This endpoint functionality lets you use multiple threads in a service instance to concurrently receive secure messages.

Feature 3

This hotfix provides access to the OutgoingSupportingTokens property in the SecurityMessageProperty class. SharePoint Web service clients can use this new property to reduce the average latency of client-side requests by reusing tokens when they are required. Previously, tokens were regenerated for each request.

↑ Back to the top

More Information

Hotfix information

A supported hotfix is now available from Microsoft. However, it is intended to correct only the problem that this article describes. Apply it only to systems that are experiencing this specific problem.

To resolve this problem, 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 website:

http://support.microsoft.com/contactus/?ws=support

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.

To download this hotfix from the Microsoft Developer Network (MSDN) Code Gallery, visit the following Microsoft Web site:

http://code.msdn.microsoft.com/KB976462

Note The MSDN Code Gallery displays the languages for which the hotfix is available. If you do not see your language listed, it is because the Code Gallery resource page is not available for that language.

Alternatively, you can download this hotfix rollup from the following Microsoft Connect Web site:

https://connect.microsoft.com/VisualStudio/Downloads/DownloadDetails.aspx?DownloadID=23806

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.

File information

For all supported x86-based versions of Windows 7

File name	File version	File size	Date	Time	Platform
Smdiagnostics.dll	3.0.4506.5000	110,592	23-Nov-2009	23:22	x86
System.identitymodel.dll	3.0.4506.5000	438,272	23-Nov-2009	23:22	x86
System.runtime.serialization.dll	3.0.4506.5000	970,752	23-Nov-2009	23:22	x86
System.servicemodel.dll	3.0.4506.5000	5,967,872	23-Nov-2009	23:22	x86
Servicemonikersupport.dll	3.0.4506.5000	17,256	23-Nov-2009	23:22	x86

For all supported x64-based versions of Windows 7 and of Windows Server 2008 R2

File name	File version	File size	Date	Time	Platform
Servicemonikersupport.dll	3.0.4506.5000	19,304	23-Nov-2009	23:23	x64
Smdiagnostics.dll	3.0.4506.5000	94,208	23-Nov-2009	23:23	x64
System.identitymodel.dll	3.0.4506.5000	397,312	23-Nov-2009	23:23	x64
System.runtime.serialization.dll	3.0.4506.5000	847,872	23-Nov-2009	23:23	x64
System.servicemodel.dll	3.0.4506.5000	5,304,320	23-Nov-2009	23:23	x64

For all supported Itanium-based versions of Windows Server 2008 R2

File name	File version	File size	Date	Time	Platform
Servicemonikersupport.dll	3.0.4506.5000	33,640	23-Nov-2009	23:21	IA-64
Smdiagnostics.dll	3.0.4506.5000	94,208	23-Nov-2009	23:21	IA-64
System.identitymodel.dll	3.0.4506.5000	397,312	23-Nov-2009	23:21	IA-64
System.runtime.serialization.dll	3.0.4506.5000	847,872	23-Nov-2009	23:21	IA-64
System.servicemodel.dll	3.0.4506.5000	5,304,320	23-Nov-2009	23:21	IA-64

Prerequisites

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

Restart requirements

You do not have to restart the computer after you install this hotfix if there is no .NET Framework instance currently being used.

↑ Back to the top

Examples of the new features

The following code example shows how to use the AllowInsecureTransport property in the security configuration of a custom binding.

<customBinding>
   <binding name="SampleHttpBinding">
      <security
           authenticationMode="IssuedTokenOverTransport"
           allowInsecureTransport="true"/> 
      <binaryMessageEncoding/>     
      <httpTransport/>
   </binding>
</customBinding>

The following code example shows how to use the DispatcherSynchronization endpoint behavior to specify the maximum number of threads for receiving messages.

<services>
      <service name="MicrosoftMyTestService">
        <endpoint address="http://loocalhost/IService" binding="customBinding"
                  contract="IService"
                  behaviorConfiguration="ServiceEPBehavior" bindingConfiguration="MyCustomBinding">
        </endpoint>
      </service>
    </services>
    <behaviors>
      <endpointBehaviors>
        <behavior name="ServiceEPBehavior">
          <dispatcherSynchronization maxPendingReceives="10"/> 
        </behavior>
      </endpointBehaviors>
    </behaviors>

↑ Back to the top

Status

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

↑ Back to the top

References

For more information about the functionality that is described in the "Feature 1" section , click the following article number to view the article in the Microsoft Knowledge Base:

971831 FIX: A hotfix that adds a SecurityBindingElement.AllowInsecureTransport property that allows the mixed-mode secured message to be sent over an unsecured transport in WCF is available for the .NET Framework 3.5 Service Pack 1

For more information about the functionality that is described in the "Feature 2" section, click the following article number to view the article in the Microsoft Knowledge Base:

975955 A hotfix is available that adds an endpoint behavior that lets services use multiple threads to receive secure messages in the .NET Framework 3.5 Service Pack 1

For more information about the functionality that is described in the "Feature 3" section, click the following article number to view the article in the Microsoft Knowledge Base:

976394 FIX: A hotfix is available that makes the SecurityMessageProperty.OutgoingSupportingToken property public in the Microsoft .NET 3.5 Service Pack 1

For more information about the SecurityMessageProperty.OutgoingSupportingTokens property in the .NET Framework 4.0, visit the following Microsoft Web site:

http://msdn.microsoft.com/en-us/library/system.servicemodel.security.securitymessageproperty.outgoingsupportingtokens(VS.100).aspx

For more information about the SecurityBindingElement.AllowInsecureTransport property in the .NET Framework 4.0, visit the following Microsoft Web site:

http://msdn.microsoft.com/en-us/library/system.servicemodel.channels.securitybindingelement.allowinsecuretransport(VS.100).aspx

For more information about the DispatcherSynchronizationBehaviorclass in the .NET Framework 4.0, visit the following Microsoft Web site:

http://msdn.microsoft.com/en-us/library/system.servicemodel.description.dispatchersynchronizationbehavior(VS.100).aspx

↑ Back to the top