How do I properly add a custom section to my Web.Config?

[Brad Wood]

If I add my own section to my Web.Config file of my (2.0) web service
project (and refer to it by adding a "section" sub-element to a
"configSections" element, I then get information messages ("Could not
find schema information for the element"...) for every custom element
and attribute in my custom section when I build my project.
What should I do to properly dispose of these messages? Surely I
shouldn't have to create a schema?

[Stan Kitsis [MSFT]]

These are just info messages. You can filter them out by clicking on the
"Messages" button in the Error List.

--
Stan Kitsis
Program Manager, XML Technologies
Microsoft Corporation

This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm

"Brad Wood" <bradley|.wood|@ndsu|.edu> wrote in message
news:%2****************@TK2MSFTNGP09.phx.gbl...

If I add my own section to my Web.Config file of my (2.0) web service
project (and refer to it by adding a "section" sub-element to a
"configSections" element, I then get information messages ("Could not find
schema information for the element"...) for every custom element and
attribute in my custom section when I build my project.
What should I do to properly dispose of these messages? Surely I
shouldn't have to create a schema?

[tonyraw]

I have the same problem with my custom config sections resulting in
around 200 info messages. Is it possible to stop these info messages
being emitted as they just provide a lot of noise which obscures other
messages?

Actually what I would really like to do is provide a schema for my
config sections and then be able to use intellisense for these
sections. Is this possible and if so is there any guidance available on
how to it?
Stan Kitsis [MSFT] wrote:

These are just info messages. You can filter them out by clicking on the
"Messages" button in the Error List.

--
Stan Kitsis
Program Manager, XML Technologies
Microsoft Corporation

This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm

"Brad Wood" <bradley|.wood|@ndsu|.edu> wrote in message
news:%2****************@TK2MSFTNGP09.phx.gbl...

If I add my own section to my Web.Config file of my (2.0) web service
project (and refer to it by adding a "section" sub-element to a
"configSections" element, I then get information messages ("Could not find
schema information for the element"...) for every custom element and
attribute in my custom section when I build my project.
What should I do to properly dispose of these messages? Surely I
shouldn't have to create a schema?

[chris haas]

I couldn't stand having Messages show up even if it did still compile.
Here's the fix:
http://www.ovationmarketing.com/XSD.asp
Brad Wood wrote:

*If I add my own section to my Web.Config file of my (2.0) web
service
project (and refer to it by adding a "section" sub-element to a
"configSections" element, I then get information messages ("Could
not
find schema information for the element"...) for every custom
element
and attribute in my custom section when I build my project.
What should I do to properly dispose of these messages? Surely I
shouldn't have to create a schema? *

--
chris haas
------------------------------------------------------------------------
Posted via http://www.codecomments.com
------------------------------------------------------------------------