Publish Article

Parser Error Message: Could not load assembly. Make sure that is compiled before accessing the page

If you are hosting your ASP.Net web application on Windows 2003 and IIS6, you may run into this error message. Especially when you migrate from ASP.Net 1.1 to ASP.Net 2.0 or have mix of applications, some using .Net 1.1 and some using .Net 2.0. In the later case the probability of running into this error is very high. Your exception message will look something like following.

Server Error in '/' Application.
Parser Error
Description: An error occurred during the parsing of a resource
required to service this request. Please review the following specific
parse error details and modify your source file appropriately.

Parser Error Message: Could not load the assembly 'App_Web_qazv2bfa'.
Make sure that it is compiled before accessing the page.

Source Error:

Line 1:  <%@ page language="VB" autoeventwireup="false"
inherits="_Default, App_Web_qazv2bfa" %>
Line 2:
Line 3:  <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"

Version Information: Microsoft .NET Framework Version:1.1.4322.2300;
ASP.NET Version:1.1.4322.2300


On IIS6.0 you can create application pools and assign different web applications to different pools. And you can configure each pool differently. I will not discuss advantages of using Application Pools in this article. That will be discussion for another article. There is one important restriction that you have to keep in mind is that within one application all applications have to use same version of .Net framework. If you will have mixed applications in the pool, you are sure to run into the error described above. If you have applications that need to use different versions of ASP.Net, then create separate pools. Put all .Net 1.1 web applications in one pool and all .Net 2.0 applications in another pool.

Go Freelance
Home     About us     Contact us    Copyright    Privacy Policy    Return Policy    Advertisers
Copyright © Netomatix