Differences between. NET FRAMEWORK4 and its client Profile version

". NET FRAMEWORK4 differs from its client Profile version "

In short, the client Profile version is a subset of the full version. Contains most of the most commonly used features and reduces the volume for easier installation and release, along with some of the benefits that Microsoft claims, such as reducing some libraries, making them more secure, and so on.

Starting with. NET 2.0, it's embarrassing to release a small program under XP that comes with a. NET 2.0 Redist installation package of more than 20 m. The user will ask, why do I need a dozens of m installation package for such a small feature? If you publish only the program and let users download and install the. NET Library, it is more unacceptable to the user.

XP still survives in China for a long time, and. NET has evolved to 4.X. The installation package is much larger. This is undoubtedly a pain for developers and users alike. So starting from 3.5, the client Profile version appears.

The client Profile version of 4.X is a little bit better than the 3.5 Client Profile version, and now it can support all versions of the system, from XP to Win7 from 32 to 64 bits. The benefits of specific Clent Profle editions:

1 Reduce release time.

2 reduce the possibility of publishing errors.

3 Reduce the capacity of the release media.

4 is more secure because it excludes some components, such as ASP, and is less vulnerable to attack.

So how much capacity can be reduced specifically? In fact, not many, about 7-8m about. But it's still worth the choice.

For the vast majority of client desktop applications, including WinForm and WPF, Ms recommends the use of client profile. Of course, it is important to note that subsets inevitably have some functional limitations, such as projects created with this can not refer to assemblies other than client profile.

Reference: http://blog.csdn.net/cnhk1225/article/details/46983245

Differences between. NET FRAMEWORK4 and its client Profile version