Client Profile should not be the default framework
Let the developer choose if they want client profile. There are more projects that require full .NETFx and just client profile.
Enable better warnings when a project is set to client profile but actually needs full .NETFx
If you really want to enable more client profile usage then setup a build warning indicating that you 'could be using client profile'
Thanks for the great suggestion. We’ve made three changes in .NET Framework 4.5 and Visual Studio 2012 in response to this:
1) Starting in .NET Framework 4.5, there is no more “client profile”.
2) When targeting previous versions of .NET (3.5 & 4.0), the default is now the full framework and not the client profile. Users wanting to retarget to the client profile can do so via the Target framework drop down in the project properties.
3) The default for executable projects is now Any CPU and not x86. Class library projects remain the same as the previous version (Any CPU).
David Kean commented
Starting in 4.5, there is no longer a "Client Profile"
And x86 shouldn't be the default either, any CPU would be better.