Re: .net web.config file

Tech-Archive recommends: Speed Up your PC by fixing your registry

From: Steve Spicer (SteveSpicer_at_discussions.microsoft.com)
Date: 11/08/04 

Date: Mon, 8 Nov 2004 03:49:04 -0800

No, maybe this is the wrong place to ask this. The aspx file runs. It is a
net application as defined in IIS6. I've changed the machine.config file on
the server to customErrors mode = "Off" and added that line in the web's
web.config file. It will not run with a web.config file in the folder. The
page will run with it not in the folder.

"Chris Leeds, MVP-FrontPage" wrote:

> last time I messed with .net stuff I remember having to get the server
> admins to set the particular folder as a .net web application.
>
> it seems to have the web.config and or .dll files running on the site it
> needs to be marked "server side" to allow it to run.
>
> HTH
>
> --
> Chris Leeds,
> Microsoft MVP-FrontPage
>
> Make More Money with Less Work
> Let Your Clients Control Their Content With Just A Browser!
> http://contentseed.com/
> --
> "Steve Spicer" <SteveSpicer@discussions.microsoft.com> wrote in message
> news:F6A55A60-8D80-4597-88D8-3D518F341304@microsoft.com...
> > I can easily run a little test .net page in a Win2003 Server, but as soon
> as
> > I create a web.config file in FP the test page, nor any other .aspx file,
> > will not run. Even if there is nothing in the file. I've got a database
> app
> > that runs fine that I want to move over to the Win2003 server and I need
> the
> > web.config file. The error I get is about custom errors. I'm using FP2000
> at
> > home to connect to the 2003 server at work. The error page is a Runtime
> Error:
> >
> > >>>
> > Description: An application error occurred on the server. The current
> custom
> > error settings for this application prevent the details of the application
> > error from being viewed remotely (for security reasons). It could,
> however,
> > be viewed by browsers running on the local server machine.
> >
> > Details: To enable the details of this specific error message to be
> viewable
> > on remote machines, please create a <customErrors> tag within a
> "web.config"
> > configuration file located in the root directory of the current web
> > application. This <customErrors> tag should then have its "mode" attribute
> > set to "Off".
> >
> >
> > <!-- Web.Config Configuration File -->
> >
> > <configuration>
> > <system.web>
> > <customErrors mode="Off"/>
> > </system.web>
> > </configuration>
> >
> >
> > Notes: The current error page you are seeing can be replaced by a custom
> > error page by modifying the "defaultRedirect" attribute of the
> application's
> > <customErrors> configuration tag to point to a custom error page URL.
> >
> >
> > <!-- Web.Config Configuration File -->
> >
> > <configuration>
> > <system.web>
> > <customErrors mode="RemoteOnly"
> defaultRedirect="mycustompage.htm"/>
> > </system.web>
> > </configuration>
> > <<
>
>
>

Quantcast