ITsVISTA
Information that makes life easier when it comes to installing, managing, and using Windows Vista.
Start About FAQ Blogroll Shop

All tag results for ‘ASP’

KB944141

March 17th, 2008 · No Comments · 213 views

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.

KB934839

January 10th, 2008 · No Comments · 208 views

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

KB931338

January 10th, 2008 · No Comments · 140 views

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.

KB936344

January 1st, 2008 · No Comments · 110 views

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.