VSIP: Client Profile is default Target Framework for new projects - by jessielu

Status : 

  By Design<br /><br />
		The product team believes this item works according to its intended design.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.

Sign in
to vote
ID 524786 Comments
Status Closed Workarounds
Type Bug Repros 0
Opened 1/13/2010 11:57:00 AM
Access Restriction Public


I created a new project with target framework set to .NET Framework 4.  After the project was created, the project properties page shows the Target Framework as .NET Framework 4 Client Profile.  This is a problem for 3rd party assemblies that target the .NET Framework 4 because they may not build against the Client Profile.
Sign in to post a comment.
Posted by Microsoft on 1/20/2010 at 3:23 PM
I should also mention that indeed there are existing 3rd party components/controls that were mainly developed for Net 3.5 and VS 2008 and are not working when projects are targeting Net4 Client Profile.
Our understanding is that many of the vendors are looking to provide a new version of their controls in the near future . Until then the workaround is to retarget the project to Net4 Full.
Posted by Microsoft on 1/20/2010 at 3:18 PM
Per blog below this is by design. We changed many of the client project templates to target Net4 Client Profile by default.
Net4 Client Profile is likely what most developers need for most client projects and should provide the small optimal deployment to end user
Developers can always retarget their project to Full.
See blog:

Thanks fro reporting this. Jossef
Posted by Microsoft on 1/13/2010 at 6:32 PM
Thank you for your feedback, We are currently reviewing the issue you have submitted. If this issue is urgent, please contact support directly(http://support.microsoft.com)
Posted by David A Nelson on 1/13/2010 at 4:18 PM
You can always change the target framework...