views:

184

answers:

2

I am about to start a new application and am excited about using asp.net mvc and nhibernate. However, the big "problem" is how I handle the user authentication stuff. What are some ways those used to using nhibernate and MVC solve this problem?

My thought is let asp.net do its own thing and I do my own thing database wise. Am curios if I should role my own using the provider model and nhibernate, if I can figure out how. Or is there a way to integrate current code that is in the mvc example into nhibernate?

+1  A: 

You can still use the ASP .NET 2.0 Membership APIs from ASP .NET MVC.

Dan
I am curios if I should rewrite them using nhibernate for data access or leave them be.
percent20
It's not necessary. You already have a object-oriented API. The data access has been taken care of for you. You could wrap the APIs to add functionality or make them easier to use if needed.
Dan
+1  A: 

Same question here and Manuel Abadia has written a custom NHMembershipProvider here.

mattRo55
Thank you for linking to this. I am needing to migrate this app to somewhere else and this will make life a bit easier. Thanks.
percent20