Should I use Membership and Roles in ASP.NET 2.0

[msnews.microsoft.com]

Hello All,

I did a lot of reading on this new feature from Microsoft ASP.NET 2.0, but I
ran into a design problem. In my project the user information contains much
more information then the information shown in the default membership and
roles tables that are installed with SQL server.

Therefore I need to link Asp_Tables to my own tables, but then I have an
issue with transactions, if I delete a user, I need to delete all the User
information in my tables as well, and that needs to be protected around a
transaction. I don't want to use System.Transaction because my transactions
will be promoted to DTC.

I wonder if there is an elegant solution for this, so I can use ASP.NET
membership and roles, but yet be able to have additional User information
and keep everything protected.

At this point I am starting to think that implementing my own Form
Authentication is simply the way to go, using my tables with my design.

 

[Jeff Dillon]

Use a stored procedure?? Or a trigger?

Either support transactions..

Jeff