Multiple Projects in an MVC application

I am working on an MVC3 application at the moment. I also have a requirement to create custom membership providers for this appl. What I was hoping to do was create a separate MVC3 solution/project with the classes + controllers/views for the membership stuff, so that I can potentially reuse it in other applications as required.

• Is this the best way to do this? Or is there any other r开发者_如何学Pythonecommended way?
• If I go this route, create the project and then add it to the initial app (as an existing item), how would I get to the controllers/views on the user project? is it just a case of setting up the routes correctly? Can Areas be used for this?

Thank you for your insights.