G
greg.hart
Hello all,
Just wanted to get some clarification on something. I was setting out
to create a login page for people to login and then be able to access
certain aspects of the website. Instead of doing what I usually do
which is store the username password in a db table then compare what
the user enters from the text boxes to what's in the db, I thought I
would try the login components from the toolbox.
In looking at how to wire those up it seems I have come across two
similiar ways, but they are a different and I am not sure if one is
better than the other etc.
In on item I found it was suggested to use the aspnet_regsql to create
the aspnetdb and the associated tables in my sql instance, add users,
which I did with a sql query I found, then wire it to the login
component.
The other item I found was within Visual Studio, click the ASP.NET
Configuration icon from within my project, which in turn creates an
aspnetdb.,df in my App_Data directory and go from there.
Not sure if the latter option is used when you don't have SQL server
available to you, but it seemed much easier to get wired up and worked
right away, versus the former option which I had trouble getting wired
up.
Thoughts?
Greg
Just wanted to get some clarification on something. I was setting out
to create a login page for people to login and then be able to access
certain aspects of the website. Instead of doing what I usually do
which is store the username password in a db table then compare what
the user enters from the text boxes to what's in the db, I thought I
would try the login components from the toolbox.
In looking at how to wire those up it seems I have come across two
similiar ways, but they are a different and I am not sure if one is
better than the other etc.
In on item I found it was suggested to use the aspnet_regsql to create
the aspnetdb and the associated tables in my sql instance, add users,
which I did with a sql query I found, then wire it to the login
component.
The other item I found was within Visual Studio, click the ASP.NET
Configuration icon from within my project, which in turn creates an
aspnetdb.,df in my App_Data directory and go from there.
Not sure if the latter option is used when you don't have SQL server
available to you, but it seemed much easier to get wired up and worked
right away, versus the former option which I had trouble getting wired
up.
Thoughts?
Greg