This article describes Hotfix Rollup 2733949 for the Microsoft .NET Framework 3.5 Service Pack 1 (SP1). This hotfix rollup provides fixes for stability, reliability, and performance issues in the .NET Framework 3.5 SP1.
This hotfix rollup is available for the following operating systems:
For example, you have a machine.config file or a web.config file that contains a redirected section such as the following:
After a .NET Framework update is installed, there are additional entries under the "bindingExtensions" element as in the following example:
This problem causes the configuration file to be invalid. The presence of the "configSource" attribute in the "bindingExtensions" element means that there should be no child elements under "bindingExtensions" in the configuration file. Additionally, when you run a Windows Communication Foundation (WCF) application on the computer, you receive a System.Configuration.ConfigurationException exception.
After this hotfix rollup is installed, future updates that are installed will be aware of the presence of the "configSource" attribute and refrain from changing these elements.
Workaround
To work around this issue, use one of the following methods:
This hotfix rollup is available for the following operating systems:
- Windows XP Service Pack 3 (SP3)
- Windows Server 2003 Service Pack 2 (SP2)
- Windows Server 2008 Service Pack 2 (SP2)
- Windows Vista Service Pack 2 (SP2)
Issue that is fixed
When you install a hotfix or an update for any of the .NET Framework 2.0, .NET Framework 3.0, or .NET Framework 3.5 components on a computer that has the .NET Framework 3.5 Service Pack 1 (SP1) installed, the machine.config or web.config file may be corrupted. This problem occurs when a "configSource" attribute is used to redirect sections of the configuration file to an external configuration file.For example, you have a machine.config file or a web.config file that contains a redirected section such as the following:
<configuration>
<bindingExtensions configSource="other.config" />
</configuration>
After a .NET Framework update is installed, there are additional entries under the "bindingExtensions" element as in the following example:
<configuration>
<bindingExtensions configSource="other.config" />
<add name="name1" />
<add name="name2" />
</configuration>
This problem causes the configuration file to be invalid. The presence of the "configSource" attribute in the "bindingExtensions" element means that there should be no child elements under "bindingExtensions" in the configuration file. Additionally, when you run a Windows Communication Foundation (WCF) application on the computer, you receive a System.Configuration.ConfigurationException exception.
After this hotfix rollup is installed, future updates that are installed will be aware of the presence of the "configSource" attribute and refrain from changing these elements.
Workaround
To work around this issue, use one of the following methods:
- Manually remove the additional child elements as a workaround. But be aware that future updates may cause this issue to occur again if this hotfix rollup is not applied to the system.
- Move the configuration from the external configuration file back into the machine.config or web.config file.