In my default application I have the web.config file however I want to modify the custom errors section whereby if i am working in the development server then the custom errors will NOT be redirected to my custom page and if I am not in the development server then yes go ahead and redirect my user to the custom error page. I thought by using the KEYS in my configuration settings within my web.config file I could add that as an attribute to my custom errors element but I found out it does not work that way.

Here is my web.config setting in the custom errors element:

<customErrors mode="On" defaultRedirect="/errorhandle/errorhandle.aspx"/>

I had tried using this but it failed:

<customErrors environment="prod" mode="On" defaultRedirect="/errorhandle/errorhandle.aspx"/>

environment was one of the keys I have currently in my configuration settings/add appkeys element.

Coming from an VBScript background I could just wrap this statement in an IF ELSE STATEMENT but I can't seem to do that in this environment.

Any suggestions or direction on how I can do this would be appreciated.

Thanks.

I don't think you can do this.

The schema for the Web.Config is pretty much defined inside the .NET runtime. (Except for the keys you can add to the AppSettings section)

The only thing I can think of is disable the custom errors functionality and implement your own in Application_Error() but that kind of defeats the purpose.... ;)

Imar

Of course, you could also just set <customErrors mode="RemoteOnly" ...>

This way you'll see errors when working on development (http://localhost) but not otherwise.

-Peter

Thanks for the feedback guys. I did have code in the GLOBAL.asax file in each of the IIS application I have on this one solution in VS but really just wanted one place to control the settings for all our .aspx pages. We just decided to turn on and off depending on the environment.

I appreciate your time and feedback.