I'm trying to work out how to reconcile this.. I have a situation where i need access to the ProviderUserKey Access.HasAccces(d.Id, member.ProviderUserKey) but then i need to refer to the umbraco member's id..
I was just wondering what the logic was behind having a member class in the umbraco business logic that didn't expose the core membership info when the members and roles are using the out of the box asp.net user fucntionality..
is there a way to achieve what i need to do without doing something like assigning one variable for each type i.e.
var member = System.Web.Security.Membership.GetUser();
var umbracoMember = Member.GetCurrentMember();
umbraco Member vs System.Web.Security.Membership
Hi Guys,
I'm trying to work out how to reconcile this.. I have a situation where i need access to the ProviderUserKey Access.HasAccces(d.Id, member.ProviderUserKey) but then i need to refer to the umbraco member's id..
I was just wondering what the logic was behind having a member class in the umbraco business logic that didn't expose the core membership info when the members and roles are using the out of the box asp.net user fucntionality..
is there a way to achieve what i need to do without doing something like assigning one variable for each type i.e.
hi tomm,
do you got any solution for the query above.
Nope.. I just used both... it feels very dirty... surely there has to be a better way!
is working on a reply...