Web.config schema messages

[Rachel]

Hi,

I currently have several sections pointing to various custom providers
inside my Web.conf file.

I get multiple messages about not being able to find schema information.
("Could not find schema information for the element
'http://schemas.microsoft.com/.NetConfiguration/v2.0:configSections'")

Currently my configuration tag is as follow:
"<configuration xmlns="http://schemas.microsoft.com/.NetConfiguration/v2.0">"

The site works fine despite the messages but It'd feel better without them!

Does someone have a fix?

Thanks.

R

[S. Justin Gengo]

Rachel,

I haven't tried this myself, but this is supposed to be the fix:

http://www.ovationmarketing.com/XSD.asp

Regards,

--
S. Justin Gengo
Web Developer / Programmer

Free code library:
http://www.aboutfortunate.com

"Out of chaos comes order."
Nietzsche
"Rachel" <Ra****@discussions.microsoft.com> wrote in message
news:1D**********************************@microsof t.com...

Hi,

I currently have several sections pointing to various custom providers
inside my Web.conf file.

I get multiple messages about not being able to find schema information.
("Could not find schema information for the element
'http://schemas.microsoft.com/.NetConfiguration/v2.0:configSections'")

Currently my configuration tag is as follow:
"<configuration
xmlns="http://schemas.microsoft.com/.NetConfiguration/v2.0">"

The site works fine despite the messages but It'd feel better without
them!

Does someone have a fix?

Thanks.

R

[Erik Funkenbusch]

On Mon, 20 Mar 2006 22:32:27 -0800, Rachel wrote:

I get multiple messages about not being able to find schema information.
("Could not find schema information for the element
'http://schemas.microsoft.com/.NetConfiguration/v2.0:configSections'")

Currently my configuration tag is as follow:
"<configuration xmlns="http://schemas.microsoft.com/.NetConfiguration/v2.0">"

Remove the xmlns attribute entirely. This is added erroneously by the
ASP.NET Administration tool.

[S. Justin Gengo]

Hmmm,

I should have realized what this really was (I reported it as a bug back in
November), thanks Erik.

http://lab.msdn.microsoft.com/produc...9-a2ea6051d54a

Here's the fix Microsoft attached to my bug report to keep it from ever
happening again:

FDBK39924#2: Fix Web Site Administration Tool
Workaround Description:
It is possible to correct this problem modifing source of configuration tool
that can be found in
%windir%\Microsoft.NET\Framework\v2.0.50727\ASP.NE TWebAdminFiles
Workaround Steps:
Change in WebAdminPage.cs file, located in
%windir%\Microsoft.NET\Framework\v2.0.50727\ASP.NE TWebAdminFiles\App_Code
directory, the line (number 93):

config.NamespaceDeclared = true;

with

config.NamespaceDeclared = false;

Regards,

--
S. Justin Gengo
Web Developer / Programmer

Free code library:
http://www.aboutfortunate.com

"Out of chaos comes order."
Nietzsche
"Erik Funkenbusch" <er**@despam-funkenbusch.com> wrote in message
news:1d****************@funkenbusch.com...

On Mon, 20 Mar 2006 22:32:27 -0800, Rachel wrote:

I get multiple messages about not being able to find schema information.
("Could not find schema information for the element
'http://schemas.microsoft.com/.NetConfiguration/v2.0:configSections'")

Currently my configuration tag is as follow:
"<configuration
xmlns="http://schemas.microsoft.com/.NetConfiguration/v2.0">"

Remove the xmlns attribute entirely. This is added erroneously by the
ASP.NET Administration tool.

[Rachel]

Unfortunately this is not a fix because I started out without the “xmlns� bit
but VS complained about my CUSTOM (provider) sections requesting a schema.
I read somewhere the actual fix is to include schema information about the
new sections in the “C:\Program Files\Microsoft Visual Studio
8\Xml\Schemas\DotNetConfig.xsd� file but how do I do that? Is there a way to
automatically generate new schema info based on existing “web.config�?
Thanks in advance.

Rachel

"S. Justin Gengo" wrote:

Hmmm,

I should have realized what this really was (I reported it as a bug back in
November), thanks Erik.

http://lab.msdn.microsoft.com/produc...9-a2ea6051d54a

Here's the fix Microsoft attached to my bug report to keep it from ever
happening again:

FDBK39924#2: Fix Web Site Administration Tool
Workaround Description:
It is possible to correct this problem modifing source of configuration tool
that can be found in
%windir%\Microsoft.NET\Framework\v2.0.50727\ASP.NE TWebAdminFiles
Workaround Steps:
Change in WebAdminPage.cs file, located in
%windir%\Microsoft.NET\Framework\v2.0.50727\ASP.NE TWebAdminFiles\App_Code
directory, the line (number 93):

config.NamespaceDeclared = true;

with

config.NamespaceDeclared = false;

Regards,

--
S. Justin Gengo
Web Developer / Programmer

Free code library:
http://www.aboutfortunate.com

"Out of chaos comes order."
Nietzsche
"Erik Funkenbusch" <er**@despam-funkenbusch.com> wrote in message
news:1d****************@funkenbusch.com...

On Mon, 20 Mar 2006 22:32:27 -0800, Rachel wrote:

I get multiple messages about not being able to find schema information.
("Could not find schema information for the element
'http://schemas.microsoft.com/.NetConfiguration/v2.0:configSections'")

Currently my configuration tag is as follow:
"<configuration
xmlns="http://schemas.microsoft.com/.NetConfiguration/v2.0">"

Remove the xmlns attribute entirely. This is added erroneously by the
ASP.NET Administration tool.

[Erik Funkenbusch]

On Wed, 22 Mar 2006 14:05:26 -0800, Rachel wrote:

Unfortunately this is not a fix because I started out without the ´xmlns¡ bit
but VS complained about my CUSTOM (provider) sections requesting a schema.
No. You should not have any complaint about a custom provider without the
xmlns.
I read somewhere the actual fix is to include schema information about the
new sections in the ´C:\Program Files\Microsoft Visual Studio
8\Xml\Schemas\DotNetConfig.xsd¡ file but how do I do that? Is there a way to
automatically generate new schema info based on existing ´web.config¡?

No, this is simply not true. The xmlns was used in betas, and mistakenly
was never removed from the administration site code. It simply should not
be there at all.