Oh you didn't say this was a conversion.

You need to move the code behind class from global.asax into APP_CODE and make sure that the global.asax file references the full type (remove the SourceFile or Codebehind attribute) declared there (MyNamespace.MyGlobalType).

If you converted this project using the VS.NET upgrade wizard it should have taken care fo this for you.

+++ Rick ---


>The search on that topic is widely used across the Internet. And, it is also caused by various scenarios. This is why it is extremely difficult to find. Some have this situation when they deploy others at design time. I have it at design time. Some others have it when the global.asax are not in the bin directory and vice versa. Some resolved the issue by changing the name of the global.asax global class name. Some resolved it by recreating the application directory of the IIS directory. Some resolved it by resinstalling VS 2005 and so on. And, for me, I was not able to resolve it up to this point. Basically, none of my ASP.NET was being able to run after the conversion. I was able to convert the Web Services and the desktop applications. But, the ASP.NET ones I have were a no go.
>
>>The error usually means that there's an error in the Global.asax codebehind class that causes the class not to compile or not be found (same thing if it didn't compile it's not there). I've seen this after a compile, but never just after a site is already up and running. If global is not loading the app simply won't run.
>
>That is also another issue. I can't get the compile version because I have it at design time. I also recreated two new projects for a test and wasn't even able to have them ok at design time.