N
neilmcguigan
Hello
1. I'm starting a new application, and was thinking of using the
asp.net membership stuff for the application itself. For example the
table "saved_searches" would link the "userid" to the userid of the
asp_net users table. Is this a good or bad idea?
2. if it's a good idea, what if i want to store saved searches for
anonymous users? There seems to be no (prebuilt) programmatic access to
the providerUserKey for anonymous users. Just use a table adapter to
get this value?
3. if it's a bad idea, should i build my own membership provider?
Thanks
Neil
1. I'm starting a new application, and was thinking of using the
asp.net membership stuff for the application itself. For example the
table "saved_searches" would link the "userid" to the userid of the
asp_net users table. Is this a good or bad idea?
2. if it's a good idea, what if i want to store saved searches for
anonymous users? There seems to be no (prebuilt) programmatic access to
the providerUserKey for anonymous users. Just use a table adapter to
get this value?
3. if it's a bad idea, should i build my own membership provider?
Thanks
Neil