I am building a web application which will have a public facing piece with a forms login, and an internal piece with windows authentication login. The two projects will be using the same database. I would like to rely on Visual Studio tooling as much as possible, but do things the right way.
I was thinking of creating three projects in a single solution:
- Internal - ASP.Net MVC 4 Intranet application
- External - ASP.Net MVC 4 Internet application
- Models - just a class library
What is the best way to handle membership and database context? Move everything to the models class?