Quantcast
Channel: ASPNETWebStack Issue Tracker Rss Feed
Viewing all articles
Browse latest Browse all 7215

Commented Issue: SimpleMembershipProvider bad designed or idea hasn't been understood ? [958]

$
0
0
Hi
we have following situation:
- 2 applications works with same database (backend/frontend - is hosting environment dbase restriction).
- frontend application could contains more then 300000members (open/local)
- backend - 1000-10000
- we want to control(work with) backend/frontend users separately - each one have to has separate membership tables combination, all tables [not only profile table]. To prevent performance specific issues on database level (before application cache, special logic).

question:
- How can we change membership, roles and other table names?
- Lot of blog posts are talking about Code First Simplemebership provider. Where is code first? Internally code using "string resources with SQL instructions".

Regards, A.K.



Comments: Sounds like membership might not be for you: [http://brockallen.com/2012/09/02/think-twice-about-using-membershipprovider-and-simplemembership/](http://brockallen.com/2012/09/02/think-twice-about-using-membershipprovider-and-simplemembership/)

Viewing all articles
Browse latest Browse all 7215

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>