Comments on: Unrecognized attribute ‘targetFramework’ – Asp.Net 4.0 http://elegantcode.com/2009/11/10/unrecognized-attribute-targetframework-asp-net-4-0/ Mon, 15 Mar 2010 06:02:02 -0500 http://wordpress.org/?v=2.8.6 hourly 1 By: Jarod Ferguson http://elegantcode.com/2009/11/10/unrecognized-attribute-targetframework-asp-net-4-0/comment-page-1/#comment-50270 Jarod Ferguson Thu, 12 Nov 2009 20:15:45 +0000 http://elegantcode.com/2009/11/10/unrecognized-attribute-targetframework-asp-net-4-0/#comment-50270 well, I think the point of the post is targeting .net 4.0 features. So, if you don't want to take advantage of them, then yes, you can remove the attribute and run 3.5. There are quite a few improvements in the WCF service stack for 4.0, in which you can take advantage of if you run .net on both sides. (Especially for Silverlight, e.g DomainServce, Entity change tracking etc) well, I think the point of the post is targeting .net 4.0 features. So, if you don’t want to take advantage of them, then yes, you can remove the attribute and run 3.5.

There are quite a few improvements in the WCF service stack for 4.0, in which you can take advantage of if you run .net on both sides. (Especially for Silverlight, e.g DomainServce, Entity change tracking etc)

]]> By: Bob The Janitor http://elegantcode.com/2009/11/10/unrecognized-attribute-targetframework-asp-net-4-0/comment-page-1/#comment-50268 Bob The Janitor Thu, 12 Nov 2009 19:53:53 +0000 http://elegantcode.com/2009/11/10/unrecognized-attribute-targetframework-asp-net-4-0/#comment-50268 maybe, but that shouldn't matter, I'm consuming a soap web service, it shouldn't matter if it was 2.0, 3.5, 4.0 or even java for that matter. The whole point of web services are for interoperability maybe, but that shouldn’t matter, I’m consuming a soap web service, it shouldn’t matter if it was 2.0, 3.5, 4.0 or even java for that matter. The whole point of web services are for interoperability

]]> By: Jarod Ferguson http://elegantcode.com/2009/11/10/unrecognized-attribute-targetframework-asp-net-4-0/comment-page-1/#comment-50267 Jarod Ferguson Thu, 12 Nov 2009 19:44:07 +0000 http://elegantcode.com/2009/11/10/unrecognized-attribute-targetframework-asp-net-4-0/#comment-50267 if you removed it from the web.config and did not update the app pool, then chances are your WCF service is using 2.0 and targeting the incorrect http handler (svc-Integrated vs svc-Integrated-4.0). A symptom of this might be that is works in 2008, and not 2010 :) if you removed it from the web.config and did not update the app pool, then chances are your WCF service is using 2.0 and targeting the incorrect http handler (svc-Integrated vs svc-Integrated-4.0). A symptom of this might be that is works in 2008, and not 2010 :)

]]> By: Bob The Janitor http://elegantcode.com/2009/11/10/unrecognized-attribute-targetframework-asp-net-4-0/comment-page-1/#comment-50266 Bob The Janitor Thu, 12 Nov 2009 19:33:56 +0000 http://elegantcode.com/2009/11/10/unrecognized-attribute-targetframework-asp-net-4-0/#comment-50266 I was having this problem with a WCF service, to fix it I just removed the target framework from the web.config I was having this problem with a WCF service, to fix it I just removed the target framework from the web.config

]]>