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

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.

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=supportNote 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/KB976462Note 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.

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>