A list of the bugs that are fixed in the .NET Framework 1.0 Service Pack 3 and that are not described elsewhere in individual Microsoft Knowledge Base articles (888527)

MORE INFORMATION

Undocumented bugs in ASP.NET

• Impersonation in ASP.NET may be unsuccessful in Microsoft Integrated Information Server (IIS) 5.0 isolation mode.
  
  When you run an ASP.NET Web Application project on a computer that is running Microsoft Windows Server 2003 with the .NET Framework 1.0 installed, you may receive an error message that is similar to the following:
  System.Web.HttpException: Access denied to 'd:\inetpub\wwwroot\ImpersonateTest\WebForm1.aspx'. Failed to start monitoring file changes.
  This problem occurs when IIS 6.0 is running in IIS 5.0 isolation mode. You have to grant the "SeImpersonatePrivilege" permission to the ASPNET account.
  
  To grant the "SeImpersonatePrivilege" permission to the ASPNET account, follow these steps:
  1. Click Start, point to Settings, and then click Control Panel.
  2. Double-click Administrative Tools.
  3. Double-click Local Security Policy.
  4. Under Local Policies, click User Rights Assignment.
  5. In the Details pane, double-click Impersonate a client after authentication.
  6. Click Add, and then assign the permission to the local account that is named ASPNET.
  7. Start a command prompt, and then type iisreset.
• You experience scripting errors when you visit a Web site that uses the ASP.NET SmartNav feature in Microsoft Internet Explorer 5.5.
  
  This problem may occur if either of the following conditions is true:
  • You apply the MS03-048 security update to Internet Explorer 5.5.
  • You apply a software update that contains the MS03-048 security update to Internet Explorer 5.5.
  This problem occurs because the MS03-048 security update prevents the SmartNav feature from working correctly in Internet Explorer 5.5.
  
  
• New default behavior encodes a new line character that is named "\n" in response headers and in configuration options.
  
  To help protect from "HTTP Response Splitting" attacks, the default behavior encodes the "\n" new line character when the "\n" new line character is found in the header body.
  
  To work around the default behavior, you must set the EnableHeaderChecking attribute to "false" in the <httpRuntime> element. The <httpRuntime> element is used to configure the ASP.NET HTTP runtime settings. The following code example shows you how to set the EnableHeaderChecking attribute to "false." The following code example also shows you how not to encode the "\n" new line character.

  <httpRuntime EnableHeaderChecking=false ...\>

• You have to log on after you install the .NET Framework on Microsoft Windows XP Home Edition.
  
  Warning Serious problems might occur if you modify the registry incorrectly by using Registry Editor or by using another method. These problems might require that you reinstall your operating system. Microsoft cannot guarantee that these problems can be solved. Modify the registry at your own risk.
  
  When you install the .NET Framework on Windows XP Home Edition, the log on screen appears. However, you expect to continue directly to the desktop after you start your computer.
  
  To resolve this problem, add the DWORD registry entry that is named ASPNET with a value of 0 (zero) to the following registry key when you install the .NET Framework:
  
  HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon\SpecialAccounts\UserList
  
  Note This registry entry indicates that the ASPNET account is a service account.
  
  
• ASP.NET State Service does not start after you install the .NET Framework 1.0.
  
  When you install the .NET Framework 1.0 on a system that has the .NET Framework 1.1 installed, the ASP.NET State Service does not start after the installation.
  
  This problem occurs because the ASPNET account is re-created when you install the .NET Framework 1.0.
  
  To work around this problem, correct the ASPNET account password. To do this, follow these steps:
  1. Click Start, click Run, type cmd, and then click OK.
  2. At the command prompt, type the following directory path:
     
     %WindowsDirectory% \Microsoft.NET\Framework\v1.1.4322\
  3. Type the following command to correct the ASPNET account password:
     
     aspnet_regiis -ir

Undocumented bugs in the .NET Framework class library

• When you try to create the CultureInfo class that is based on an ELK locale, you may receive the following error message:
  Culture <someLCID> is not a supported culture.
  Note The placeholder <someLCID> is the language identifier.
  
  When you try to create an instance of the CultureInfo class that is based on an ELK locale, you receive an error message that is similar to the following:
  Culture <someLCID> is not a supported culture.
  The problem occurs when you try to create an instance of the CultureInfo class for a locale that is not supported by the .NET Framework.
  
  The following new fallback behavior has been added to reduce errors that are returned when a culture is not supported by the CultureInfo class.
  • GetUserDefaultLCID
    
    Create CultureInfo that is based on current user locale.
  • GetSystemDefaultLCID
    
    Create CultureInfo that is based on the system default.
  • GetSystemDefaultUILanguage
    
    Create CultureInfo that is based on the system installed languages.
  • Create CultureInfo that is based on Invariant culture.
  Note If the culture is not supported by the operating system, you may receive the following error message:
  Culture <someLCID> is not a supported culture.
• National Language Support (NLS) data contains an incorrect name for Serbia.
  
  The name for Serbia has been changed to Serbia and Montenegro.

Undocumented bugs in the .NET Class Library (NCL)

• The "ServerProtocolViolationException" Web exception occurs when you call the HttpWebRequestGetResponse method.
  
  To help protect from "HTTP Response Splitting" attacks, parsing is performed according to the document that is named Request for Comments (RFC) 2616. This means that all control characters are not permitted in names or in values. For example, the carriage return (CR) character and the linefeed (LF) character are not permitted. There are other characters that are not permitted in names. Additionally, every response header must have a colon.
  
  To work around this new behavior, you must add the useUnsafeHeaderParsing attribute of the <httpWebRequest> element in the Machine.config file. The following is a code example that shows you how to set the useUnsafeHeaderParsing attribute to "true."

  <system.net>
  	<settings>
  		<httpWebRequest
  			useUnsafeHeaderParsing = "true"
  		/>
  	</settings>
  </system.net>
  

Undocumented bugs in Universal Runtime (URT) integration

• The Active Directory directory service administrative deployment is not supported for the .NET Framework 1.0 Service Pack 3. When you create a deployment image of the .NET Framework 1.0 Service Pack 3, the installation of the image is unsuccessful.
  
  
• When you install the .NET Framework 1.0 Service Pack 3, and then you uninstall the .NET Framework 1.0 Service Pack 3, random files are left in the global assembly cache (GAC) in Microsoft Windows Millennium Edition.
  
  
• The .NET Framework must be repaired after you upgrade the operating system.
  
  When you upgrade the operating system, the .NET Framework must be repaired before you apply the .NET Framework 1.0 Service Pack 3.
  
  For example, you must repair the .NET Framework 1.0 when you upgrade from Windows Millennium Edition to Windows XP. After you upgrade to Windows XP, you have to perform a repair on the existing .NET Framework 1.0 before you apply the .NET Framework 1.0 Service Pack 3. To repair the .NET Framework 1.0, follow these steps:
  1. Click Start, and then click Control Panel.
  2. Double-click Add or Remove Programs.
  3. Click Microsoft .NET Framework SDK, and then click Click here for support information.