By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
432,045 Members | 2,120 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 432,045 IT Pros & Developers. It's quick & easy.

Could not load type

P: n/a

Hi,

I have built an application using ASP.NET. I can compile and run this
application fine on a development machine, and on another development
machine.

I tried to then run the same application on yet another development machine
(were trying to get a new revision control system up and running on this
project) but the application always reports 'Could not load type' when we
try and run a page.

The problem can be solved by modifying the codebehind and re-building, but
that would take a very long time!. Why does this happen?

I've read about Windows XP caching files at compile time, could this be
something to do with it? I know for sure that there is absolutely nothing
wrong with the code, and I'll be damned if anyone can prove otherwise - it
works fine... if I add a single comment char to the codebehind!

Below is the output that I get when I run the application for the first time
on a new development machine (the 'default' page).

Can anyone shed any light on this - it's most frustrating!

Neil Ramsbottom
Server Error in '/Capture' 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
'Cencion.Disney2003.Capture.Global'.

Source Error:
Line 1: <%@ Application Codebehind="Global.asax.vb"
Inherits="Cencion.Disney2003.Capture.Global" %>

Source File:
N:\Development\Projects\Cencion\Disney\Disney2003\ Capture\global.asax
Line: 1
----------------------------------------------------------------------------
----
Version Information: Microsoft .NET Framework Version:1.1.4322.573; ASP.NET
Version:1.1.4322.573
Nov 17 '05 #1
Share this Question
Share on Google+
4 Replies


P: n/a

I'm at the end of my tether with this.We are trying to develop a large
application, but we are constantly having to spend time rebuilding
individual files because of this damn stupid bug. If time were not a factor,
we would be switching this project to Java.

In light of the apparent lack of assistance that Microsoft appear to want to
give regarding this, I will be considering Java over .NET for future
projects.

I'm not normally one to have a pop at Microsoft, but this really is taking
the p**s. The one KB article on it (that I could fine) is no help
whatsoever.
Neil Ramsbottom
"Neil Ramsbottom" <ne*************@cencion.net> wrote in message
news:eX**************@TK2MSFTNGP12.phx.gbl...

Hi,

I have built an application using ASP.NET. I can compile and run this
application fine on a development machine, and on another development
machine.

I tried to then run the same application on yet another development machine (were trying to get a new revision control system up and running on this
project) but the application always reports 'Could not load type' when we
try and run a page.

The problem can be solved by modifying the codebehind and re-building, but
that would take a very long time!. Why does this happen?

I've read about Windows XP caching files at compile time, could this be
something to do with it? I know for sure that there is absolutely nothing
wrong with the code, and I'll be damned if anyone can prove otherwise - it
works fine... if I add a single comment char to the codebehind!

Below is the output that I get when I run the application for the first time on a new development machine (the 'default' page).

Can anyone shed any light on this - it's most frustrating!

Neil Ramsbottom
Server Error in '/Capture' 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
'Cencion.Disney2003.Capture.Global'.

Source Error:
Line 1: <%@ Application Codebehind="Global.asax.vb"
Inherits="Cencion.Disney2003.Capture.Global" %>

Source File:
N:\Development\Projects\Cencion\Disney\Disney2003\ Capture\global.asax
Line: 1
-------------------------------------------------------------------------- -- ----
Version Information: Microsoft .NET Framework Version:1.1.4322.573; ASP.NET Version:1.1.4322.573

Nov 17 '05 #2

P: n/a
Neil hi,

I'm willing to help, if you want.

When you got this error if you create new file in the bin directory does
it stop the error message. Can you send me the code of the global class?
Until now every time that I saw that error it was related to the code.

Cheer up, I participate in very large and complex .net projects and
although there where problems we manage to solve them all.

If you want e-mail me to na***@dao2com.com.

Natty Gur, CTO
Dao2Com Ltd.
28th Baruch Hirsch st. Bnei-Brak
Israel , 51114

Phone Numbers:
Office: +972-(0)3-5786668
Fax: +972-(0)3-5703475
Mobile: +972-(0)58-888377

Know the overall picture
*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!
Nov 17 '05 #3

P: 1
Neil,
The problem is that the ASP.NET version for the web page in IIS properties
is not compatible with your application. If you use VS.NET 2003, then
ASP.NET framework needs to be 1.1 or above. For VS.NET 2005, ASP.NET
needs to be 2.0. So just make sure that your server machine has ASP.NET
2.0. If not, download from here
http://www.microsoft.com/downloads/details.aspx?FamilyID=0856EACB-4362-4B0D-8EDD-AAB15C5E04F5&displaylang=en
and set the ASP.NET version to 2.0 for your web page in IIS.
Hope that helps,
Bill
Jul 10 '06 #4

P: 1
bcheng,
You are right on the mark with your diagnosis. I had the same issue and after reading your post, I corrected the error.

I don't know why the conversion of my Web service project from 1.1 to 2.0 did not set this property correctly. It must be a "feature".

Thanks!
Jul 18 '06 #5

This discussion thread is closed

Replies have been disabled for this discussion.