.NET Framework Client Profile
Introduction
As you know, the size of the .NET framework is increasing from release to release. But, unfortunately, not all potential users have a wide unlimited channel.
The goal 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 due to extra megabytes in the installer.
Those. I had 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 Vista operating system.
Pluses of .NET 3.5
As a result, the .NET Framework Client Profile was selected. Because in this case, XP users will have to download about 30 megabytes (framework + application), and Vista users about 12 megabytes. 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 downloading only the application itself.
After the decision was made, there was a desire to learn the opinion of the habr community on this issue. But I did not find publications where the .NET Framework Client Profile would be affected. Therefore, I decided to highlight this stuffing.
Description of the .NET Framework Client Profile The
.NET Framework Client Profile is the 28 MB builds most commonly used to create .NET desktop applications.
It included:
Detailed description - Introducing the .NET Framework Client Profile
Detailed assembly list - .NET Framework Client Profile Assemblies
Full framework download size (3.5SP1)
No frameworks installed ~ 56 MB
Installed 2.0 ~ 50 MB
Installed 2.0SP1 ~ 33 MB
Installed 3.0SP1 ~ 10 MB
In more detail - On the Size of the .NET Framework
PS It would be interesting to hear your opinions on this matter.
As you know, the size of the .NET framework is increasing from release to release. But, unfortunately, not all potential users have a wide unlimited channel.
The goal 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 due to extra megabytes in the installer.
Those. I had 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 Vista operating system.
Pluses of .NET 3.5
- functionally richer than its predecessor
- has a Client Profile version (details below)
As a result, the .NET Framework Client Profile was selected. Because in this case, XP users will have to download about 30 megabytes (framework + application), and Vista users about 12 megabytes. 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 downloading only the application itself.
After the decision was made, there was a desire to learn the opinion of the habr community on this issue. But I did not find publications where the .NET Framework Client Profile would be affected. Therefore, I decided to highlight this stuffing.
Description of the .NET Framework Client Profile The
.NET Framework Client Profile is the 28 MB builds most commonly used to create .NET desktop applications.
It included:
- Common Language Runtime (CLR)
- ClickOnce
- Windows forms
- Windows Presentation Foundation
- Windows Communication Foundation
Detailed description - Introducing the .NET Framework Client Profile
Detailed assembly list - .NET Framework Client Profile Assemblies
Full framework download size (3.5SP1)
No frameworks installed ~ 56 MB
Installed 2.0 ~ 50 MB
Installed 2.0SP1 ~ 33 MB
Installed 3.0SP1 ~ 10 MB
In more detail - On the Size of the .NET Framework
PS It would be interesting to hear your opinions on this matter.