 |
|
 |
I am thinking to use this table and entity and leave them empty but hydrate them from sp calls with efextensions. has anyone else tried this approach?
|
| Sign In·View Thread·PermaLink | |
|
|
|
 |
|
 |
It is very difficult to work out what this code would do other than to download it and build it.
|
| Sign In·View Thread·PermaLink | 1.00/5 (2 votes) |
|
|
|
 |
|
|
 |
|
 |
Hi,
I finished the coding. However, I was not yet able to fully test all the providers. If you want me to send you the beta leave me your email address and I will send it to you.
Cheers, M
|
| Sign In·View Thread·PermaLink | |
|
|
|
 |
|
|
 |
|
|
 |
|
 |
Hi, firstly thanks for your excellent job again.
I just finished implementing your provider to my project and tested it. Everything works perfect but only one thing is not working right. Although a user is locked out he or she is able to login. So I have reviewed the code and found a small missing thing. It's in ValidateUser() function:
if (CheckPassword(password, user.Password)) { if (user.IsApproved && !user.IsLockedOut) { isValid = true; .......
Hope it helps.
|
| Sign In·View Thread·PermaLink | |
|
|
|
 |
|
 |
Can your property IsLockedOut be null?
Don't you get this error?
Operator '&&' cannot be applied to operands of type 'bool' and 'bool?'
Thanks!!
|
| Sign In·View Thread·PermaLink | |
|
|
|
 |
|
 |
You're right alibaba069. If IsLockedOut column in database allows nulls, "&& cannot be applied" error will be occurred. I think I overlooked it because designed my database myself. My suggestion you should set IsLockedOut column as cannot be null. Already CreateUser() method is assigning false value to IsLockedOut automatically. If I'm wrong please warn me...
|
| Sign In·View Thread·PermaLink | |
|
|
|
 |
|
 |
Thanks a lot for that. You are completely right. I fixed the code and the db schema as you suggested. This will be available with the release of the complete provider implementations coming very soon.
Cheers
|
| Sign In·View Thread·PermaLink | |
|
|
|
 |
|
 |
Hi. I would like to ask you a Question.
I don't know much about Provider Model Design Patterns. I would like to use them, because they are well known. I was doing some examples for integrate it in my application in ADO.NET. And I have a doubt.
Is it possible to use providers if in my data base I have other entries (such us telephone number) that they are not specified in the MemberShip Provider?
Then If I add it on my implementation of EFMemberShipProvider it won't work with another Provider like SqlMemberShipProvider.
And what about if I don't use one, like userName because I consider the email as identifier.
Can I still use a Provider Model Design?
Thanks.
|
| Sign In·View Thread·PermaLink | |
|
|
|
 |
|
|
 |
|
|
 |
|
 |
You are welcome.  A couple of other providers are already coded and I started the doco on codeproject. However, due to moving my home it will take a bit until I will be able to finish everything. Plz bear with me. Cheers
|
| Sign In·View Thread·PermaLink | |
|
|
|
 |
|
|
 |
|
|
 |
|
|
 |
|
|
 |
|
 |
Thanks for that.
However, this has got nothing to do with the Entity Framework since it is built on top of the DevExpress XPO layer.
Cheers,
|
| Sign In·View Thread·PermaLink | |
|
|
|
 |
|
 |
Will you implement the RoleProvider and ProfileProvider too? I want to use your provider in my site, but I need roles too... Thanks anyway for the code, but as others said, you should perhaps talk a little more about your implementation.
|
| Sign In·View Thread·PermaLink | 5.00/5 (1 vote) |
|
|
|
 |
|
|
 |
|
 |
Michael Ulmann has posted a reply to your message at "Article "Custom membership provider for the entity framework"":
If you understood the MS membership provider you would know that this is just covering the same functionality as the SqlMembershipProvider. It does not make sense at all to dump heaps of lines of code that are straight forward implemented.
Cheers
Actually, I DO understand the membership provider. But, I'm not the next guy reading this "article". I have to think about the newbie comming in behind me that might NOT understand the provider. You leave it entirely up to the reader to decipher your code, which is NOT good way to teach someone about it.
|
| Sign In·View Thread·PermaLink | |
|
|
|
 |
|
 |
I understand your objection. However, the membership provider functionality is elaborately described in the MSDN. I did not want to rewrite a documentation about that, thus the requirements to understand the membership provider model. Same applies for the ADO.NET Entity Framework, the MSDN is the right place to learn about it for newbies.
The published solution is meant as reusable component and does exactly the same as the SqlMembershipProvider but it utilize SQL to Entities rather than SQL statements.
I don't see what there might be to decipher for anyone?
From my understanding Codeproject is meant to be a platform to exchange solutions rather than a mirror of the MSDN.
Cheers
|
| Sign In·View Thread·PermaLink | |
|
|
|
 |
|
|
 |