NET Framework 4.0 and. NET Framework 4.0 Client profile

NET Framework 4.0 and. NET Framework 4.0 Client profile differences:

The. NET Framework 4.0 is no doubt like the. NET Framework 2.0, which is the 4.0 version of the. NET Framework;

The. NET Framework 4.0 Client profile is a subset of the. NET Framework 3.5 SP1, which is the. NET Framework 4.0 simplified version,

is for client-side applications (This is why it is not possible to use the IIS7 API).

What is to introduce this simplified version?

1. Reduce the deployment time of the. NET Framework and the applications that package also the. NET Framework;
2. Reduce the failure of the. NET framework deployment;
3. Reduce the size of the. NET framework in the ISV software, thus giving its software more space;
4. Reduce the compromised "interface" of the system where the. NET Framework Client Profile is installed because the client Profille contains the components required by ASP.

When to use NET4 Client profiles and when to use NET4 the full Framework?

Client Profile:
We recommend the NET4 Client profile is utilized as the primary framework for most client desktop applications (inclu Ding Windows Forms and WPF apps).
Since we is considering to make the NET4 client profiles available broadly to desktops via Windows Update, most Client des Ktops May has NET4 Client profile soon after NET4 releases making it ubiquitous*.
Until that time, NET4 apps can chain-install the NET4 Client profile which are smaller and faster to install.

*note:this plan is not final.

Full framework:
The full framework was a superset of the Client profile. It should mainly is used for:

Server apps (e.g. ASP. NET apps) for developer scenarios (for example, this includes MSBuild) for all other Legacy Client s Cenarios (for example, this includes System.Data.OracleClient.dll which was being deprecated in NET4) that's not included In the Client profile.

Category: C #

NET Framework 4.0 and. NET Framework 4.0 Client profile