Are there any good reasons to use .NET Framework 4 Client Profile instead of the full version?
I mean, real-life reasons. I am creating a .NET application, and since it's quite easy to create an installer that will install the .NET framework on a client machine, why bother using the Client Profile?
The documentation answers this:
The .NET Framework 4 Client Profile is a subset of the .NET Framework 4 that is optimized for client applications. It provides functionality for most client applications, including Windows Presentation Foundation (WPF), Windows Forms, Windows Communication Foundation (WCF), and ClickOnce features. This enables faster deployment and a smaller install package for applications that target the .NET Framework 4 Client Profile.
A smaller install package could be a bonus, especially if you're targeting non-traditional devices like tablets with less storage space. It's also a shorter download time if the Framework needs to be installed.
Applications that target the .NET Framework 4 Client Profile typically improve the deployment experience by having smaller download sizes and quicker install times. An application that targets the .NET Framework 4 Client Profile has a smaller redistribution package that installs the minimum set of client assemblies on the user's computer, without requiring the full version of the .NET Framework 4 to be present.
A good answer can be found in Stack Overflow question Differences between Microsoft .NET 4.0 full Framework and Client Profile. Basically, only use the full framework if you know you need to. Normal client applications should only need the client framework.
Some reasons:
