ASP.Net 2 authentication WITHOUT the new stuff? [modified]
-
Ok, perhaps I just don't get it. I'm an old asp developer... I've been using .net 1.1 for some time now. Now I'm tasked with implementing a new asp.net 2 site on top of an older sql 2000 db. This is where things get whacked for me: every article I can find wants me to use the aspnetdb (whether in sql Express or by porting it over to an existing sql database). But the database I have already contains the username and password stuff. DOes this mean I must re-write all of the logic to look this information up in other tables across databases? Does this mean I must re-code my object model? Help me obi wan... isn't there a better way? -- modified at 1:35 Wednesday 16th August, 2006
-
Ok, perhaps I just don't get it. I'm an old asp developer... I've been using .net 1.1 for some time now. Now I'm tasked with implementing a new asp.net 2 site on top of an older sql 2000 db. This is where things get whacked for me: every article I can find wants me to use the aspnetdb (whether in sql Express or by porting it over to an existing sql database). But the database I have already contains the username and password stuff. DOes this mean I must re-write all of the logic to look this information up in other tables across databases? Does this mean I must re-code my object model? Help me obi wan... isn't there a better way? -- modified at 1:35 Wednesday 16th August, 2006
Hi there, The ASP.NET 2.0 privides a couple of common services like Membership, Roles ... in the provider model using the predefined tables in the aspnetdb database (or you can install in your current db). And to use these services, you are only required to do some configurations without writing any line of code. However, if you want to use these services with your custom database schema then you need to privide your own custom providers[^]. In addition, you can keep using your custom object model to do all the common tasks instead of using the supported services.
-
Hi there, The ASP.NET 2.0 privides a couple of common services like Membership, Roles ... in the provider model using the predefined tables in the aspnetdb database (or you can install in your current db). And to use these services, you are only required to do some configurations without writing any line of code. However, if you want to use these services with your custom database schema then you need to privide your own custom providers[^]. In addition, you can keep using your custom object model to do all the common tasks instead of using the supported services.
Yes, I see regarding the membership, roles, etc... however it's tough to re-write your database when everything centers around it, you know? I did find out late last night that it seems to be the best route to write a custom provider. I can't believe how long it took me to find out this information... I would think this was a more common problem..? Oh well, thank you so much for replying.
-
Yes, I see regarding the membership, roles, etc... however it's tough to re-write your database when everything centers around it, you know? I did find out late last night that it seems to be the best route to write a custom provider. I can't believe how long it took me to find out this information... I would think this was a more common problem..? Oh well, thank you so much for replying.