Dec 08, 2014 07:02 AM|AxelD|LINK
Thank you Michelle.
However, I'm sharing pgaule's opinion:
One of the main reasons for using Entity Framework is its navigation property service. If you omit navigation properties for some other pattern, Entity Framework on ASP.NET Identity renders no benefit. There'd be no reason from a user's perspective for using
Entity Framework for ASP.NET.
Making use of generic keys is no excuse for omiting navigation properties. The ASP.NET Identity team can easily create a relationship mapping corresponding to any key there is in ASP.NET Identity. Doing so is but using one of the key features of Entity Framework.
So I still would very much like to suggest to return to provide navigation properties to ASP.NET.
Is this possible?