Chapter 4: "Could not find schema inf ... "

coollights · January 31st, 2006, 06:18 PM

Trying to run Ch 4 exercises, I received 50 error messages related to "Could not find schema information for the element 'http://schemas.microsoft.com/.NetConfiguration/v2.0:configuration'". After the colon, the message varied with :configuration, :appSettings, :connectionStrings and several others. In web.config, I have this line - <configuration xmlns="http://schemas.microsoft.com/.NetConfiguration/v2.0">.

Any idea why I'm getting this error? I've been running examples all day and haven't had any problems.

DaveSussman · February 1st, 2006, 04:49 AM

There are two possible problems here:

1. You're running the samples via IIS and havn't configured the IIS site to use ASP.nET 2.0 (it defaults to 1.1). If you're just pressing F5 to run samples and using the built-in web server, then this isn't the issue.

2. There is a known problem with intellisense in the web configuration file. Make sure web.config doesn't have any attributes on it's <configuation> element. That is it should appear just as <configuration>.

Dave

coollights · February 2nd, 2006, 03:18 PM

Thanks, Dave. I changed the configuration element to just <configuration> and it works fine.

habib · November 11th, 2006, 03:54 AM

Hi Dave,
i removed the code from configuration tag and all error are removed but now its giving me an error of Parser Error Message: Unrecognized configuration section 'connectionStrings' and i am using IIS6.0 but its not configure in v2.0 and i have designed my application in vs2005 any help will be highly appreciated.
thanks,
Habib
Afghanistan

DanM · November 12th, 2006, 12:44 PM

Hi Habib,

Your problem then is that your application is not running ASP.NET 2.0. Only v2.0 recognizes the <connectionStrings> section of web.config. v1.x does note and so throws an error.

Dan

Dan Maharry
Read the feed at http://feeds.feedburner.com/dansarchive

ddawson59 · December 28th, 2006, 02:28 AM

I just wondered why does the code downloaded containg the xmlns attribute in the <configuration> tag? Is it not needed or is there an error in the application (VWD)?

DanM · December 28th, 2006, 09:26 AM

It's 50/50. According to Microsoft, the xmlns should be there to make it valid xml. It's just that the bug in VWD \ VS2005 prevents intellisense from working if it is there. Which is annoying as VWD will add it in from tiem to tiem to make it 'correct'. Easier to remove it and have intellisense working.

Hopefully this is fixe din service pack 1 for vs2005 \ vwd.

Dan

Dan Maharry
Read the feed at http://feeds.feedburner.com/dansarchive