Page 2 - Parser Error Message: Could not load type

ASP Free Forums Sponsor:

#16

May 6th, 2004, 09:14 PM

cymonp

Registered User

Join Date: May 2004

Posts: 2

Time spent in forums: < 1 sec
Reputation Power: 0

Parser Error - WORKS!!! Try this. Thanks to saghari.

Quote:

Originally Posted by saghari

Hi
Oh, I had this problem for new web forms added to solution, but after a short navigating in VS menu I found the solution --> Ctrl +Shift +B you should "rebuild solution" from "Build" menu.

Regards

Keep up the good work!

Take Care,
Cymon

#17

May 6th, 2004, 09:17 PM

cymonp

Registered User

Join Date: May 2004

Posts: 2

Time spent in forums: < 1 sec
Reputation Power: 0

I have try the Crtl+Shift+B then Recompile/Rebuild the solution. For so many times I've ask and seek for the answer. THIS MADE ME HAPPY. IT WORKS. I recommend it.

#18

May 14th, 2004, 03:39 PM

Anubi

Registered User

Join Date: May 2004

Posts: 1

Time spent in forums: < 1 sec
Reputation Power: 0

Please... this is frustrating

Hello everyone,

I tried everything above, but I still can't solve it.

Code:
<%@ Page language="c#" Codebehind="WebForm1.aspx.cs" AutoEventWireup="false" Inherits="TestTreeView.WebForm1" %>

Error:

Server Error in '/TestTreeView' 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 type 'TestTreeView.WebForm1'.

Source Error:

Line 1: <%@ Import NameSpace="Microsoft.Web.UI.WebControls"%>Line 2: <%@ Register TagPrefix="iewc" Namespace="Microsoft.Web.UI.WebControls" Assembly="Microsoft.Web.UI.WebControls, Version=1.0.2.226, Culture=neutral, PublicKeyToken=31bf3856ad364e35" %>Line 3: <%@ Page language="c#" Codebehind="WebForm1.aspx.cs" AutoEventWireup="false" Inherits="TestTreeView.WebForm1" %>Line 4: <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN" >Line 5: <HTML>
Source File: c:\inetpub\wwwroot\TestTreeView\WebForm1.aspx Line: 3

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

Can someone come up with another solution?

Oh, and before I got this error, I got a not that I had to delete <add assembly="*"/>
from the machine.config file.
Maybe that has something to do with it?

Greets and thx to all on advance.

#19

May 27th, 2004, 08:37 PM

lanzdale

Registered User

Join Date: May 2004

Posts: 1

Time spent in forums: < 1 sec
Reputation Power: 0

The dll bin folder is relative to IIS

If you're sure you've got the new version complied and in the bin folder,
( try ildasm on it to be sure names are correct, I made
a shortcut in my SendTo folder) , check one other important thing.

The bin folder is an IIS Virtual folder, not just a Windows folder.
I fixed a similiar problem by copying that whole application to a temp
location, then in IIS MMC, Delete the virtual folder.
(It deletes the real folder too, that's why you copy 1st.) , then
copy back and in IIS MMC again New / Virtual Directory, give same name,
point to it.

(Also be sure to record/remake any IIS directory properties like certificates.)

Don't ask me why there's nothing of this on the Microsoft site (or
why it's so hidden). It's so obvious an error.

#20

June 10th, 2004, 03:00 AM

KarlXII

Registered User

Join Date: Jun 2004

Location: Stockholm

Posts: 1

Time spent in forums: < 1 sec
Reputation Power: 0

Hi everyone !

I had this problem also and most of the given solutions didn´t work for me, until I actually found out that I had to edit the row
"Inherits="WSUtbImport.Global" %>"
to add the prefix of my actual project name like:
"Inherits="xxx.xxx.xxx.WSUtbImport.Global" %>"

Then after rebuilding solution it worked just fine. Thank you to Manos to lead me in the correct direction for this one.

#21

November 14th, 2004, 08:25 PM

Brazenheart

Registered User

Join Date: Nov 2004

Posts: 1

Time spent in forums: < 1 sec
Reputation Power: 0

I had this same problem but for yet a different reason. I was converting an ASP.Net Visual Studio project to a command line build. I setup a batch file to run vbc and construct the assembly. The library compiled fine, but when I ran it, I would get the "could not load type" error on every page.

After a variety of efforts, I decided to load up the dll in a disassembler and compare it to the dll I had created under Visual Studio. It turns out that all the pages reference as their classes something like the following: <Namespace of project>.<Codebehind class> (e.g. project1.index), but in the disassembler I could see that the namespace was "-", so even though all the classes were there, the pages weren't looking for the right namespace. I added the command line argument "/rootnamespace:<namespace of my project>" and the problem was solved.

I don't know how many of you compile asp.net libraries from the command line, but this might help give you an idea of the nature of the "could not load type" error.

#22

December 2nd, 2004, 11:11 AM

vongthep

Registered User

Join Date: Feb 2004

Posts: 11

Time spent in forums: 1 h 26 m 55 sec
Reputation Power: 0

Using VB.NET and getting error?

Quote:

Originally Posted by tulsatoldwing

I have seen this error reported numerous times in different forums, but haven't found the solution to my particular problem yet. I have created a few sample ASP.net apps, from a book I am studying, and haven't had any trouble compiling and running my apps, until recently. Now I get the following error when I create a new ASP.NET Web Application (VB.net) in VS.net, and "Start" the 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 type 'WebApplication2.Global'.

Source Error:

Line 1: <%@ Application Codebehind="Global.asax.vb" Inherits="WebApplication2.Global" %>

Source File: c:\inetpub\wwwroot\WebApplication2\global.asax Line: 1
---------------------------------------------------------------

It doesn't matter whether I add web controls to the form or not. I haven't knowingly changed anything about my environment since I was previously able to compile and run ASP.NET apps. And I'm not changing any of the default code that is generated by VS.NET before I attempt to start the application.

The suggestion solution to this error usually contains a warning that the application has not been built or is not located in the bin subdirectly of the virtual directory. But my app IS being built (WebApplication2.dll) and IS located in the bin subdirectly of my virtual directory.

I would appreciate any suggestions.

Check this link out. Worked for me

http://support.microsoft.com/defaul...kb;en-us;312311

Last edited by Shadow Wizard : January 5th, 2005 at 11:11 AM.

#23

December 29th, 2004, 05:06 AM

rytterqvist

Registered User

Join Date: Dec 2004

Posts: 1

Time spent in forums: < 1 sec
Reputation Power: 0

Iis

The following solved the problem for me (running the VB.NET project locally):

Go to folder
C:\Inetpub\wwwroot

Rename the folder where your solution is PROJECT.OLD

In IIS, right click on Standard Web, New, Create a new Virtual Catalog.

Create a new Virtual Catalog named as your old solution PROJECT

Go to folder
C:\Inetpub\wwwroot

Copy the files from PROJECT.OLD to PROJECT

Thats all!

#24

January 4th, 2005, 10:42 PM

m_corby

Registered User

Join Date: Jan 2005

Posts: 1

Time spent in forums: < 1 sec
Reputation Power: 0

My problem was resolved when I replaced the machine.config.

In the end I narrowed it down to the below line in the ProcessModelAttributes section.

Username = 'SYSTEM'

instead of Username = '[user]'

#25

January 5th, 2005, 11:16 AM

Shadow Wizard

Moderator From Beyond

ASP Free God 48th Plane (28500 - 28999 posts)

Join Date: Sep 2004

Location: Israel

Posts: 28,836

Folding Points: 544103 Folding Title: Super Ultimate Folder - Level 2

Time spent in forums: 3 Months 2 Weeks 1 Day 13 h 54 m 20 sec
Reputation Power: 2389

enough said in this thread... time to close it - more than enough possible solutions. if anyone wants to share another solution send me message.

Last edited by Shadow Wizard : January 5th, 2005 at 11:20 AM.

#26

January 12th, 2005, 03:34 AM

Shadow Wizard

Moderator From Beyond

Join Date: Sep 2004

Location: Israel

Posts: 28,836

Time spent in forums: 3 Months 2 Weeks 1 Day 13 h 54 m 20 sec
Reputation Power: 2389

--suggested solution by slymonkey:

The cause for this error is that the name in the Inherits statement of the html, i.e.

Code:

Inherits="<projectname>.<something>"

does not match the name of the public class it is looking for. If you view the code for the page that is causing the error the name in the inherits section and the name of the Public Class (right at the top of your code) won't be the same. What is needed is to name them both the same, doesn't matter what you name them. You could name the Public Class as follows

Code:

Public Class IhaveCheekyMonkeysInMyPants
 End Class

As long as the inherits statement in the html matches as follows

Code:

Inherits="<projectname>.IhaveCheekyMonkeysInMyPants"

you are good to go.

Thread Tools	Search this Thread
Email this Page	Search this Thread: Advanced Search
Display Modes	Rate This Thread
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode	Rate This Thread: