parser error: Could not load type ???.Global in globall.asax line 1

  • Thread starter Thread starter Tyson Zwicker
  • Start date Start date
T

Tyson Zwicker

Hi,

I'm suddenly unable to run any ASP.net applications. Last week everything
worked. But now (Mondays!) I get the same error from _every_ application
I've written:

Parser Error

Description: An error occured during the parsing of a resource required to
service this request. Please review the following specific parse error
details and modify your source code appropriately.

Parser Error Message: Could not load type HTMLTableExtractor.Global

Source Error:

<% Application Codebehind = "Global.asax.cs"
Inherits="HTMLTableExtractor.Global" %>

This is what I have tried to date:

1. Erase Global.asax file and replace with a new one. (Didn't work).
2. Create a whole new empty project, and import old classes in one by one
(Didn't work).
3. Erase "bin" folder and rebuild application from scratch. (Didn't work).
4. Erase all files in
c:/winnt/system/microsoft.net/framework/v1.1.4322/Temporary ASP.NET Files.
and then rebuild (Didn't Work).
5. Restarted the ASP.NET thread. (Didn't work).
6. Restarted IIS. (Didn't work).
7. Moved everything to new virtual directory. (Didn't work).
8. Restarted the computer a dozen times..

Now, I can deploy these applications to another server, and they run, on the
other server. Just not on my computer. On my computer they don't run from
IE. Visual studio does not appear to be the problem.

I'm about ready to use the one solution I do know: FORMAT C: :)

Any suggestions? Can I remove IIS and reinstall it without screwing up
Visual Studio and having to reinstall everything?

Thanks,

Tyson
 
I did everything you did and ran into the same issue.

Here was how I was able to work around it.

Inside of the Global.asax.vb wrap the Global class inside of the same namespace your project is in:

NameSpace Group.NameSpace
Public Class Global
------
End Class
End NameSpace

Then Build the app, view in browser and it worked for me.

I was then able to remove the namespace and everything still worked fine.


Good Luck,
Chad
 
Back
Top