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.

In a Microsoft .NET Framework 2.0-based application, you try to use the System.Transactions.CommittableTransaction.Commit method to commit a transaction. However, the call to the System.Transactions.CommittableTransaction.Commit method may always be blocked.

When you use a try-catch block to handle an exception from multi-threads in the Microsoft .NET Framework 2.0, the exception is not handled correctly. This problem occurs even after you use the try-catch block to implement an appropriate exception handler.

In the Microsoft .NET Framework 2.0, the XML serialization may lose some optional elements in an XSD schema.

Consider the following scenario:

• In Microsoft Visual Studio 2005, you create multiple pages in different folders in an ASP.NET-connected application.
• These pages use the same name.
• You set a breakpoint in one of these pages.

In this scenario, a significant delay may occur when you try to debug the ASP.NET-connected application. Additionally, this delay may cause a time-out error. In this case, you receive the following error message:

Unable to start debugging on the web server. The operation has timeout.

On a Windows Vista-based computer, you try to view the list of computers and of shared resources on the network by using one of the following methods:

• Run the NET VIEW command to show the list of the computers and the shared resources.
• View the computers and the shared resources in Windows Explorer.

However, you cannot obtain the list of computers and of shared resources.

For example, you run the NET VIEW command to view the network resources. Then, you receive following error message:

An internal Windows error occurred.
More help is available by typing NET HELPMSG 2140.

This problem occurs if the network has lots of computers in the browse list.

Consider the following scenario:

• You create a managed service that uses the Microsoft .NET Framework 2.0.
• You run the managed service on a computer that is running the .NET Framework 2.0.

In this scenario, the managed service is not stopped in a timely manner on the computer when the operating system shuts down. Therefore, you may experience delays when the operating system shuts down.

Consider the following scenario. You install the MS07-040 security update. Then, you run a Microsoft ASP.NET 2.0 Web application that is built on the Microsoft .NET Framework 2.0. In this scenario, you may receive an exception error message that resembles the following:

Event Type: Warning
Event Source: ASP.NET 2.0.50727.0
Event Category: Web Event
Event ID: 1309
Date: 12/07/2007
Time: 10:24:38
User: N/A
Computer:
Description:
Event code: 3005
Event message: An unhandled exception has occurred.
Event time: 12/07/2007 10:24:38
Event time (UTC): 12/07/2007 8:24:38
Event ID: aa58f4d35bc547aeafd7c417967bdd8d
Event sequence: 8
Event occurrence: 1
Event detail code: 0

Application information:
Application domain: /LM/W3SVC/1/Root/ApplicationDomain
Trust level: Full
Application Virtual Path: /Path
Application Path: D:\ApplicationPath
Machine name: ComputerName

Process information:
Process ID: ProcessID
Process name: w3wp.exe
Account name: NT AUTHORITY\NETWORK SERVICE

Exception information:
Exception type: EndPointException
Exception message: Type ‘System.Web.HttpHeaderCollection’ in Assembly ‘System.Web, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a’ is not marked as serializable.

Note: This problem also occurs in the .NET Framework 2.0 for Windows Vista.

The information in this article applies to the following configuration(s):

• Catalyst Control Center
• Radeonâ„¢ X800 series
• Windows Vista 32-bit Edition
• Windows Vista 64-bit Edition
• Windows XP Professional
• Windows XP Home Edition
• Windows XP Media Center Edition
• Windows XP Professional x64 Edition

Symptoms:
A Microsoft .NET Framework error may appear when switching between user accounts and or toggling between Catalyst Control Center skins

When you back up and then restore Windows Vista, the Microsoft .NET Framework is not restored correctly.