In asp.net-mvc, Is there any good reason to keep your model in the same project?
===

I have an asp.net-mvc site and recently I have wanted to generate emails with the same data that i am using to render to a webpage.  So slowly but surely I started moving a lot of my model and data access code into a seperate project so i can do the email generation stuff from a command line app or a service, etc (no dependency on any web stuff) . . if I take this one step further, I am now thinking I should just move all of my model and data access code outside of the MVC project so its a bit more future proof.   I know MVC gives you the default Model folder inside the web project.  Is there any reason to keep it there?