Troubleshooting .NET Framework Targeting Errors

Posted on 2010-11-10
Last Modified: 2013-11-17
Hi My site was working and now is not working after I did the following in my Visual Studio 2010

The Web project ‘ ’ is targeting “.netframework, version =v2.0’, which is not installed on this machince. You must download this framework, as well as .net framework 3.5, in order to open and build this project. In order to proceed, you must select an option below

( x) retarget the project to .net framework 4. After the project opens, you can retarget it to another framework or profile.
(  ) take me to the framework download web site
( ) leave the project as unloaded.

[ ] Do not ask me again during this operation.

I've chooose X Retarget... So now it's now working and it giving me the following errors How I can fixed back to 2.0

 Please advice...


Configuration Error
Description: An error occurred during the processing of a configuration file required to service this request. Please review the specific error details below and modify your configuration file appropriately.

Parser Error Message: Unrecognized attribute 'targetFramework'.

Source Error:

Line 12:           debugging ASP.NET files.
Line 13:     -->
Line 14:             <compilation defaultLanguage="vb" debug="true" targetFramework="4.0"/>
Line 15:             <!--  CUSTOM ERROR MESSAGES
Line 16:           Set customErrors mode="On" or "RemoteOnly" to enable custom error messages, "Off" to disable.

Source File: E:\inetpub\wwwroot\UNESCO\web.config    Line: 14
Question by:elieazzi
  • 7
  • 2

Author Comment

Comment Utility
This my web.config file.

<?xml version="1.0"?>



		<add key="XmlFilePath" value="./menu.xml"/>




          Set compilation debug="true" to insert debugging symbols (.pdb information)

          into the compiled page. Because this creates a larger file that executes

          more slowly, you should set this value to true only when debugging and to

          false at all other times. For more information, refer to the documentation about

          debugging ASP.NET files.


		<compilation defaultLanguage="vb" debug="true" targetFramework="4.0"/>


          Set customErrors mode="On" or "RemoteOnly" to enable custom error messages, "Off" to disable. 

          Add <error> tags for each of the errors you want to handle.


		<customErrors mode="Off"/>


          This section sets the authentication policies of the application. Possible modes are "Windows", 

          "Forms", "Passport" and "None"


		<authentication mode="None"/>


          This section sets the authorization policies of the application. You can allow or deny access

          to application resources by user or role. Wildcards: "*" mean everyone, "?" means anonymous 

          (unauthenticated) users.



			<allow users="*"/>

			<!-- Allow all users -->

			<!--  <allow     users="[comma separated list of users]"

                             roles="[comma separated list of roles]"/>

                  <deny      users="[comma separated list of users]"

                             roles="[comma separated list of roles]"/>




          Application-level tracing enables trace log output for every page within an application. 

          Set trace enabled="true" to enable application trace logging.  If pageOutput="true", the

          trace information will be displayed at the bottom of each page.  Otherwise, you can view the 

          application trace log by browsing the "trace.axd" page from your web application



		<trace enabled="false" requestLimit="10" pageOutput="false" traceMode="SortByTime" localOnly="true"/>


          By default ASP.NET uses cookies to identify which requests belong to a particular session. 

          If cookies are not available, a session can be tracked by adding a session identifier to the URL. 

          To disable cookies, set sessionState cookieless="true".


		<sessionState mode="InProc" stateConnectionString="tcpip=" sqlConnectionString="data source=;user id=sa;password=" cookieless="false" timeout="20"/>


          This section sets the globalization settings of the application. 


		<globalization requestEncoding="utf-8" responseEncoding="utf-8"/>

		<pages controlRenderingCompatibilityVersion="3.5" clientIDMode="AutoID"/></system.web>


Open in new window

LVL 19

Accepted Solution

Daniel Van Der Werken earned 500 total points
Comment Utility
Change this line:
<compilation defaultLanguage="vb" debug="true" targetFramework="4.0"/>

to this:

<compilation defaultLanguage="vb" debug="true" />

Author Comment

Comment Utility
I've chagned now i'm having this error

Line 56:     -->
Line 57:             <globalization requestEncoding="utf-8" responseEncoding="utf-8"/>
Line 58:             <pages controlRenderingCompatibilityVersion="3.5" clientIDMode="AutoID"/></system.web>
Line 59: </configuration>

Author Comment

Comment Utility
i did it but i'm having the following errors
Line 56:     -->

Line 57: 		<globalization requestEncoding="utf-8" responseEncoding="utf-8"/>

Line 58: 		<pages controlRenderingCompatibilityVersion="3.5" clientIDMode="AutoID"/></system.web>

Line 59: </configuration>

Open in new window

What Should I Do With This Threat Intelligence?

Are you wondering if you actually need threat intelligence? The answer is yes. We explain the basics for creating useful threat intelligence.


Author Comment

Comment Utility
are u there ?

Author Comment

Comment Utility
As a I  try, right click your website >> Property Pages >> Build >> change "Target Framework" to .NET Framework 4.0

I only see 4.0 I'm not able to see 2.0 or 3.5 Any solutions?

Author Comment

Comment Utility
Hi Dan,

I've removed the following code.

Line 58:             <pages controlRenderingCompatibilityVersion="3.5" clientIDMode="AutoID"/>

What this mean ? Now it's working please advice....
<globalization requestEncoding="utf-8" responseEncoding="utf-8"/>


Open in new window


Author Closing Comment

Comment Utility
Please answer my comments. thank you for your time.
LVL 19

Expert Comment

by:Daniel Van Der Werken
Comment Utility
Sorry.  Took Veteran's Day off.
When you target 3.5 or above, it puts a bunch of stuff in the Web.config.  As a result, you will not be able to use that very web.config for 2.0 builds.  

One thing you might want to do is clear out the web.config of anything that refers to 3.5 or as another possibility, create a blank project with 2.0 as the target and use that web.config as a model for the web.config you need.

Featured Post

How to run any project with ease

Manage projects of all sizes how you want. Great for personal to-do lists, project milestones, team priorities and launch plans.
- Combine task lists, docs, spreadsheets, and chat in one
- View and edit from mobile/offline
- Cut down on emails

Join & Write a Comment

Introduction This article shows how to use the open source plupload control to upload multiple images. The images are resized on the client side before uploading and the upload is done in chunks. Background I had to provide a way for user…
It was really hard time for me to get the understanding of Delegates in C#. I went through many websites and articles but I found them very clumsy. After going through those sites, I noted down the points in a easy way so here I am sharing that unde…
Here's a very brief overview of the methods PRTG Network Monitor ( offers for monitoring bandwidth, to help you decide which methods you´d like to investigate in more detail.  The methods are covered in more detail in o…
This video gives you a great overview about bandwidth monitoring with SNMP and WMI with our network monitoring solution PRTG Network Monitor ( If you're looking for how to monitor bandwidth using netflow or packet s…

744 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

12 Experts available now in Live!

Get 1:1 Help Now