Microsoft Knowledge Base Article
This article contents is Microsoft Copyrighted material.
©2005-©2007 Microsoft Corporation. All rights reserved.
Terms
of Use |
Trademarks
Article ID: 306725 - Last Review: January 25, 2006 - Revision: 4.4
BUG: The .NET configuration provider defaults to UTF-8 encoding when creating new configuration files
This article was previously published under Q306725
SYMPTOMS
When you use the Windows Management Instrumentation (WMI)
configuration provider to create a new configuration file, UTF-8 character
encoding is used by default.
CAUSE
The WMI configuration provider does not provide control
over the XML encoding that is used in a configuration file. It only uses
preexisting encoding if this is already specified in the configuration file.
RESOLUTION
To work around this problem, you can add an
encoding attribute to the header of the configuration file
through other means (such as through an XML parser, a text editor, or direct
file access). For example, you could start with a template configuration file
that has the proper XML encoding header.
If you specify the encoding
in a configuration file, the WMI configuration provider applies the encoding on
both read and write operations. The provider also preserves the encoding
information in the XML file.
STATUS
Microsoft has confirmed that this is a bug in the Microsoft products that are listed in the "Applies to" section.
APPLIES TO
- Microsoft Windows Management Instrumentation in . NET
- Microsoft .NET Framework 1.1
- Microsoft .NET Framework 1.0
- Microsoft .NET Framework Class Libraries 1.1
- Microsoft .NET Framework Class Libraries 1.0
- Microsoft Visual Studio .NET 2003 Professional Edition
- Microsoft Visual Studio .NET 2002 Professional Edition
| kbvs2005doesnotapply kbvs2005swept kbtshoot kbvs2002sp1sweep kbbug kbnofix kbreadme KB306725 |
Community Feedback System
Very often, it takes hours to solve a problem. Very often, you've looked high
and low, and have tried a lot of solutions. When you finally found it, chances
are, it was because someone else helped you. Here's your chance to give back.
Use our community feedback tool to let others know what worked for you and what
didn't.
Please also understand that the community feedback system is not warranted to be
correct, it's simply a system that we've built to let people try and help each
other. If something in a feedback response doesn't make sense to you, or you're
not comfortable making changes that the feedback talks about (like registry
edits), please consult a professional.
Thank you for using kbAlertz.com Feedback System.
-- Scott Cate
Be the first to leave feedback, to help others about this knowledge base
article.
(Optional) Name
(Optional)
Public URL Or Email
Comments
No
HTML -- Text Only Please