Re: web.config ignored!?!?!

Jonny,

could you try, instead of using :

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

editing that line to just :

<configuration>

If that's the only mistake, that will eliminate the error message.

I know that you're looking for a fuller solution,
but that might enable you to continue working on the app.





Juan T. Llibre, asp.net MVP
asp.net faq : http://asp.net.do/faq/
foros de asp.net, en español : http://asp.net.do/foros/
===================================
"Jonny Bergdahl" <jonny.bergdahl@xxxxxxxxxxxxxxxx> wrote in message
news:F0E998D3-2EEE-4A81-9196-0B252C1CDC5C@xxxxxxxxxxxxxxxx
To be able to see that error message, you need to set <compilation debug="true">.

Besides from using the <compilation> tag for compilation, ASP.NET uses that flag to change certain
runtime behaviour. One of those is how it handles resources returned to the browser, such as
images and style sheets. When debug is set to true, it telles the browser never to cache the
content, effectively making our application too slow to be usable. This is the reason the debug
flag always should be set to false in a production server.

The debug flag does not, however, make ASP.NET ignore the settings for <customErrors> or <trace>,
which you easily can verify by yourself.

If you wish to ignore reality I can't help you, nor can anybody else.

Seems your reality differs wastly from mine, as I have successfully used both the <customErrors>
and <trace> settings to get the needed output on our production servers, where we always have
debug set to false.

The issue I am having is with our staging server - any web sites created there ignores these
settings. We have four separate web sites on the server, all with different IP addresses. I have
also mapped Localhost to one of them, but browsing to http://localhost/trace.axd also displays the
"Trace error" message instructing me to do what I have already done, set tracing to on.

Regards;
/jb


.