BUG: ASP.NET runtime rejects configuration file as invalid (307506)
The information in this article applies to:
- Microsoft Windows Management Instrumentation in . NET
- Microsoft .NET Framework 1.1
- Microsoft .NET Framework 1.0
- Microsoft Visual Studio .NET (2003), Professional Edition
- Microsoft Visual Studio .NET (2002), Professional Edition
This article was previously published under Q307506 SYMPTOMS If a configuration file does not already contain a
<configSections> Extensible Markup Language (XML) element, and the first
instance of a configSection class is written to the configuration file by using the
configuration Windows Management Instrumentation (WMI) provider, the
<configSections> XML element may be written after other XML elements (and therefore appear later in the
configuration file). This causes the ASP.NET runtime and other parts of the
.NET Framework to reject the configuration file as invalid.CAUSE This behavior occurs because the configuration WMI provider
does not provide control over the ordering of XML elements in configuration
files. It merely preserves the existing order in the configuration file.RESOLUTION To work around this issue, start with an empty
configuration file (or a nonexistent configuration) and make sure that the
first instance being written to the file is an instance of the configSection WMI class.
You can also write an empty
<configSections> XML element to the file through other means (for
example, manually use a text editor, through an XML parser, to directly access
the file).STATUSMicrosoft has confirmed that this is a bug in the Microsoft products that are listed in the "Applies to" section.
| Modification Type: | Minor | Last Reviewed: | 1/25/2006 |
|---|
| Keywords: | kbvs2005doesnotapply kbvs2005swept kbtshoot kbvs2002sp1sweep kbbug kbnofix kbreadme KB307506 kbAudDeveloper |
|---|
|