Thanks for the response.
Too bad the schema is not public. It would be nice to have. You could
validate the XML in Visual Studio in stead of when ASP.NET parses it. I am
not impressed with the errors ASP.NET returns. I have one occasion where the
error report was the web.config file needed either:
<customErrors mode="RemoteOnly">
<error statusCode="nnn" redirect="Errornnn.htm" />
</customErrors>
or
<<customErrors mode="Off" />
The customeErrors element was in the file, in its normal generated location,
but the cause of the error was above it. Validating the file would have found
the problem before running the ASP.NET application.
I suggest the schema be made public so Visual Studio can be used to validate
the web.config before running the ASP.NET application. With the enterprise
framework for the web.config file I would thought one would be available.
--
Jim
"Wei-Dong XU [MSFT]" wrote:
> Hi Jim,
>
> Yes, there is one schema for web.config. However, it is not public. This is
> mostly because ASP.net runtime will parse the web.config at the first
> access of the web application. ASP.net will parse it for you and if it is
> invalid, ASP.net will return error immediately. So there is no one schema
> available.
>
> Please feel free to let me know if you have any further question on this
> matter.
>
> Best Regards,
> Wei-Dong XU
> Microsoft Product Support Services
> This posting is provided "AS IS" with no warranties, and confers no rights.
> It is my pleasure to be of assistance.
>
> >> Stay informed about: Is there an XML Schema for the web.config file