Introduction

This article describes hotfix rollup 2803756 that is available for the Microsoft .NET Framework 2.0 Service Pack 2 (SP2). This hotfix rollup is available to fix several issues in the .NET Framework 2.0 SP2. For more information about the issues that the hotfix resolves, see the "More information" section.

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=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.

Prerequisites

To apply this hotfix, you must have the Microsoft .NET Framework 2.0 SP2 installed.

Restart requirement

You must restart the computer after you apply this hotfix if any affected files are being used. We recommend that you close all .NET Framework-based applications before you apply this hotfix.

Hotfix replacement information

This hotfix package does not replace a previously released hotfix package.

The global 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.

For all supported x86-based versions of the .NET Framework 2.0 SP2 in Windows 8

File name

File version

File size

Date

Time

System.security.dll

2.0.50727.7017

258,048

22-Jan-2013

23:06

Mscorlib.dll

2.0.50727.7017

4,550,656

22-Jan-2013

23:06

Mscordacwks.dll

2.0.50727.7017

990,280

22-Jan-2013

23:06

Mscorwks.dll

2.0.50727.7017

5,936,688

22-Jan-2013

23:06

Sos.dll

2.0.50727.7017

389,688

22-Jan-2013

23:06

For all supported x64-based versions of the .NET Framework 2.0 SP2 in Windows 8 and Windows Server 2012

File name

File version

File size

Date

Time

Mscorlib.dll

2.0.50727.7017

4,567,040

22-Jan-2013

23:06

Mscordacwks.dll

2.0.50727.7017

1,756,728

22-Jan-2013

23:06

Mscorwks.dll

2.0.50727.7017

10,002,480

22-Jan-2013

23:06

Sos.dll

2.0.50727.7017

485,944

22-Jan-2013

23:06

System.security.dll

2.0.50727.7017

258,048

22-Jan-2013

23:06

System.security.dll

2.0.50727.7017

258,048

22-Jan-2013

23:06

Mscorlib.dll

2.0.50727.7017

4,550,656

22-Jan-2013

23:06

Mscordacwks.dll

2.0.50727.7017

990,280

22-Jan-2013

23:06

Mscorwks.dll

2.0.50727.7017

5,936,688

22-Jan-2013

23:06

Sos.dll

2.0.50727.7017

389,688

22-Jan-2013

23:06


Issues that this hotfix rollup resolves

Common language runtime (CLR) issues

Issue 1

Assume that you run a .NET Framework 2.0 SP2-based or a Microsoft .NET Framework 3.5 Service Pack 1 (SP1)-based Microsoft Office Automation application on a non-English language operating system. In this situation, the application crashes with an exception.

For example, you run an application that contains the following code:


Imports Microsoft.Office.Interop
Imports Microsoft.Office.Core

Dim oApp As New Excel.Application()
oApp.Visible = True
oApp.UserControl = True
Dim oBooks As Object = oApp.Workbooks
oBooks.GetType().InvokeMember("Add", Reflection.BindingFlags.InvokeMethod, Nothing, oBooks) Note The .NET Framework 3.5 SP1 includes the .NET Framework 2.0 SP2.

Issue 2

Assume that you have a .NET Framework 2.0 SP2-based or a .NET Framework 3.5 SP1-based application is signed with a signature that uses a certificate. The serial number of the certificate is 00. In this situation, a System.Security.Cryptography.CryptographicException exception occurs when the application verifies the signature. Additionally, the application cannot start.


Need more help?

Expand your skills
Explore Training
Get new features first
Join Microsoft Insiders

Was this information helpful?

What affected your experience?

Thank you for your feedback!

×