Consider the following scenario. You upgrade from the Microsoft .NET Framework 3.0 to the .NET Framework 3.0 Service Pack 1. Then, you change the input language in a text box on the Microsoft Expression Design surface to an East Asian language. In this scenario, the language does not function correctly.

Note: This problem also occurs on computers that have the Microsoft .NET Framework 3.5 installed.

You have an application that is built on the Microsoft .NET Framework 2.0 and that is hosted on Internet Information Services (IIS) 7.0. The first time that you access a Microsoft ASP.NET page in the application, you receive an HTTP 400 error message. However, later requests succeed.

Consider the following scenario. An application that is built on the Microsoft .NET Framework 2.0 contains a Microsoft Windows Forms control. You set the ImeMode property of the control to a specific value that is not the NoControl value. The focus is on the control. Then, you perform one of the following operations:

• You move the focus to another window. Then, you move the focus back to the control.
• You minimize the window that contains the control. Then, you restore the window.

In this scenario, the value of the ImeMode property automatically changes to the Off value.

When you browse a Microsoft .NET Framework 2.0 ASP.NET Web application, you may receive one of the following exceptions:
Exception 1

Exception type: FileNotFoundException Exception message: Could not load file or assembly ‘App_Web_-e9dbmaj, Version=0.0.0.0, Culture=neutral, PublicKeyToken=null’ or one of its dependencies. The system cannot find the file specified.

Exception 2

Compiler Error Message: CS0006: Metadata file ‘C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET Files\cms.web\44e73607\b028acb3\App_global.asax.fakktchx.dll’ could not be found

The Windows Management Instrumentation (WMI) service stops responding on a computer that is running the Microsoft .NET Framework 2.0 and Microsoft System Center Configuration Manager 2007.

Microsoft has released security bulletin MS07-040. The security bulletin contains all the relevant information about the security update. This information includes file manifest information and deployment options. To view the complete security bulletin, visit one of the following Microsoft Web sites:

• Home users:
  

  ” title=”http://www.microsoft.com/technet/security/bulletin/ms07-040.mspx

” class=”autohyperlink” target=”_blank”>www.microsoft.com/technet/security/bulletin/ms07-040.mspx

When you try to add a WebReference object to a Web service in the Microsoft .NET Framework 2.0, files are created by the Web service discovery. The Web service discovery is handled by the DiscoveryClientProtocol class. By using the Web service discovery process, Web service clients, such as Microsoft Visual Studio 2005, learn that an XML Web service exists. Web service clients also learn where to find the XML Web service’s description document. The Web service clients then save the discovered documents to the disk by using the WriteAll method. For example, the discovered documents may be .xsd schema files or service descriptions. At the end of the process, the client deletes the files.

For security reasons or in other situations, you may want to change the location of these files in the temp folder. An update is available for the .NET Framework 2.0. This update lets you configure the location of the temp folder by using the application’s Machine.config file. You can configure the location of the temp folder by using code that resembles the following.

<system.xml.serialization>
    <xmlSerializer tempFilesLocation="<Full path of the temp folder>"/>
  </system.xml.serialization>

You have a computer that is running the Microsoft .NET Framework 2.0. When you use the Show method in a Microsoft Component Object Model (COM) client application to display a Windows form on the computer, the form may not work as expected. For example, you may experience one or more of the following symptoms:

• When you press the TAB key, the focus does not change from one control to another control.
• When you press ENTER on a command button that has the focus, the Click event of the command button does not occur.

You may experience other unexpected behavior for keystroke activities or for mouse activities.

When you start a Microsoft .NET Framework 2.0 managed application that has a Microsoft Authenticode signature, the .NET Framework 2.0 managed application takes longer than usual to start.

When assemblies are loaded for the first time in a Microsoft .NET Framework 2.0 ASP.NET Web application, you receive the following error message:

System.IO.FileNotFoundException
Could not load file or assembly ‘AssemblyName’ or one of its dependencies. The system cannot find the file specified.

You may receive this error message if the following conditions are true:

• The .NET Framework 2.0 ASP.NET Web application references one or more class library assemblies.
• You create DEVPATH environment variables so that these assemblies locate the version of the assemblies that you want to use.

This problem does not occur if you use Microsoft ASP.NET 1.1 to develop the application.