Vista + Orcas Beta 1 web.config child nodes not allowed when building or using ASP.NET configura
Running Windows Vista Business edition w/ VS 2005 SP1 installed + VS Orcas Beta 1. When creating a new ASP.NET website project I receive the following when building a basically empty page:
Error 1 E:\..\Documents\Visual Studio Codename Orcas\Projects\WebApplication1\WebApplication1\Default.aspx: ASP.NET runtime error: Child nodes not allowed. (E:\..\Documents\Visual Studio Codename Orcas\Projects\WebApplication1\WebApplication1\web.config line 46) E:\..\Documents\Visual Studio Codename Orcas\Projects\WebApplication1\WebApplication1\Default.aspx 1 1 WebApplication1
It points to the following line in the web.config:
<providerOptionname="CompilerVersion"value="v3.5"/>
The web.config is completely unmodified and as-is when creating a new ASP.NET web site.
I had trouble installing .NET framework 3.5 via the VS Orcas setup so I had installed it separately first and then ran the VS Setup - maybe this had something to do with it. I may not have run all the installs in the .NET install directory (there were a few from what I remember).
Help! Totally can't play with ASP.NET in this cool beta... how unsatisfying after downloading 5.2 gbs.
I am experiencing the same problems.
After a few hours searching the web, I think the reason for the problem is that we're trying to use ASP.NET 3.5 (or, the version of ASP.NET that ships with .NET 3.5) with IIS 7.0. If you check the properties in IIS 7.0 (i.e. the Application Pools), you can't select other versions of ASP.NET but 2.0.
I remember having read that they didn't change anything in the System.Web assemblies (because they wanted to ensure 100% backwards compatibility with .NET 2.0) and that ASP.NET 3.5 simply is a set of extension assemblies (System.Web.Extensions) - this explains why there's simply one option on the IIS 7 Application Pool settings.
However, I would think that the new 3.5 compilers (i.e. for C# 3.0) should be associated with an application somehow.
If I'm unable to resolve this, I'm going back to Windows 2003 Server for Orcas web development.
Somebody from MS please help us! :-)
the sample solution is delete the xml child where the complier said,just like
<compilers>
<compiler language="c#;cs;csharp" extension=".cs"
type="Microsoft.CSharp.CSharpCodeProvider, System, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089">
</compiler>
<compiler language="vb;vbs;visualbasic;vbscript" extension=".vb" compilerOptions="/optioninfer+"
type="Microsoft.VisualBasic.VBCodeProvider, System, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089">
</compiler>
</compilers>
i suggest you use orcas to debug or run the web project, and i think iis7 is not compatible with .net framework 3.5 now.
Sorry about the troubles you all are running into. Unfortunately, this looks like something that you'd get much better traction on if you'd post about it in the
ASP.NET Forums instead as they're better suited to help out with these types of problems. Sorry that's not much help but I hope someone there can help you get going.
I had the same problem. After installing Orcas Beta 1 install the following patches.
\VS2008 Beta 1\WCU\dotNetFramework\dotNetMSP\x86
Windows6.0-KB110806-x86.msu
Windows6.0-KB929300-x86.msu
Windows6.0-kb930264-x86.msu
In that order. Reboot after the final install and it should fix both the Web projects and the Winforms projects when targeting the 3.5 framework.
Regards
Tobi.
