Should I combine asp.net db membership with the db site or keep it separate?

Question

which is better and why?

Answer 1

If your site database contains its own membership structure, I would be inclined to write my own membership provider to get the data out of it.

If you use the default ASP.NET membership database, you might want to keep it separate, as it can be used by more than one application.

, , , , , ASP.NET.

, . , , .

Answer 2

, . , . , .