Did anybody convert this solution to use Entity Framework instead of Linq2SQL?

It seems Microsoft merely supports Linq2SQL (only bug fixes), and because of the growing and widening functionality of the EF, it worths the conversion.

The first difficulty is in the custom membership provider.

In all GetUser... methods we have to return the MembershipUser for the Asp.net Authentication Service, but we want ot use the UserInformation object in our solution, to store them in the Globals.currentUser and use them in the UserRegistration and AccountSettings pages.

In Linq2SQL it's easy to circumvent this difficuly, because we can inherit UserInformation from MembershipUser, as we did in UserInformationMetadata.cs class.

In EF however all objects are inherited from the EntityObject, so we can't inherit from two base classes.

Maybe the solution is to extract Interface from the membershipUser and apply it to UserInformation? Did anybody solve this issue?

Any help will be greatly appreciated,

Gabor

Yes I'm having this problem to as like you say the UserInformation class cannot inherit MembershipUser as it already inherits from EntityObject.
Im currently creating my own user class and will ditch the metadata class but the price of this is losing the neat validation provided by attributes.
I will let you know how this goes. I do think its a good idea to ditch LinqToSQL though due to MS basically giving up on it.

If You create a new User class, You can attach attrubutes to them, or create metadata class manually.

If You give up with the UserInforation class like in the book's code, You also lost the possibility to build a usercontrol based on dataform very easy, with validation and localization possibilities, and use them on Registration and AccountSettings pages, wich save you from many manual coding.

I'm waiting for Your solution inpatiently

Gabor

Has anyone been able to resolve this?

The book has some great ideas but it seems to me that Entity Framework support is a must for serious RIA Services LOB app development.

I can figure out how to manipulate custom providers without using EF but I really like the way the book integrates them with Linq2SQL and it would be great if we could do it with EF.