I am developing a website using ASP.Net 2.0, which needs a forum. I have just set up a DNN site, & am starting to get my head around how it works. The main site also has a user registration process, which I have implemented using the ASP.Net 2.0 Membership facility, using the standard SQLServer provider.
The users of this site will really hate having to rehgister twice, so I need some kind of mechanism to either (i) share the user information, so that users regietered in one are automatically registered in the other, or (ii) automate the registration process in the other, so the two user exists in both.
My first idea seems preferable to me, unless of course it raises many issues, in which case it may be simpler to implement my second idea. However, let's think about the first idea first.
Firstly, what would happen if I simply pointed my other website's membership provider at the DNN database on my SQL Server? Has this been done before?
I notice that DNN doesn't implement the ASP.Net 2.0 Roles functionality, whereas my other website does. If I pointed both websites (the DNN one & the non-DNN one) at the same SQWL database, but then enabled roles in my other website, would that just enable my other website to use the Roles tables in the DNN database, even though DNN doesn't use them itself? Would that then enable me to use these Roles exclusively in the other website, without affecting any Roles functionality within DNN (given that DNN implements its own Roles functionality)?
Any thoughts on this topic would be appreciated, as I need to decide quickly exactly how I am going to do this, as I am very short on time (but then, aren't we all, most of the time?)
Thanks,
Paul Cutcliffe
eNet IT Solutions Ltd
+44 (0)1323 640500
+44 (0)7739 731427