The Microsoft .NET Framework 4.0 full installer (32- and 64-bit) is 48.1 MB and the Client Profile installer is 41.0 MB. The extracted installation files are 237 MB and 194 MB respectively, and once installed, they are 537 MB and 427 MB.
This is a difference of 110 MB. What difference is there between the two packages?
The.NET Client Profile is a subset of the.NET Framework, which was provided with.NET Framework 4 and earlier versions and was optimized for client applications. The.NET Framework is a development platform for Windows, Windows Phone and Microsoft Azure and provides a managed app execution environment and the.NET Framework class library. Microsoft net framework 4 0 full. free download - Microsoft.NET Framework 4, Microsoft.NET Framework 4.5, Microsoft.NET Framework 3.5, and many more programs. Microsoft.NET Framework 4 Client Profile is a redistributable package which provides only a few features of the.NET Framework 4, and it has been developed specifically to enable fast deployment.
When is it preferable to install the Client Profile instead of the full .NET Framework?
Peter MortensenWhat's new in .NET Framework 4 Client Profile RTM explains many of the differences:
When to use NET4 Client Profile and when to use NET4 Full Framework?
NET4 Client Profile:
Always target NET4 Client Profile for all your client desktop applications (including Windows Forms and WPF apps).
NET4 Full framework:
Target NET4 Full only if the features or assemblies that your app need are not included in the Client Profile. This includes:
However, as stated on MSDN, this is not relevant for >=4.5:
Starting with the .NET Framework 4.5, the Client Profile has been discontinued and only the full redistributable package is available. Optimizations provided by the .NET Framework 4.5, such as smaller download size and faster deployment, have eliminated the need for a separate deployment package. The single redistributable streamlines the installation process and simplifies your app's deployment options.
cicYou should deploy 'Client Profile' instead of 'Full Framework' inside a corporation mostly in one case only: you want explicitly deny some .NET features are running on the client computers. The only real case is denying of ASP.NET on the client machines of the corporation, for example, because of security reasons or the existing corporate policy.
Saving of less than 8 MB on client computer can not be a serious reason of 'Client Profile' deployment in a corporation. The risk of the necessity of the deployment of the 'Full Framework' later in the corporation is higher than costs of 8 MB per client.
A list of assemblies is available at Assemblies in the .NET Framework Client Profile on MSDN (the list is too long to include here).
If you're more interested in features, .NET Framework Client Profile on MSDN lists the following as being included:
And the following as not being included:
Cameron MacFarland nailed it.
I'd like to add that the .NET 4.0 client profile will be included in Windows Update and future Windows releases. Expect most computers to have the client profile, not the full profile. Do not underestimate that fact if you're doing business-to-consumer (B2C) sales.
Peter MortensenYou have a Mac,
.Net Framwork is for Windows and normally you would have to install Windows either into BootCamp or
a virtual machine software (better,easier, not as powerful as direct install, fine if you don't need it) like VMFusion (best), Parallels Desktop (best) or the free Virtualbox (works)
But there is a Open Source .Net framework called Mono
I don't have any expereince with this, so your on your own
Perhaps that's for the developers to implement with their programs, I don't know if there is a Mac client so you can access .Net
Ask the website your visiting to do something so your Mac can also visit and use the site.
Apr 4, 2012 7:54 PM
댓글 영역