I suggest you ...

← Visual Studio

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'

93 votes
Vote
Sign in
Check!
(thinking…)
Reset
or sign in with
  • facebook
  • google
    Password icon
    Forgot password?
    Create a password
    I agree to the terms of service
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    MotoWilliamsMotoWilliams shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →
    completed  ·  Visual Studio teamAdminVisual Studio team (Product Team, Microsoft) responded  · 

    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).

    Thanks

    David Kean
    CLR Team

    2 comments

    Sign in
    Check!
    (thinking…)
    Reset
    or sign in with
    • facebook
    • google
      Password icon
      Forgot password?
      Create a password
      I agree to the terms of service
      Signed in as (Sign out)
      Close
      Close
      Submitting...
      • David KeanDavid Kean commented  ·   ·  Flag as inappropriate

        Starting in 4.5, there is no longer a "Client Profile"

        David Kean
        BCL Team

      Visual Studio: .NET

      Feedback and Knowledge Base

      (thinking…)