The Client Profile is smaller in size and its goal is to improve the deployment size, time, reliability and overall deployment experience for client applications.
The Client Profile contains the functionality that most common desktop client applications (including Windows Forms and WPF applications) would need, so we expect that many client application developers will target it. This will improve the overall application deployment experience when the application requires .NET Framework 4 to be installed.
When to use NET4 Client Profile and when to use NET4 Full Framework?
We recommend that the NET4 Client Profile be utilized as the primary framework for most client desktop applications (including Windows Forms and WPF apps).
Since we are considering to make the NET4 Client Profile available broadly to desktops via Windows Update, most client desktops may have NET4 Client Profile soon after NET4 releases making it ubiquitous*.
Until that time, NET4 apps can chain-install the NET4 Client Profile which is smaller and faster to install.
*Note: This plan is not final."
The client profile came in .NET 3.5, but was little-used for various reasons.
In .NET 4.0 the client profile is more mature and I am not worried that it will be tentative. Given the late stage of the process (this is in Beta 2 with a go-live license after all), it would take a major problem for them to change now.
Smart client projects all default to using the client profile - WPF, Windows Forms, etc. Because of this, CSLA needs to have a client-profile-compatible version that can be referenced by those projects.
Of course it still needs a full-.NET version for web app development, which is really the only common project type left that still uses full .NET.
The biggest change from 3.5 to 4.0 is that it is actually possible to deploy only the client profile to a target workstation. In 3.5 if you installed the client profile, Microsoft Update would automatically pull down the rest of .NET. But in 4.0 if you install the client profile, that's all that machine may ever have. Unless the user later installs another app that requires full .NET, they may never have full .NET on the machine.
So it is in all of our best interest to target the right profile when building apps, and specifically to try to stick with the client profile when building smart client apps.
Of course I'm of the opinion that most smart client apps going forward should be written in Silverlight - which is basically a third profile (so we have client, full, Silverlight).
JonnyBee:The MVVMExperiment sample is not yet updated for CSLA 4.0 - and still references CSLA 3.8 (target .NET 3.5
CSLA .NET for Silverlight is its own download from
You need to download and build the framework, then download and build the samples.
You should make sure to follow the recommended folder structure, as the assembly references use relative paths. If you don't follow the recommended folder structure you'll need to remove/re-add all the Csla.dll references.
You also must have .NET 3.5 SP1 and SL3 installed of course. The DataAnnotations assembly was introduced in .NET 3.5 SP1 and SL3.
Copyright (c) Marimer LLC