the process returns a true value if the ID is found, otherwise it will just return an error message as a string. now i look at it again with a little clearer mind there is no need to typecast it.

and for the check i take it it will be enough to add a button that first checks and then fires the register event. maybe this way i can centralize that check so the login can call it as well. but first i would like to know how to put the registration up, then i will see about part 2.

and i would like to contact you but i cant find an email adress or PM function in here.

Hi Jon,

I dont want to hi-jack this thread, but thanks a lot for posting this detailed page, i was just starting to write a small custom registration form today and this has cut down my research time by a huge factor. I find it difficult to pin down in the DNN documentation where to find the various functions i need, and given the scope of the DNN API its easy to understand, but there seems not to be any detailed information on the various objects, such as userinfo.

I was wondering, i have also got a pre-created security role. Immediately following the insertion of the new user, i'd like to add them straight to that role - could you suggest how i would go about that? - also what what 'type' is DotNetNuke.Security.Membership.UserCreateStatus, so i know how to handle the variable crstat, i presume it is used to identify the success of the attempt to add a user?

EDIT:
I got it working, during my searches i stumbled on another post with the answer already contained, provided again by yourself Jon!
For anyone elses reference, this did the trick. Obviously the objuser.UserID is populated as part of the return for a successful user addition.
RoleController rc = new DotNetNuke.Security.Roles.RoleController();
rc.AddUserRole(this.PortalId,info.UserID, rc.GetRoleByName(this.PortalId, "Customer").RoleID, DateTime.MinValue);

Many Thanks, Charles

DotNetNuke.Security.Roles.

hi again,

on the page 2 you stated that i would first call a few login processes and then redirect the user to another page. would that be coded into the module or set up in dotnetnuke?

and the registration/login module, does that have to be only the fields i want to use when logging in or the full registration? because then i would need to make either a seperate login/register page since i only want the ID to be entered on registration and not on login. or i would need to edit the default login page to check for a valid ID, but this would mean i would have to edit again when i update