.NET Framework Client Profile

Introduction

As you know, the size of the .NET framework increases from release to release. But, unfortunately, not all potential users have a wide unlimited channel.
The task was to determine which .NET Framework that supports WPF is optimal in terms of ease of distribution. After all, I do not want to lose users because of the extra megabytes in the installer.
Those. It was necessary to decide which .NET Framework to use: .NET 3.0 or .NET 3.5.


Comparison
')
The main plus of .NET 3.0 - it is preinstalled in the operating system Vista
Pros of .NET 3.5

• functionally richer compared to its predecessor
• has client profile version (details below)

As a result, the .NET Framework Client Profile was selected. Because In this case, XP users will need to download about 30 megabytes (framework + application), and Vista users about 12. It should be noted that some users of Windows Vista will receive .NET 3.5 through Windows Update and for them the installation will cost by downloading only the application itself.

After making a decision, there was a desire to learn the opinion of the habr-community on this issue. But I did not find any publications where the .NET Framework Client Profile would be affected. Therefore, I decided to highlight this vobros.

Description .NET Framework Client Profile

The .NET Framework Client Profile is the 28 MB of builds most often used when creating desktop applications on .NET.
It includes:

• Common Language Runtime (CLR)
• ClickOnce
• Windows forms
• Windows Presentation Foundation
• Windows Communication Foundation

Detailed description - Introducing the .NET Framework Client Profile
Detailed list of assemblies - .NET Framework Client Profile Assemblies

Full framework download size (3.5SP1)

There are no installed frameworks ~ 56 MB
Installed 2.0 ~ 50 MB
Installed 2.0SP1 ~ 33 MB
Installed 3.0SP1 ~ 10 MB

Read more - On the Size of the .NET Framework

PS It would be interesting to hear your opinions on this.