Re: Should I use Membership and Roles in ASP.NET 2.0
- From: "Jeff Dillon" <jeffdi@xxxxxxxxxxx>
- Date: Wed, 1 Nov 2006 12:45:37 -0800
Use a stored procedure?? Or a trigger?
Either support transactions..
Jeff
"msnews.microsoft.com" <abc@xxxxxxxxxxx> wrote in message
news:ejos6%23Q$GHA.1224@xxxxxxxxxxxxxxxxxxxxxxx
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.
.
- References:
- Should I use Membership and Roles in ASP.NET 2.0
- From: msnews.microsoft.com
- Should I use Membership and Roles in ASP.NET 2.0
- Prev by Date: Forms Based Authentication and AD and Roles and Security Trimming!
- Next by Date: Object reference not set to an instance of an object
- Previous by thread: Should I use Membership and Roles in ASP.NET 2.0
- Next by thread: Re: unable to execute dos commands through web application
- Index(es):
Relevant Pages
|