Re: Manually adding a ASP.Membership account for an install script

One way to do this is to actually add

System.Web
and all the <membership> xml to a CONSOLE app or Windows Form app.

And then you can code against the membership provider, and get this default
data in.

.......

I do this for an application.
The client gives me a list of users, their default password, and a user to
role mapping.
(I give them the list of roles).

I actually wrote a (company owned) text file parser that does the work for
me.

..................

The TSQL stuff.

I got this to work one time, but I was using plain passwords. So maybe
someone else can help with that.





"DotNetNewbie" <snowman908070@xxxxxxxxx> wrote in message
news:48b68d25-2432-427c-99e2-eb8a011a9c72@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Hello,

I am having issues with manually creating a membership user using the
stored procedure: aspnet_Membership_CreateUser

I can't seem to be able to insert a 'password salt' value and have it
work when I try and log in.

Here is what I did: After creating a user and being able to
successfully log into my application, I looked in the database for the
Password Salt.

I then used that SAME value along with username in my install.sql
script file (it just preloads the database with data).

My login doesn't work though, what could the problem be?


.

Loading