Entity Framework entity splitting

We were talking about how we can be smarter about setting up models for objects where the required fields change depending on who is looking at it - e.g. Where an administrator is setting up a user they should only need to set up email address, username, dummy password and client. When the user logs in it should then force them to fill in more details, such as name and address. One way of doing this is documented below.

http://www.robbagby.com/entity-framework/entity-framework-modeling-entity-splitting/

Entity Framework 4.1 Release Candidate available for download

Update from CTP 5.

http://www.microsoft.com/downloads/en/details.aspx?FamilyID=2dc5ddac-5a96-48b2-878d-b9f49d87569a

Procedurally generated culture sensitive validation for ExtJS.

So here's a quick update of what I've been doing in the last week.  My estimate for this was way of the mark but I encountered a couple of bugs in ExtJS concerning at which point ExtJS receives its validation data, and at which point we can hook in to use its nifty features, but now I think I've got the best part of a pattern down for how to go about building custom controls with culturally sensitive validation.