first aspx file live

[thersitz]

hi,

I have some rented web space -- it is suppose to have asp.net 2.0 loaded.

I can drop a default.aspx file in the directory and it will load. Currently
in that file i have only basic html -- no asp.net code.

If I drop a web.config file in the root directory, I then cannot get the
file to load, instead get the default error page -- which tells me if I want
to see the problem, I need to add <customErrors mode="Off"/> to the
web.config file -- which I have done -- but it still shows the same default
error page and does not recognize the <customErrors mode="Off"/> line. Below
is the basic config file I am using. Can anyone give me an idea of what I am
doing wrong. thanks

<configuration xmlns="http://schemas.microsoft.com/.NetConfiguration/v2.0">

<appSettings />

<connectionStrings />

<system.web>

<compilation defaultLanguage="vb" debug="false" />



<authentication mode="None" />



<customErrors mode="Off" />

</system.web>

</configuration>

 

[thersitz]

I can view the aspx pages just fine on my local machine using VS 2005's web
server -- even files with aspx controls.

thanks

 

[Juan T. Llibre]

re:

If I drop a web.config file in the root directory, I then cannot get the file to load, instead get
the default error page

What happens if you change :
<configuration xmlns="http://schemas.microsoft.com/.NetConfiguration/v2.0">

to:
<configuration>

?

 

[thersitz]

Thanks for the suggestion, Juan. But that did not change the problem. It
doesn't even seem to recognize the <customErrors mode="Off" /> declaration
in the web.config -- but it certainly recognizes the web.config being
there -- because when it is there, the pages err -- but when I remove it,
they display. And again I have no problems viewing on my local machine.

thanks

 

[RBarrand]

check with your provider if they have a web.config in the root (wwwroot)
I imagine your web.config is in the root of your personal folder

 

[thersitz]

Thanks.

I have been ftping my copy of the web.config into the root on the provider's
server. I have been on the phone with them, and the problem could be on
their end -- they are looking into it -- so hopefully this is resolved.