Atlas Web.config warnings?

When I compile an Atlas web application, I get quite a few warnings in my error list. These are the errors I get:

The 'requirePermission' attribute is not declared.
Could not find schema information for the element 'microsoft.web'.
Could not find schema information for the element 'converters'.
Could not find schema information for the element 'add'.
... etc.

This happens even with a brand new AJAX application.

Can anyone tell me why this is happening?

Thanks.

You need to keep the configuration schema in web.config like this :
<configurationxmlns="http://schemas.microsoft.com/.NetConfiguration/v2.0">

But when you add uri for the configuration schema, IntelliSense editor in web.config is disable.

I was having a similar problem, but when I ran the Web Site Configuration utility this got added for me automatically.

so after adding this I lose all intellisense and moreover I get these warnings.

Could not find schema information for the element 'http://schemas.microsoft.com/.NetConfiguration/v2.0:configuration about 84 such messages.

Anyway to get around these warnings, seems like I replaced a small number of warnings for a larger set.

The url of configuration schema verion 2.0 is "http://schemas.microsoft.com/.NetConfiguration/v2.0". It is default for .net 2.0 configuration schema. As you see in MSDN, SectionInformation class had been defined a public property that called "RequirePermission". But in VS.NET configuration schema file, it doesn't define an attribute "requirePermission" for "section" node. Therefore, when section node has "requirePermission" attribute, it will raise warnings liked "The 'requirePermision' attribute is not declared".
If you don't intend to modify web.config programmatically, you don't need to set up "requirePermision" attribute value. :)
There is no need to set url of configuration schema. This url only helps VS.NET could find help item when you press F1 in web.config.

I read the above postings and none of them sound promising to remove the warnings that were original posted for...

Adding... <configuration xmlns="http://schemas.microsoft.com/.NetConfiguration/v2.0"> to the web.config poduced 84 messages about schemas not being found.

If anyone can help with more detail for the following, that would be GREAT!!!

Code from Web.config
<microsoft.web>
<converters>
<add type="Microsoft.Web.Script.Serialization.Converters.DataSetConverter"/>
<add type="Microsoft.Web.Script.Serialization.Converters.DataRowConverter"/>
<add type="Microsoft.Web.Script.Serialization.Converters.DataTableConverter"/>
</converters>
<webServices enableBrowserAccess="true"/>
</microsoft.web>

Warnnings:
Could not find schema information for the element 'microsoft.web'. C:\Inetpub\wwwroot\Atlas_1\Web.config
Could not find schema information for the element 'converters'. C:\Inetpub\wwwroot\Atlas_1\Web.config
Could not find schema information for the element 'add'. C:\Inetpub\wwwroot\Atlas_1\Web.config
Could not find schema information for the attribute 'type'. C:\Inetpub\wwwroot\Atlas_1\Web.config
Could not find schema information for the element 'add'. C:\Inetpub\wwwroot\Atlas_1\Web.config
Could not find schema information for the attribute 'type'. C:\Inetpub\wwwroot\Atlas_1\Web.config
Could not find schema information for the element 'add'. C:\Inetpub\wwwroot\Atlas_1\Web.config
Could not find schema information for the attribute 'type'. C:\Inetpub\wwwroot\Atlas_1\Web.config
Could not find schema information for the element 'webServices'. C:\Inetpub\wwwroot\Atlas_1\Web.config
Could not find schema information for the attribute 'enableBrowserAccess'. C:\Inetpub\wwwroot\Atlas_1\Web.config
There's just silly warnings, it's not affecting your application working or compiling one single bit... just ignore them... it's a bug/needed-schema-fix for the framework, but it's nothing more than an annoyance
OK, agreed.. it does not impact the application, but VERY anoying. Thanks for snapping me out of it. :)

Totally disagree with Morningz, totally agree with jrblack

"just ignore them" is no solution :P

I have the same problem and I wanna solve it, not hear comments like "just forget it" or "you don't need it"...

yeah, i agree with NNM, i also got those warnings, and i'm not crazy about just forgetting things like that...
In this case,

<

configurationxmlns="http://schemas.microsoft.com/.NetConfiguration/v2.0">

worked for me, but the attitude "just forget it" is not gonna get you far imo...

I changed from: <configuration>
to: <configuration xmlns="http://schemas.microsoft.com/.NetConfiguration/v2.0">

Went

from: 6 warnings, 21 messages
to: 101 messages

I wonder which one is better. beta2 with ctp

NNM:

In this case,

<

configurationxmlns="http://schemas.microsoft.com/.NetConfiguration/v2.0">

worked for me, but the attitude "just forget it" is not gonna get you far imo...

Well, pick your poison...

1) Leave the "warnings" that do not affect the application one single bit from working

or

2) Live without Intellisense in the web.config file

You choose #2, i choose #1, and i can live with it if you can.... otherwise i see no need for either one of your posts that just rehash posts from months ago

I just get off by seeing 0 erros 0 warnings 0 everything when I compile... :P

And it gets drummed into our heads by people trying to stop us from being lazy programmers, "Treat warnings as errors"

I find it difficult to ignore warnings. A warning is indicative of a problem that needs to be fixed.

of course, here's the ultimate answer: Dude, it's beta.

(still annoys me though)

What bugs me is 2.0 isn't beta anymore and it is still annoying me.