Downgrading to asp.net 2.0

I have build an asp.net website using Visual Studio 2008 and .NET Framework 3.5.
When published on the server (Windows server 2003), it throwing the attached error. (Line 104)
I think its because the server uses .NET Framework 2.0. If changing the .NET framework on the server is not an option, how can I change the Framework on my website ? Are there any changes that can be made on IIS without disturbing the existing websites on it?

In VS 2008, I went to Website -> Start Options -> Build -> selected .NET Framework 2.0 and recompiled the website. I did not see any change in the code or web.config file after that. Are the changed files hidden?
Also, doing this still did not get rid of the error. Any ideas please?
Parser Error Message: Child nodes not allowed.

Source Error:

Line 102:		<compilers>
Line 103:			<compiler language="c#;cs;csharp" extension=".cs" warningLevel="4" type="Microsoft.CSharp.CSharpCodeProvider, System, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089">
Line 104:				<providerOption name="CompilerVersion" value="v3.5"/>
Line 105:				<providerOption name="WarnAsError" value="false"/>
Line 106:			</compiler>

Open in new window

Angel02Asked:
Who is Participating?
 
strickddCommented:
You've done the hard part of downgrading the project itself. Now if you create a web.config for the app it will be a 2.0 web.config and you can port your current settings to the new one. That should fix your problem.
0
 
chapmanjwCommented:
Is the .NET 3.5 framework installed on the Windows Server 2003 box?
0
 
Angel02Author Commented:
@chapmanjw
.NET 3.5 is NOT installed on the Windows 2003. Does it matter if the website is not using it anyway ?
0
 
chapmanjwCommented:
I would either take the compilers section completely out of your web.config or install .NET 3.5 on the server and set your target back to 3.5.  VS doesn't make all the changes necessary on an existing app automatically when you change the target framework.
0
 
Angel02Author Commented:
Thanks, as you said and as strickdd indicated above, recreating the web.config, after changing the target framework fixed the issue. Now the website is actually using .NET 2.0.
Works perfect when new installations on the server are not feasible. Thank You !
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.