Groups | Blog | Home
all groups > visual studio .net general > august 2006 >

visual studio .net general : Could not find schema information for the element


Leslie
8/14/2006 7:34:01 AM
I have a VS 2005 project that was converted to a 2005 project. I get several
errors that start with the "Could not find schema information fo rthe
element..." These are elements that are found in custom sections that
reference
"System.Configuration.NameValueSectionHandler,System,Version=1.0.5000.0,Culture=neutral,PublicKeyToken=b77a5c561934e089"

How do I get rid of these informational messages?

Thanks,

v-garych NO[at]SPAM online.microsoft.com (
8/15/2006 12:00:00 AM
Hi Leslie,

[quoted text, click to view]

This error could be caused by some syntax errors in your code or an
inaccurate scheme file (DotNetConfig.xsd) which is provided by the VS2005.

If you make sure your code is all right, I suggest you use an updated
scheme file to replace the default one, you can download the updated one
and find directions on the following links:

http://www.peterritchie.com/Hamlet/Downloads/74.aspx

Thanks!

Best regards,

Gary Chang
Microsoft Online Community Support
==================================================
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
ications.

Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscriptions/support/default.aspx.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
Leslie
8/15/2006 5:42:45 PM
Gary,

I updated the schema file based upon the instructions in the link. But the
problem still occurs.

messages appear on custom config file sections. The sections are used during
program execution and all of that seems to work just fine. However, there is
no schema documentation for the custom sections as they are sections that I
have created.

The NameValueSectionHandler works great, it is just the messages that are
causing the problems.

How should a custom section be documented and where?

Thanks,

Leslie


[quoted text, click to view]
v-garych NO[at]SPAM online.microsoft.com (
8/16/2006 12:00:00 AM
Hi Leslie,

[quoted text, click to view]

You need to create your own XSD (e.g. mySchema.xsd) to describe that custom
configuration section, and save it to your VS2005 schemas directory
(...\Program Files\Microsoft Visual Studio 8\xml\Schemas\) directory.

Then, in the DotNetConfig.xsd (I mentioned in the previous reply, which is
located in the same directoryl), include the schema-file (mySchema.xsd) you
just created by adding the following line:

<xs:include schemaLocation="mySchema.xsd" />


Wish it helps!

Best regards,

Gary Chang
Microsoft Online Community Support
==================================================
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
ications.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
Leslie
8/16/2006 7:55:01 AM
Gary,

Creating my own XSD fixed it.

Thanks,

Leslie

[quoted text, click to view]
AddThis Social Bookmark Button