Advice needed (ASP.NET membership)

[Robert]

Hi there,

I''m going be to be working on a new (Internet) web site that requires users
to sign up for the service we offer (with a SQL Server back end). Does it
make sense to rely on the membership services of ASP.NET to store our users.
That is, should I start by:

1) Creating my DB using the standard "ASPNETDB.mdf" file generated with the
"ASP.NET Configuration" tool (available on the Visual Studio "Website" menu)
2) Build the remainder of my DB on top of this one (including adding my
application-specific columns to the "aspnet_Users" table in the above DB)

Is this an accepted and even recommended practice. My app would then add new
users to the "aspnet_Users" table when they sign up (using
"Membership.CreateUser()"). It doesn't seem to make sense to create a new DB
from scratch with my own "Users" table. Can someone offer some advice.
Thanks.

 

[HillBilly]

Go to http://asp.net and watch the video that explains how to configure
Membership. The video(s) answers your question.

 

[Robert]

Go to http://asp.net and watch the video that explains how to configure

Membership. The video(s) answers your question.

Thanks. I'll take a look but I'm already familiar with the basic details of
membership. What's still unclear is whether the membership DB should be
maintained separately from my app's DB. I wouldn't think so since I need my
own users table so it would be ugly and difficult to maintain two separate
DBs. I could create my own membership provider but that's just reinventing
the wheel so it seems to make sense to just extend the native "ASPNETDB.mdf"
file. I'll try to locate the video you're referring to since maybe it will
clear this up. Thanks.