Figured it out. It is actually because of the namespacing of the "Inherits"
value for Global.asxs, which remained the old namespace when I changed the
project's namespace before I add the setup project into the solution.
I thought this value could be changed automatically, but it didn't. That
causes the asp.net can not find its codebehind.
The indexing is another issue normally will cause the problem on both local
and production server. Anyway, thanks for Scott's comment. It is very nice
to see our project is running properly now.
Jim
"Scott Allen" <bitmask@[nospam].fred.net> wrote in message
news:tr********************************@4ax.com...
I've seen this happen when Index Server is running. Once the indexing
service was stopped there were no problems..
--
Scott
http://www.OdeToCode.com
On Sun, 12 Sep 2004 22:49:57 -0400, "Jim" <NA@NA.COM> wrote:
Hi, I hv got a problem for one of my asp.net web application. When I am
trying to use a web set up project to install my application on iis
server,
there always an error on Global.asxs for "Type can not be load.". I am
very
sure my project is compiled properly. And I can run the application on
both
local and production machine with a virtual directory point to my project
folder on iis. Any solutions for this problems will be very appreciated,
thanks!
