views:

40

answers:

0

How is everyone designing their EF models when using the built in ASP .NET Membership functionality?

I have many entities (blog posts, comments, photos, etc.) which have a user id associated with them. I currently have a User model that maps to the aspnet_User table, but there is lots of sketchy code juggling around both the MembershipUser entity and the User model which I've created.

Does anybody have any clever solutions I may be overlooking to merge the two entities while still using the included membership functionality?