"Steven Cheng[MSFT]" wrote:

> Hello Onecorp,
>
> Based on the symptom you described, you're encountering an known issue of
> the VS 2005/ASP.NET 2.0. I've found your another thread posting in the
> newsgroup about "web site admin tool....". I think the (
> xmlns="http://schemas.microsoft.com/.NetConfiguration/v2.0" ) attribute is
> added everytime you use web site admin tool to configure the ASP.NET 2.0
> application, correct?
>
> According to our internal product database, the problem is actually due to
> the following cause:
>
> 1. ASP.NET 2.0 originally force to use the
> (xmlns="http://schemas.microsoft.com/.NetConfiguration/v2.0" ) namespace
> explicitly (in beta) and finally change it as an optional value since it
> will break some design-time features(such as IDE intellisense for editing
> web.config file and show design-time schema information not found warning
> you met...).
>
> 2. The MSDN document below hasn't been updated after this change, currently
> this is also a pending request in our internal product database.
>
> http://msdn2.microsoft.com/en-us/library/ms228147.aspx
>
> 3. When using the web admin web tool to configure our ASP.NET 2.0 web
> application, it will automatically add the (
> xmlns="http://schemas.microsoft.com/.NetConfiguration/v2.0" ) attribute to
> our web.config's root element. and will result to the above issue.
>
> Here is the existing bug report entry in the MSDN product feedback center:
>
> #Web admin adds namespace to web.config
> http://connect.microsoft.com/VisualStudio/feedback/ViewFeedback.aspx?Feedbac
> kID=105100
>
> Currently , as a workaround you can consider the following options:
>
> 1) leave the ( xmlns="http://schemas.microsoft.com/.NetConfiguration/v2.0"
> ) attribute in the web.config file and the "could not found schema
> information..." warning is specific to vs 2005 xml designer only, it won't
> affect your ASP.NET application's runtime behavior.
>
> 2) You can manually remove the (
> xmlns="http://schemas.microsoft.com/.NetConfiguration/v2.0" ) attribute in
> your web.config and this will not cause any problem. You can refer to the
> following forum article and the ASP.NET product manager Scott has also
> mentioned this:
>
> http://forums.asp.net/thread/1254376.aspx
>
>
> In addition, since this is a known issue which is still pending in our dev
> team, I would also suggest you submit a new request or vote the existing
> record above. Thus, our product team can hear more from the community on
> this issue and will have increase the priority of this issue.
>
> Anyway, I'm sorry for any inconvenience it brings you on this issue.
>
>
> Sincerely,
>
> Steven Cheng
>
> Microsoft MSDN Online Support Lead
>
>
>
> ==================================================
>
> 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.
>
>
>
>