CODEWITHSUNDEEP
visual-studio-2010entity-frameworkdbcontextasp.net-mvc-areas
tcode
tcode

Reputation: 5105

3 MVC projects in 1 Solution

I have to build 3 MVC web applications using Entity Framework (www.company1.com www.company2.com www.company3.com). The websites will all access the same sql server database, but will be slightly different in their own way (appearance, data etc). More than likely all three MVC applications will be hosted on the same server, but binded to different domain names.

Currently in Visual Studio, I have the following structure to my solution

I would have preferred to have used Area's, but I can't because each site has to be assigned it's own different domain name. I guess I am just seeking assurances that architecting my solution this way won't cause any difficulties for me when the applications are published. I am slightly paranoid about the sites sharing the dbContext or something, however, I know that many sound silly.

It would be great if anyone could advice me if this all looks ok, or maybe there is a better way to do what I am asking.

Thanks as ever.

Upvotes: 0

Views: 76

Answers (2)

Faust
Faust

Reputation: 15404

I've done the same thing for the same reason. I have a CMS that must reside at a different host-name. It works fine.

The trick is finding ways of sharing code across the MVC apps. To avoid circular dependencies and such, I created one more MVC app to hold things such as my controller that serves up image files, HTML Helpers that can be re-used, etc.

Upvotes: 1

Kevin Hendricks
Kevin Hendricks

Reputation: 785

As long as you have a good way of validating and differentiating the sites in the Datalayer, than you will not have to worry. How are you validating this?

I also would always put simulair code and pages in a main project so you do not copy parts or even whole pages for different sites. (My guess is that you already did so)

Upvotes: 1

Related Questions